Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Ryan Anderson commented on PUP-6382 Re: Add "Automatic (delayed start)" as option for Service Resource on Windows Our organization is very interested in having the ability to set this startup state on Windows services. It was submitted some time ago, might some development resources be given to this? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-747) Improve Solaris $::ipaddress accuracy
Title: Message Title Ryan Anderson commented on FACT-747 Re: Improve Solaris $::ipaddress accuracy While appreciated, heroic efforts are needed to get facter3.x dependencies to compile on Solaris, making this less useful than if the fix was given to the now-abandoned facter 2.x gem which I'm still using with puppet 5.x on Solaris. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-747) Improve Solaris $::ipaddress accuracy
Title: Message Title Ryan Anderson commented on FACT-747 Re: Improve Solaris $::ipaddress accuracy Amen! Thanks Branan Riley 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 (PUP-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Ryan Anderson commented on PUP-5591 Re: undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class I think you meant to tag a different Ryan Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-747) Improve Solaris $::ipaddress accuracy
Title: Message Title Ryan Anderson created an issue Facter / FACT-747 Improve Solaris $::ipaddress accuracy Issue Type: Improvement Affects Versions: FACT 2.2.0, FACT 1.7.5 Assignee: Eric Sorenson Created: 24/Oct/14 9:49 AM Environment: Solaris 8/9/10 on SPARC, observed on numerous SPARC models Priority: Normal Reporter: Ryan Anderson On Solaris, in the ifconfig output, NICS show up as driverinstance (eg bge0, bge1, hme0, etc). In facter, the $::ipaddress fact is derived from the NIC that is alphabetically first, but this is not always accurate. For example, interface ge0 has the IP of the hostname, but bge0 may be configured for a storage or cluster network and it will show up as $::ipaddress since 'bge' comes before 'ge', even though this is wrong. Here is a real-world example of mine, ipaddress_bge0 is on a non-routable admin network and ipaddress_nxge0 is the IP of the server in DNS: ipaddress = 192.168.1.17 ipaddress_bge0 = 192.168.1.17 ipaddress_lo0 = 127.0.0.1 ipaddress_nxge0 = 10.19.1.3 ipaddress_nxge1 = 10.19.1.4 ipaddress_sppp0 = 192.168.224.3 Can the behavior be changed on Solaris so $::ipaddress equals the IP that matches the hostname?
Jira (FACT-479) Custom facts with facter 1.7.5 on AIX display facts as [fact value]
Title: Message Title Ryan Anderson created an issue Facter / FACT-479 Custom facts with facter 1.7.5 on AIX display facts as [fact value] Issue Type: Bug Affects Versions: 1.7.5 Assignee: Eric Sorenson Components: Community Created: 05/May/14 8:41 AM Environment: operating system Priority: Normal Reporter: Ryan Anderson I have a ruby custom fact that when queried with 'facter -p mysite' on AIX 6.1/7.1 displays as expected (eg TX), but if I do 'facter -p | grep mysite' it shows up like [TX]. It will show up this wrong way when it goes to puppetdb. The facter version is 1.7.5 with puppet 3.4.3, both installed via gems, on AIX with ruby 2.0.0p353. The built-in facts do not have this same issue. The custom ruby fact code is something like: Facter.add(mysite) do setcode do case Facter.value(:ipaddress) when /^10\.1\.91\.|^10\.1\.92\.|^10\.1\.93\./ TX when /^13\.1\.1\.|^13\.1\.2\./ CA end end end
