Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5192 undefined method `[]' for Puppet::Transaction::Event with certain reports Change By: Julien Pivotto Comment: I have attached all the files of the gist in this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5192 undefined method `[]' for Puppet::Transaction::Event with certain reports Change By: Julien Pivotto When Calling the function "YAML.load_file(path)" with a yaml file where a resource_statuses: member has events: non-empty, we get a "undefined method `[]' for #" error.See attached files and gist. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Julien Pivotto assigned an issue to Henrik Lindberg Puppet / PUP-5192 undefined method `[]' for Puppet::Transaction::Event with certain reports Change By: Julien Pivotto Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5193) Support hashing of sshkey hostnames
Title: Message Title Jan Örnstedt created an issue Puppet / PUP-5193 Support hashing of sshkey hostnames Issue Type: New Feature Affects Versions: PUP 3.6.2 Assignee: Unassigned Created: 2015/09/03 7:54 AM Environment: ssh Priority: Normal Reporter: Jan Örnstedt I modern versions of openssh hashing of the hostnames in the known_host files is supported. This prevents exposure of hostnames in case a system gets broken in to. One can easily convert a file with the command ssh-keygen -H -f known_hosts_file. Syntax differs slightly from standard format. One hostname per line and change from ',' to '|' as separators. Add Comment
Jira (PUP-5193) Support hashing of sshkey hostnames
Title: Message Title
Jan Örnstedt commented on PUP-5193
Re: Support hashing of sshkey hostnames
{{# Original format test001.foo.bar,test001,192.168.6.2 ssh-rsa KEY1 test002.foo.bar,test002,puppet,192.168.2.112 ssh-rsa KEY2 test003.foo.bar,test003,192.168.6.4 ssh-rsa KEY3 test004.foo.bar,test004,192.168.4.70 ssh-rsa KEY4}}
{{# New format
1
v3iPyExlUULgqexvUA8EB3CtcAI=
f3V+/Eh/ZROz8JiCma5Hoxp3e6E= ssh-rsa KEY1
1
N5YndxRA6ktBQ4s+ES/PAtYAAtk=
+rQl7OeQpCemAJDk8tJ0+VfnKP0= ssh-rsa KEY1
1
CJOdrHQ0tw33nkWSmq5hqSKPU0c=
Dx6ezAfXi5xq1XbC/PuBT3n1YCY= ssh-rsa KEY1
1
JUWFiiP2gugzc0Sy522/803UAnY=
l338IZ8o8wER4x6E1OdRv8SoBPw= ssh-rsa KEY2
1
XPLNGHtMf2+f4b6+3panMHo++a0=
oxOA0B6/Q90oG18KqWasZ/pOML0=
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-5192 undefined method `[]' for Puppet::Transaction::Event with certain reports Change By: Julien Pivotto Attachment: test.yaml Attachment: test.rb Attachment: RESULT Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title
Julien Pivotto updated an issue
Puppet / PUP-5192
undefined method `[]' for Puppet::Transaction::Event with certain reports
Change By:
Julien Pivotto
When Calling the function {color:#205081} "YAML.load_file(path)" {color} with a yaml file where a {color:#59afe1} resource_statuses: member {color} has {color:#d04437} events: {color} non-empty, we get a {color:#d04437} "undefined method `[]' for # {color} " error.See attached files and gist.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Julien Pivotto commented on PUP-5192 Re: undefined method `[]' for Puppet::Transaction::Event with certain reports I have attached all the files of the gist in this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Julien Pivotto assigned an issue to Unassigned Puppet / PUP-5192 undefined method `[]' for Puppet::Transaction::Event with certain reports Change By: Julien Pivotto Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5193) Support hashing of sshkey hostnames
Title: Message Title Jan Örnstedt updated an issue Puppet / PUP-5193 Support hashing of sshkey hostnames Change By: Jan Örnstedt I In modern versions of openssh hashing of the hostnames in the known_host files is supported. This prevents exposure of hostnames in case a system gets broken in to.One can easily convert a file with the command ssh-keygen -H -f known_hosts_file.Syntax differs slightly from standard format.One hostname per line and change from ',' to '|' as separators. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Henrik Lindberg commented on PUP-5192 Re: undefined method `[]' for Puppet::Transaction::Event with certain reports From the gist: /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/event.rb:40:in `initialize_from_hash': undefined method `[]' for # (NoMethodError) Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5099) Include code_id in environment catalog
Title: Message Title David Lutterkort updated an issue Puppet / PUP-5099 Include code_id in environment catalog Change By: David Lutterkort Summary: Include catalog_id code_id in environment catalog Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5194) Investigate CI failures Sept 3 re puppetserver not starting
Title: Message Title Kylo Ginsberg commented on PUP-5194 Re: Investigate CI failures Sept 3 re puppetserver not starting First pass triage: These failures are because puppetserver isn't starting. That appears to be because jruby can't find puppet. I think that's because puppet is being installed differently (site_ruby vs vendor_ruby). Matthaus Owens give me a ping and I can share what I've figured out so far (which is not much clearer than the above ) Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5099) Include code_id in environment catalog
Title: Message Title
David Lutterkort updated an issue
Puppet / PUP-5099
Include code_id in environment catalog
Change By:
David Lutterkort
The environment compiler needs to put the {{ catalog_id code_id }} from which the environment catalog was compiled into the environment catalog.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5081) CapabilityFinder needs to look up capabilities by code_id
Title: Message Title
David Lutterkort updated an issue
Puppet / PUP-5081
CapabilityFinder needs to look up capabilities by code_id
Change By:
David Lutterkort
This avoids a scenario When we look up consumed resources in which PuppetDB , without direct puppet, agents could naturally run in we need to restrict the wrong order.Produced capability resources will have associated code_ids and consumed resources will only be satisfied query by resources with {{code_id}} to make sure we do not find the same code_id. This means that if capability produced in a new previous, outdated version of the code as that would confuse us when the production of a resource is pushed and moved from one node to another.When {{Puppet::Resource::Catalog#resource}} uses the consuming agent requests its new catalog before the producing agent {{CapabilityFinder}} to look up consumed capabilities , it will fail compilation needs to pass {{code_id}} to it, and apply {{CapabilityFinder}} needs to add it to its cached catalog, so that changes won't happen out of order PuppetDB query .
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5074) Support consume/produces annotations in site-wide manifest
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5074 Support consume/produces annotations in site-wide manifest Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: AM Tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5075) classes within a modules namespace cannot be used to produce capabilities
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5075 classes within a modules namespace cannot be used to produce capabilities Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: AM Tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5079) Check that the 'nodes' parameter for application instances is sound
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5079 Check that the 'nodes' parameter for application instances is sound Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: AM Tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5088) Produces/consumes mapping: make sure we only allow '=>' in the notation
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5088 Produces/consumes mapping: make sure we only allow '=>' in the notation Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: AM Tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5192 undefined method `[]' for Puppet::Transaction::Event with certain reports Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5126) Feature Request - Ability to extract an array or hash of values from collected resources - or make resource collections enumerable
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5126 Feature Request - Ability to extract an array or hash of values from collected resources - or make resource collections enumerable Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4697) Puppet service provider for SuSE should default to systemd except for version 11
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-4697 Puppet service provider for SuSE should default to systemd except for version 11 Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1221) Memory fact failing in SPARC Solaris with "kstat_read - permission denied"
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1221 Memory fact failing in SPARC Solaris with "kstat_read - permission denied" Change By: Michael Smith Status: Ready for CI Test Assignee: William Hopper qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Josh Cooper commented on PUP-5192 Re: undefined method `[]' for Puppet::Transaction::Event with certain reports Nicholas Fagerlund I think this is the issue you ran into the other day Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1185) Add node definition for Solaris 11 (SPARC, i386) to Facter
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1185 Add node definition for Solaris 11 (SPARC, i386) to Facter Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-428) Add node definition for Solaris 10 to Hiera
Title: Message Title Michael Smith assigned an issue to qa Hiera / HI-428 Add node definition for Solaris 10 to Hiera Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5133) Add node definition for Solaris 11 (SPARC, i386) to Puppet
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5133 Add node definition for Solaris 11 (SPARC, i386) to Puppet Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5196) puppet module tool validates the wrong directory when used w/ --environment
Title: Message Title Alexander Johnson assigned an issue to Anderson Mills Puppet / PUP-5196 puppet module tool validates the wrong directory when used w/ --environment Change By: Alexander Johnson Assignee: Anderson Mills Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5078) Check that resource refs in export/consume are capability resources
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5078 Check that resource refs in export/consume are capability resources Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: AM Tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5043) Allow marking types as capabilities
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5043 Allow marking types as capabilities Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: AM Tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5033) Parse 'application', 'consume', and 'produce'
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5033 Parse 'application', 'consume', and 'produce' Change By: Steve Barlow Scope Change Category: Adopted Scope Change Reason: AM Tickets Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1222) Operatingsystemrelease incorrect in SPARC Solaris 10
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1222 Operatingsystemrelease incorrect in SPARC Solaris 10 Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1223) Extend Solaris acceptance facts test to validate SPARC
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1223 Extend Solaris acceptance facts test to validate SPARC Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5193) Support hashing of sshkey hostnames
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5193 Support hashing of sshkey hostnames Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5196) puppet module tool validates the wrong directory when used w/ --environment
Title: Message Title Alexander Johnson updated an issue Puppet / PUP-5196 puppet module tool validates the wrong directory when used w/ --environment Change By: Alexander Johnson Sprint: CODEMGMT 2015-09-23 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5196) puppet module tool validates the wrong directory when used w/ --environment
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5196 puppet module tool validates the wrong directory when used w/ --environment I assigned this one to the code management scrum team. /cc Adrien Thebo, Alex Dreyer, Alexander Johnson. Change By: Kylo Ginsberg Scrum Team: Code Management Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4890) Add code_id to catalog
Title: Message Title
David Lutterkort updated an issue
Puppet / PUP-4890
Add code_id to catalog
Change By:
David Lutterkort
The compiler terminus should add the current {{code_id}} to the catalog it produces. The {{code_id}} should be serialized over the wire. Also update the catalog schema and api docs. The clojure catalog endpoint will need to make the {{code_id}} available to the compiler, either by including it in the request options hash or by registering a callback so ruby can lookup the value. The {{code_id}} also needs to be available as an attribute of the {{catalog}} object that gets passed through the evaluator.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1221) Memory fact failing in SPARC Solaris with "kstat_read - permission denied"
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-1221 Memory fact failing in SPARC Solaris with "kstat_read - permission denied" Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5194) Investigate CI failures Sept 3 re puppetserver not starting
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-5194 Investigate CI failures Sept 3 re puppetserver not starting Issue Type: Task Assignee: Kylo Ginsberg Created: 2015/09/03 9:15 AM Priority: Normal Reporter: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1953) PE Module can't deal with multiple PDB instances
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-1953 PE Module can't deal with multiple PDB instances Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5196) puppet module tool validates the wrong directory when used w/ --environment
Title: Message Title Ben Ford created an issue Puppet / PUP-5196 puppet module tool validates the wrong directory when used w/ --environment Issue Type: Bug Assignee: Unassigned Components: PMT Created: 2015/09/03 10:21 AM Priority: Normal Reporter: Ben Ford When installing to an environment, puppet module tool validates the $basemodulepath instead of the correct environment directory. root@puppetfactory:/etc/puppetlabs/code/environments # puppet module install puppetlabs/motd --environment binford2k Notice: Preparing to install into /etc/puppetlabs/code/environments/binford2k/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ...
Jira (FACT-1172) invalid byte sequence in UTF-8 for disk UUID
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Facter / FACT-1172 invalid byte sequence in UTF-8 for disk UUID Change By: Shaigy Nixon Assignee: qa Shaigy Nixon Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5081) CapabilityFinder needs to look up capabilities by code_id
Title: Message Title David Lutterkort updated an issue Puppet / PUP-5081 CapabilityFinder needs to look up capabilities by code_id Change By: David Lutterkort Summary: associate capability resources in PuppetDB with specific CapabilityFinder needs to look up capabilities by code_id Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5195) How to verify memory allocation of my puppetmaster (V3.8.2)
Title: Message Title Kylo Ginsberg assigned an issue to ankit Puppet / PUP-5195 How to verify memory allocation of my puppetmaster (V3.8.2) Change By: Kylo Ginsberg Assignee: Melissa Stone ankit Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5195) How to verify memory allocation of my puppetmaster (V3.8.2)
Title: Message Title Kylo Ginsberg commented on PUP-5195 Re: How to verify memory allocation of my puppetmaster (V3.8.2) ankit in that snippet above you're running the ruby puppet master which doesn't use JAVA_ARGS. You may be wanting to run the puppetserver which is the clojure implementation and does use JAVA_ARGS. Read more here: http://docs.puppetlabs.com/puppetserver/1.1/ You also might ask on IRC or the puppet-users google group for more interactive help. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5194) Investigate CI failures Sept 3 re puppetserver not starting
Title: Message Title Matthaus Owens commented on PUP-5194 Re: Investigate CI failures Sept 3 re puppetserver not starting Kylo GinsbergI'm pretty sure this is due to the master->stable merge yesterday. There are 2 commits that weren't on puppet stable that affect install.rb behavior (and add a flag). It looks as though install.rb stops parsing flags once it finds a flag it doesn't recognize, and because --no-check-prereqs appears before the --siteruby flag, it is not honored. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5195) How to verify memory allocation of my puppetmaster (V3.8.2)
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-5195 How to verify memory allocation of my puppetmaster (V3.8.2) Change By: Kylo Ginsberg Workflow: Release Engineering Scrum Team Workflow Key: CPR PUP - 216 5195 Project: Community Package Repository Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5197) app_management feature switch has no effect when running under puppet-server
Title: Message Title David Lutterkort created an issue Puppet / PUP-5197 app_management feature switch has no effect when running under puppet-server Issue Type: Bug Assignee: Unassigned Created: 2015/09/03 2:13 PM Priority: Normal Reporter: David Lutterkort When running the master under puppet-server, setting app_management in puppet.conf has no effect, because Puppet::Pops::Parser::Lexer2 is loaded before Puppet[:app_management] has been properly initialized. Therefore, the lexer always behaves as if app mgmt was turned off. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5124) Puppet does not wait for resources before parsing provider
Title: Message Title Kylo Ginsberg assigned an issue to Piotr Bugała Puppet / PUP-5124 Puppet does not wait for resources before parsing provider Change By: Kylo Ginsberg Assignee: Piotr Bugała Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5124) Puppet does not wait for resources before parsing provider
Title: Message Title Kylo Ginsberg commented on PUP-5124 Re: Puppet does not wait for resources before parsing provider Piotr Bugała if I understand what you're doing here, I believe a common pattern here is to create a feature predicated on the presence of the binary, and confine the provider to that feature. This will take two puppet runs: one in which the binary is installed (and the provider you're interested does not run because it's confine isn't met) and a second run where the provider can run. You might also ask on the puppet-users group or on IRC for other ways to solve this problem. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5173) puppet 3.8.3 2015-09-16 Release
Title: Message Title Kylo Ginsberg commented on PUP-5173 Re: puppet 3.8.3 2015-09-16 Release Melissa Stone, Nicholas Fagerlund, Hailee Kenney, Henrik Lindberg, Steve Barlow: after talking to a few of you I'm nominating Sept 16th. If that doesn't work for you chime in here. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5173) puppet 3.8.3 2015-09-16 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5173 puppet 3.8.3 2015-09-16 Release Change By: Kylo Ginsberg puppet 3.8.3 2015-09- 09 16 ReleaseWhen working through this ticket, add it to the board and then keep it in the Ready for Engineering column.Move the subtasks to In Progress when you are working on them and Resolved when you have completed them.In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. * The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. * Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. * When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5192) undefined method `[]' for Puppet::Transaction::Event with certain reports
Title: Message Title Nicholas Fagerlund commented on PUP-5192 Re: undefined method `[]' for Puppet::Transaction::Event with certain reports Yup, that's the one. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1226) Create AIX facts acceptance test
Title: Message Title Michael Smith created an issue Facter / FACT-1226 Create AIX facts acceptance test Issue Type: Task Assignee: Unassigned Created: 2015/09/03 12:53 PM Fix Versions: FACT 3.1.0 Priority: Normal Reporter: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are
Jira (FACT-631) operatingsystemmajrelease does not work on Solaris
Title: Message Title Michael Smith commented on FACT-631 Re: operatingsystemmajrelease does not work on Solaris We should probably verify this in Facter 3.1.0 and close it. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4683) repair winrm/winrm-fs gem
Title: Message Title Alice Nodelman commented on PUP-4683 Re: repair winrm/winrm-fs gem Ethan Brown, Ryan Gard and I have determined to call this a miss for now. We will be moving forward with a different ssh transport for cygwinless windows template construction. Removing 'blocking' state. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5024) Acceptance: validate "enable=true ensure=running" works on service masked by systemd
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5024 Acceptance: validate "enable=true ensure=running" works on service masked by systemd Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5197) app_management feature switch has no effect when running under puppet-server
Title: Message Title
David Lutterkort updated an issue
Puppet / PUP-5197
app_management feature switch has no effect when running under puppet-server
Change By:
David Lutterkort
When running the master under puppet-server, setting {{app_management}} in {{puppet.conf}} has no effect, because {{Puppet::Pops::Parser::Lexer2}} is loaded before {{Puppet[:app_management]}} has been properly initialized. Therefore, the lexer always behaves as if app mgmt was turned off. The proximate cause for this is that puppet-server's {{puppet/server/master.rb}}, which is loaded as one of the first things when a JRuby container is initialized, loads {{puppet/info_service}} before loading the Puppet config. The {{info_service}} in turn instantiates a compiler, and things go sideways from there.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1172) invalid byte sequence in UTF-8 for disk UUID
Title: Message Title Shaigy Nixon commented on FACT-1172 Re: invalid byte sequence in UTF-8 for disk UUID Validated on redhat-6-x86_64 with facter --version 3.0.2 (commit 532d5242a61a803953abdd57b3d0f7bc68f447c0): Steps followed: 1) On agent, modify the the label on one of the block devices. [root@kttki3p2lxbxi25 ~]# blkid /dev/sda1: UUID="eb475619-f4b3-41af-91ca-b37fec3374d7" TYPE="ext4" /dev/sda2: UUID="wVL1i1-l6QX-pl33-9m55-KJ6S-sX2k-KI3JAE" TYPE="LVM2_member" /dev/sdb1: UUID="7o1inr-VPe2-Uqi8-bIlW-JQWS-u2M6-wZQbST" TYPE="LVM2_member" /dev/mapper/VolGroup-lv_root: UUID="22709047-0ea7-4424-9ffd-3c54eba2f514" TYPE="ext4" /dev/mapper/VolGroup-lv_swap: UUID="3e258a40-f1ee-4afa-8462-e5f49b0ffa5f" TYPE="swap" [root@kttki3p2lxbxi25 ~]# e2label /dev/sda1 "€†Ã€M€†Ã€M" Warning: label too long, truncating.
Jira (FACT-631) operatingsystemmajrelease does not work on Solaris
Title: Message Title
William Hopper commented on FACT-631
Re: operatingsystemmajrelease does not work on Solaris
Verified in stable (3.1.0):
Solaris 10:
operatingsystem => Solaris
operatingsystemmajrelease => 10
operatingsystemrelease => 10_u10
os => {
architecture => "sun4v",
family => "Solaris",
hardware => "sun4v",
name => "Solaris",
release => {
full => "10_u10",
major => "10",
Jira (PUP-5011) Helper methods for enumerating manifest files in environments
Title: Message Title Christopher Price commented on PUP-5011 Re: Helper methods for enumerating manifest files in environments Yes, the API would just give us the current values of all of the settings from the environment.conf file, presumably including the full modulepath. Then the autoloader logic for determining which files to consider as candidates for parsing would be duplicated in Clojure and give us much more control over how we interact with the Ruby APIs. I agree with Henrik Lindberg's suggestion that a prereq for this would be to document a specification for defining which files are parsed, but assuming we had that, and that it wasn't insanely complex? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5102) Define minimum version for a package
Title: Message Title Andreas Wilke commented on PUP-5102 Re: Define minimum version for a package Kylo Ginsberg didn't know that versioning is such a complex topic and not all packages are using semver which makes it indeed hard to use it for all packages. But what if we implement this with a note to use it with caution that this should only be used for packages where version compare works fine? Why shouldn't we not support it? The customer reported it would really help him and could make his life easier to manage thousands of systems and hundreds of packages where it is almost impossible to get each node and each package installed to the same version level. This is a day to day battle for operations which doesn't always make sense to update productive systems only because there is a new version available. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1154) $::rubysitedir pointing to wrong directory.
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Facter / FACT-1154 $::rubysitedir pointing to wrong directory. Change By: Shaigy Nixon Assignee: qa Shaigy Nixon Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1222) Operatingsystemrelease incorrect in SPARC Solaris 10
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1222 Operatingsystemrelease incorrect in SPARC Solaris 10 Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5197) app_management feature switch has no effect when running under puppet-server
Title: Message Title David Lutterkort updated an issue Puppet / PUP-5197 app_management feature switch has no effect when running under puppet-server When trying to run the HEAD of the Puppet master repo against the HEAD of the puppet-server repo, ran across this bug. Change By: David Lutterkort Scope Change Category: Found Story Points: 1 Scrum Team: Application Management Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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
Jira (PUP-5197) app_management feature switch has no effect when running under puppet-server
Title: Message Title David Lutterkort updated an issue Puppet / PUP-5197 app_management feature switch has no effect when running under puppet-server Change By: David Lutterkort Sprint: AM 2015-09-09 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5191) Investigate Puppet acceptance failures on Solaris 10 x86_64
Title: Message Title Michael Smith updated an issue Puppet / PUP-5191 Investigate Puppet acceptance failures on Solaris 10 x86_64 Change By: Michael Smith Security: Internal Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4820) osx curl with client certs causes puppet acceptance test to segfault
Title: Message Title Michael Smith commented on PUP-4820 Re: osx curl with client certs causes puppet acceptance test to segfault Is this test worth running on OSX? Solaris also fails it because we don't ship the curl command in AIO. However this test only curls the master, nothing being tested agent-side. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4697) Puppet service provider for SuSE should default to systemd except for version 11
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Puppet / PUP-4697 Puppet service provider for SuSE should default to systemd except for version 11 Change By: Shaigy Nixon Assignee: qa Shaigy Nixon Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5191) Investigate Puppet acceptance failures on Solaris 10 x86_64
Title: Message Title Michael Smith commented on PUP-5191 Re: Investigate Puppet acceptance failures on Solaris 10 x86_64 Solaris 10 doesn't have the stat utility, but it's supposed to be available on the Solaris 10 install media. Can we get that installed? Heath Seals Solaris 11 already has it. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4757) Update pre-suites to install puppet-agent on "pe" platforms
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4757 Update pre-suites to install puppet-agent on "pe" platforms Change By: Kylo Ginsberg Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5013) Improve the code for profiling resource evaluation?
Title: Message Title Kylo Ginsberg commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Christopher Price: I don't know the usual ticket flow for Server. This is in Ready for Test but not in a sprint - would someone from QA usually test this? Or ...? Either way, we're planning to release with this (4.2.2 first) on/around 9/9 so please advise on what we need to do next with this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1222) Operatingsystemrelease incorrect in SPARC Solaris 10
Title: Message Title John Duarte commented on FACT-1222 Re: Operatingsystemrelease incorrect in SPARC Solaris 10 Using puppet-agent-1.2.3.251.ga38600c.sparc.pkg.gz, the correct result is now returned. -bash-3.2# uname -a SunOS sol10 5.10 Generic_147440-01 sun4v sparc SUNW,SPARC-Enterprise-T5120 -bash-3.2# facter operatingsystemrelease 10_u10 -bash-3.2# facter --version 3.0.2 (commit 369f809c858c82c633ddb7ec18c47e04c149d561) Add Comment
Jira (PUP-5197) app_management feature switch has no effect when running under puppet-server
Title: Message Title Henrik Lindberg commented on PUP-5197 Re: app_management feature switch has no effect when running under puppet-server merged to master at: 25b5061 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5024) Acceptance: validate "enable=true ensure=running" works on service masked by systemd
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5024 Acceptance: validate "enable=true ensure=running" works on service masked by systemd Change By: Kylo Ginsberg Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4605) With a systemd masked service: 'enable=true ensure=running' doesn't work
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4605 With a systemd masked service: 'enable=true ensure=running' doesn't work Change By: Kylo Ginsberg Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5018) Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist
Title: Message Title Kylo Ginsberg commented on PUP-5018 Re: Puppet::FileSystem.unlink fails on Windows when the target path doesn't exist Rob Reynolds can you update the two release notes fields for this ticket? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1223) Extend Solaris acceptance facts test to validate SPARC
Title: Message Title John Duarte commented on FACT-1223 Re: Extend Solaris acceptance facts test to validate SPARC Confirmed on both Solaris 10 and 11 SPARC with facter at version 3.0.2 (commit 369f809c858c82c633ddb7ec18c47e04c149d561) Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5197) app_management feature switch has no effect when running under puppet-server
Title: Message Title David Lutterkort assigned an issue to David Lutterkort Puppet / PUP-5197 app_management feature switch has no effect when running under puppet-server Change By: David Lutterkort Assignee: David Lutterkort Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1221) Memory fact failing in SPARC Solaris with "kstat_read - permission denied"
Title: Message Title
John Duarte commented on FACT-1221
Re: Memory fact failing in SPARC Solaris with "kstat_read - permission denied"
On Sol 10 SPARC
-bash-3.2# facter --version
3.0.2 (commit 369f809c858c82c633ddb7ec18c47e04c149d561)
-bash-3.2# uname -a
SunOS sol10 5.10 Generic_147440-01 sun4v sparc SUNW,SPARC-Enterprise-T5120
-bash-3.2# facter memory
{
swap => {
available => "2.00 GiB",
available_bytes => 2147475456,
capacity => "0%",
Jira (PUP-5131) Get pre-suites working for Solaris 10 for Puppet
Title: Message Title John Duarte commented on PUP-5131 Re: Get pre-suites working for Solaris 10 for Puppet Successfully tested against SPARC Command (from acceptance directory of puppet stable) SHA=bd98fdd74b51eba26a76dcb2fd2d3afc0fc3596c SUITE_VERSION=1.2.3.230.gbd98fdd RUBYLIB=./lib bundle exec beaker --hosts config/nodes/solaris-10-sparc.yaml --options config/aio/options.rb --preserve-hosts always --tests tests/ensure_puppet-agent_paths.rb Results of pre-suite Test Suite: pre_suite @ 2015-09-03 16:14:33 -0700 - Host Configuration Summary - - Test Case Summary for suite 'pre_suite' - Total Suite Time: 204.19 seconds
Jira (PUP-5097) Hostname and Domain as trusted facts
Title: Message Title Henrik Lindberg commented on PUP-5097 Re: Hostname and Domain as trusted facts On the PR, Nicholas Fagerlund brings up that not all certnames are constructed to contain hostname and domain. By doing it the way it is now merged can be misconstrued as actual trusted information about a hostname and domain, when it in fact is just parts of the name of a certificate which could have been constructed with a name that does not contain those actual pieces of information. Because of this, we may want to rethink the design. At least relabel the values to something that makes it obvious that they are an interpretation based on what is in the certname. A user would have to know how they are naming certs. Ideally the concept would be open ended, just giving access to the parts of the certname - but then it becomes difficult to piece them together - domain can be more than one part. (There is no way to say - the rest of an array with dots between) in the hiera 'dot notation'). Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4697) Puppet service provider for SuSE should default to systemd except for version 11
Title: Message Title
Shaigy Nixon commented on PUP-4697
Re: Puppet service provider for SuSE should default to systemd except for version 11
Validated with puppet-agent SHA:39d88481cc2d0f9a4b1d6036b572861a0a891b27 On SLES-11-x86_64:
er00r4b4m4g1xox:/tmp # cat /etc/issue
Welcome to SUSE Linux Enterprise Server 11 SP3 (x86_64) - Kernel \r (\l).
er00r4b4m4g1xox:/tmp # /opt/puppetlabs/bin/puppet --version
4.2.1
er00r4b4m4g1xox:/tmp # /opt/puppetlabs/bin/puppet apply -e 'package {"apache2" : ensure => "present" }'
Notice: Compiled catalog for er00r4b4m4g1xox.delivery.puppetlabs.net in environment production in 0.75 seconds
Notice: /Stage[main]/Main/Package[apache2]/ensure: created
Notice: Applied catalog in 2.27 seconds
Jira (FACT-1221) Memory fact failing in SPARC Solaris with "kstat_read - permission denied"
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1221 Memory fact failing in SPARC Solaris with "kstat_read - permission denied" Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5134) Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet
Title: Message Title John Duarte commented on PUP-5134 Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet Successfully tested against SPARC Solaris 11 Command (as run from acceptance directory of puppet stable) SHA=bd98fdd74b51eba26a76dcb2fd2d3afc0fc3596c SUITE_VERSION=1.2.3.230.gbd98fdd RUBYLIB=./li b bundle exec beaker --hosts config/nodes/solaris-11-sparc.yaml --options config/aio/options.rb --preserve-hosts always --tes ts tests/ensure_puppet-agent_paths.rb Results of pre-suite Test Suite: pre_suite @ 2015-09-03 16:32:00 -0700 - Host Configuration Summary -
Jira (PUP-5097) Hostname and Domain as trusted facts
Title: Message Title Kylo Ginsberg commented on PUP-5097 Re: Hostname and Domain as trusted facts Re-opening this to reflect ongoing discussion. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5044) launchd enable/disable on OS X 10.10
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5044 launchd enable/disable on OS X 10.10 Change By: Kylo Ginsberg Release Notes Summary: On OS X 10.10 enable / disable of services did not work due to a change in the location of the overrides plist. This updates the logic to use the new location used by 10.10+. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5044) launchd enable/disable on OS X 10.10
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5044 launchd enable/disable on OS X 10.10 Change By: Kylo Ginsberg Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4605) With a systemd masked service: 'enable=true ensure=running' doesn't work
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4605 With a systemd masked service: 'enable=true ensure=running' doesn't work Change By: Kylo Ginsberg Release Notes Summary: With a systemd masked service the combination of the enable=true and ensure=running attributes did not work, although using them serially would work. This fix addresses that use case. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5013) Improve the code for profiling resource evaluation?
Title: Message Title Kylo Ginsberg commented on PUP-5013 Re: Improve the code for profiling resource evaluation? Also I snipped / tweaked the commit summary for use as Release Notes Summary. Feel free to hack on that further. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5013) Improve the code for profiling resource evaluation?
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5013 Improve the code for profiling resource evaluation? Change By: Kylo Ginsberg Release Notes Summary: When surfacing Puppet metrics in Puppet Server, w/o this change, a huge percentage of the metrics related to resource evaluation are never registered / tracked, because there are multiple code paths that can lead to resource evaluation during compilation, and only one of them has a profiling block around it.E.g. whether or not a resource gets metrics tracked may depend on whether it was introduced via NC vs site.pp, etc.This fix to the profiling code provides much more interesting and complete data to look at. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5013) Improve the code for profiling resource evaluation?
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5013 Improve the code for profiling resource evaluation? Change By: Kylo Ginsberg Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5195) How to verify memory allocation of my puppetmaster (V3.8.2)
Title: Message Title Kylo Ginsberg commented on PUP-5195 Re: How to verify memory allocation of my puppetmaster (V3.8.2) ankit there are two ways to run the puppet master: a ruby implementation and a clojure implementation. Your snippet shows that you're running the ruby implementation. Your questions are about the clojure implementation. To run the clojure implementation, I recommend reading the docs at the link I gave above. Hope this helps! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5198) Disallow file_line for managed files
Title: Message Title Lindsey Smith moved an issue Puppet / PUP-5198 Disallow file_line for managed files Change By: Lindsey Smith Key: ENTERPRISE PUP - 800 5198 Project: Puppet Enterprise Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5198) Disallow file_line for managed files
Title: Message Title Lindsey Smith commented on PUP-5198 Re: Disallow file_line for managed files Moved this ticket from ENTERPRISE to PUP project. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5198) Disallow file_line for managed files
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-5198 Disallow file_line for managed files Change By: Lindsey Smith Affects Version/s: PUP 3.8.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5195) How to verify memory allocation of my puppetmaster (V3.8.2)
Title: Message Title ankit assigned an issue to Jeremy Barlow Puppet / PUP-5195 How to verify memory allocation of my puppetmaster (V3.8.2) Change By: ankit Assignee: ankit Jeremy Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4865) Package resources no longer fail with bad names on EL5
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4865 Package resources no longer fail with bad names on EL5 Change By: Kylo Ginsberg Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4865) Package resources no longer fail with bad names on EL5
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4865 Package resources no longer fail with bad names on EL5 Change By: Kylo Ginsberg Release Notes Summary: On Red Hat Enterprise Linux 5, there was a regression wherein package resources with bad names (which should fail) were not failing. This fix restores the correct behavior which is to fail the catalog application. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5173) puppet 3.8.3 2015-09-16 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5173 puppet 3.8.3 2015-09-16 Release Change By: Kylo Ginsberg Summary: puppet 3.8.3 2015-09- 09 16 Release Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
