Jira (FACT-2891) Facter 4.0.46 (from puppet 7) breaks virtual flag

17 views
Skip to first unread message

Christian Reiss (Jira)

unread,
Dec 8, 2020, 1:24:04 AM12/8/20
to puppe...@googlegroups.com
Christian Reiss created an issue
 
Facter / Bug FACT-2891
Facter 4.0.46 (from puppet 7) breaks virtual flag
Issue Type: Bug Bug
Affects Versions: FACT 4.0.44
Assignee: Unassigned
Components: Facter 4
Created: 2020/12/07 10:23 PM
Environment:
  • Tested in similar Systems running CentOS 7,
  • Puppet-agent 7,
  • same code,
  • with above commands.

100% reproduceable.

Priority: High High
Reporter: Christian Reiss

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)

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Mihai Buzgau (Jira)

unread,
Dec 8, 2020, 3:26:03 AM12/8/20
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Sprint: ready for triage 2

Mihai Buzgau (Jira)

unread,
Dec 8, 2020, 3:26:03 AM12/8/20
to puppe...@googlegroups.com

Bogdan Irimie (Jira)

unread,
Dec 8, 2020, 3:33:03 AM12/8/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ready for triage 2 ghost-9.12
Sub-team: ghost

Kenyon Ralph (Jira)

unread,
Dec 8, 2020, 3:53:03 AM12/8/20
to puppe...@googlegroups.com
Kenyon Ralph commented on Bug FACT-2891
 
Re: Facter 4.0.46 (from puppet 7) breaks virtual flag

As a workaround, try having lspci installed (from the pciutils package on Debian), if it's not already there. I found this in https://tickets.puppetlabs.com/browse/FACT-2081?focusedCommentId=771889&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-771889 (if it's already installed, then this is a distinct bug)

Christian Reiss (Jira)

unread,
Dec 8, 2020, 4:00:09 AM12/8/20
to puppe...@googlegroups.com

Hey,

read that too. But thats no workaround as puppet always installs pciutils (which contails lspci):

[chris@zen10:~] $ rpm -qa | grep pciutils
pciutils-3.5.1-3.el7.x86_64
pciutils-libs-3.5.1-3.el7.x86_64

Oana Tanasoiu (Jira)

unread,
Dec 9, 2020, 11:11:03 AM12/9/20
to puppe...@googlegroups.com

Claire Cadman (Jira)

unread,
Dec 16, 2020, 2:58:16 PM12/16/20
to puppe...@googlegroups.com
Claire Cadman updated an issue
Change By: Claire Cadman
Labels: doc_reviewed platform_7.1
Reply all
Reply to author
Forward
0 new messages