Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-2891

Facter 4.0.46 (from puppet 7) breaks virtual flag

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • High
    • Resolution: Fixed
    • FACT 4.0.44
    • FACT 4.0.47
    • Facter 4
      • Tested in similar Systems running CentOS 7,
      • Puppet-agent 7,
      • same code,
      • with above commands.

      100% reproduceable.

    • Night's Watch
    • ghost-9.12
    • Needs Assessment
    • Bug Fix
    • Hide
      Description of the problem: Facter fails to detect that it is on virtual environment when it's run on OpenVZ.
      Description of the fix: Check if /proc/lve/list file is a regular file instead of checking if it's executable.
      Show
      Description of the problem: Facter fails to detect that it is on virtual environment when it's run on OpenVZ. Description of the fix: Check if /proc/lve/list file is a regular file instead of checking if it's executable.
    • Needs Assessment

    Description

      Hey,

      I am running the puppet-collection 7 with facter 4.0.46 that comes along. I have a few containers that are inside OpenVZ / Virtuozzo environment. Previously it was matched correctly as "openvz" or "openvzhe", now its just "physical":

      [root@zen10:~] # systemd-detect-virt
      		 
      openvz
      		 
      [root@zen10:~] # facter is_virtual virtual
      		 
      is_virtual => false
      		 
      virtual => physical
      		 
      [root@zen10:~] # facter -v 
      4.0.46

       

      On a similar system, albeit not updates to Puppet 7:

       

      [root@babbel:~] # systemd-detect-virt
      		 
      openvz
      		 
      [root@babbel:~] # facter is_virtual virtual
      		 
      is_virtual => true
      		 
      virtual => openvz
      		 
      [root@babbel:~] # facter -v 
      3.14.12 (commit 70d26da13c9fee27973c1eb22200871e21445d97)

       

      Attachments

        Activity

          People

            oana.tanasoiu Oana Tanasoiu
            creiss Christian Reiss
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support