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

xenu vs. xen0 difference not recognized by Puppet

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: FACT 3.1.0
    • Fix Version/s: FACT 3.3.0
    • Component/s: None
    • Environment:

      xen, rhel 5.11/6.7, PE 2015.2.0/2015.2.1

    • Template:
    • Story Points:
      5
    • Sprint:
      Client 2016-06-15, Client 2016-06-29
    • CS Priority:
      Reviewed
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Facter inappropriately reported Xen domU and dom0 VMs as "xen". This was a regression to Facter 2. Facter now reports the Xen domains separately as Facter 2 did.

      Description

      To manage hosts with the Xen hypervisor, customer tries to determine if it is xen0 or xenu, and Facter reports them just as "xen." Ideally for Xen, Puppet/Facter would detect whether you are a xen dom0 or a xen domU (reports xen0 and xenu respectively). Currently this is the report of the virtual fact when using the xen hypervisor.

      [root@herd-agent-06 ~]# facter virtual
      xen
      

      Per our customer this worked, that is, multiple facts were present for multiple values (xen0, xenu) of Xen in Facter 2.x.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  branan Branan Riley
                  Reporter:
                  rvdlinden Rene van der Linden
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  14 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support