Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Thomas J Miller jr commented on FACT-1762 Re: valid networking facts in 3.x get ignored in 4.x Can't blame you a bit. And yes, there is a push to get our devs to start using structured facts. Our setup involves curated (and concatenated) tenancies (long story as to how and why) which the developers themselves ultimately control. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Branan Riley updated an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Change By: Branan Riley Sprint: Platform OS Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Branan Riley commented on FACT-1762 Re: valid networking facts in 3.x get ignored in 4.x I know we were never really happy with that munging (and we'd prefer you migrate to structured facts!), but Facter 3 was intended to be compatible with Facter 2, so I believe this is something we could take on as a bugfix in the 3.6.x series. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Branan Riley updated an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Thomas J Miller jr commented on FACT-1762 Re: valid networking facts in 3.x get ignored in 4.x Thank you for confirming that I'm still sane Please let me know of any changes/fixes that occur, though we have implemented a workaround (detailed in the description) that has equal efficacy and minimal future impact. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Michael Smith commented on FACT-1762 Re: valid networking facts in 3.x get ignored in 4.x This was likely unintentional. Facter 3 was a rewrite, and it looks like we missed how Facter 2 was munging the network interface names. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Michael Smith updated an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Change By: Michael Smith Affects Version/s: FACT 3.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1762) valid networking facts in 3.x get ignored in 4.x
Title: Message Title Thomas J Miller jr created an issue Facter / FACT-1762 valid networking facts in 3.x get ignored in 4.x Issue Type: Bug Assignee: Unassigned Created: 2017/09/22 1:37 PM Environment: Any Priority: Minor Reporter: Thomas J Miller jr 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 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
