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

[Facter 2.4.5] On Virtuozzo containers "ipaddress" becomes 127.0.0.1

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: FACT 2.4.5
    • Fix Version/s: FACT 2.4.6
    • Component/s: Community
    • Labels:
      None
    • Template:
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Reverted FACT-380 to return the ipaddress fact to its previous behavior

      Description

      facter virtual
      openvz

      Facter 2.4.4:
      facter | grep "^ip"
      ipaddress => 192.168.1.171
      ipaddress_lo => 127.0.0.1
      ipaddress_venet0 => 127.0.0.1
      ipaddress_venet0_0 => 192.168.1.171
      ipaddress_venet0_1 => 192.168.1.172

      Facter 2.4.5:
      facter | grep "^ip"
      ipaddress => 127.0.0.1
      ipaddress_lo => 127.0.0.1
      ipaddress_venet0 => 127.0.0.1
      ipaddress_venet0_0 => 192.168.1.171
      ipaddress_venet0_1 => 192.168.1.172

      Didn't replicate it for Xen domU or physical nodes.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. FACT-1318 update to ipaddress fact in 2.4.5 breaks testing

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. FACT-1319 ipaddress retruns now 127.0.0.2 since facter 2.4.5

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. FACT-380 Private ipaddress is used as ipaddress fact

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              apircalabu Adi Pircalabu
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support