Jira (FACT-1762) valid networking facts in 2.x get ignored in 3.x

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x Change By: Branan Riley Certain hiera entries which rely on calling Facter to fill values in PE 3.8 fail miserably in PE 4.8.1. We traced it to a behavior in Facter. Specifically, we found that calling the fact key of "ipaddress_eth0_1" used to return a good value in 3.8, but now returns a blank in puppet -agent  4.8.1. However, I have discovered that calling ipaddress_eth0:1 in 4.8.1 does work. I was not aware of this change until one of my teams and I found out the hard way.  To test locally, one only needs to do this (as root, on any Linux server with bonding set up): # facter ipaddress_bond0_1  (this should return a blank in 4.8.1, yet return the ip address value of bond0:1 in 3.8) # facter ipaddress_bond0:1 (this should return an ip address that corresponds to bond0:1, and this is the workaround we put into the hiera .yaml file.) (There may be documentation somewhere that already describes this, but I was unable to find it). Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x Change By: Branan Riley

Certain hiera entries which rely on calling Facter to fill values in PE 3.8 fail miserably in PE 4.8.1.

We traced it to a behavior in Facter. Specifically, we found that calling the fact key of "ipaddress_eth0_1" used to return a good value in 3.8, but now returns a blank in  puppet-agent  4.8.1. However, I have discovered that calling ipaddress_eth0:1 in 4.8.1 does work. I was not aware of this change until one of my teams and I found out the hard way.

To test locally, one only needs to do this (as root, on any Linux server with bonding set up): # facter ipaddress_bond0_1  (this should return a blank in 4.8.1, yet return the ip address value of bond0:1 in 3.8) # facter ipaddress_bond0:1 (this should return an ip address that corresponds to bond0:1, and this is the workaround we put into the hiera .yaml file.) (There may be documentation somewhere that already describes this, but I was unable to find it).

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x

Change By: Branan Riley Summary: valid networking facts in  3  2 .x get ignored in  4  3 .x

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x

Change By: Branan Riley Story Points: 3

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x

Change By: Branan Riley Sprint: Platform OS  Grooming  Ready for Eng.

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x

Change By: Branan Riley Sprint: Platform OS  Ready for Eng.  Grooming/Triage

Add Comment

This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x

Change By: Branan Riley Labels: linux networking triaged

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Jake Yip (JIRA)]

Jake Yip commented on FACT-1762

Re: valid networking facts in 2.x get ignored in 3.x In addition to alias interfaces, vlan interfaces that were munged in facter 2 are also broken in facter 3 On a Linux box, the interface name is eth0.100 facter 2: ipaddress_eth0_100 facter 3: ipaddress_eth0.100 I'm wondering if this is fixed as a by-product of fixing this bug, or should this be another bug? I can't find a bug report pointing this vlan interfaces specifically.

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Facter / FACT-1762

valid networking facts in 2.x get ignored in 3.x

Change By: Geoff Nichols Labels: breaking linux networking triaged

Add Comment

[Larissa Lane (JIRA)]

Larissa Lane commented on FACT-1762

Re: valid networking facts in 2.x get ignored in 3.x Garrett Guillotte We might need some documentation for this

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-1762

valid networking facts in 2.x get ignored in 3.x

Change By: Branan Riley Sprint: Platform OS Grooming/Triage

Add Comment

[Garrett Guillotte (JIRA)]

Garrett Guillotte updated an issue

Facter / FACT-1762 valid networking facts in 2.x get ignored in 3.x

Change By: Garrett Guillotte Component/s: DOCS

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on FACT-1762

Re: valid networking facts in 2.x get ignored in 3.x Thank you for reporting this issue. While we agree this is likely an improvement, we do not anticipate addressing this any time soon due to other issues demanding precedence. As such, this ticket will be closed as “Won’t Do”. We may revisit this at a later time, and if so, will re-open this ticket. If you are interested in submitting a patch to implement this issue, please open a pull request and re-open this ticket.

Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)