Jira (HI-416) User defined node scope variable not available in hierarchies
Title: Message Title Lucien Boland commented on HI-416 Re: User defined node scope variable not available in hierarchies I can verify that I have tried ::nodetype and variable is still not available for hierarchy Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1437) Creating an external fact that calls `facter -p` to get the value of another external fact causes a fork bomb
Title: Message Title Nick Walker created an issue Facter / FACT-1437 Creating an external fact that calls `facter -p` to get the value of another external fact causes a fork bomb Issue Type: Bug Assignee: Unassigned Created: 2016/06/08 4:56 PM Labels: tcse Priority: Normal Reporter: Nick Walker Reproduction [root@master201620-centos ~]# cat /etc/puppetlabs/facter/facts.d/test.sh #!/bin/bash
Jira (FACT-1437) Creating an external fact that calls `facter -p` to get the value of another external fact causes a fork bomb
Title: Message Title Nick Walker updated an issue Facter / FACT-1437 Creating an external fact that calls `facter -p` to get the value of another external fact causes a fork bomb Change By: Nick Walker Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1356) External facts should be able to return structured data
Title: Message Title Nate McCurdy updated an issue Facter / FACT-1356 External facts should be able to return structured data Just to clarify this, external facts already do support showing structured data. It's external executable facts that don't support structured data. Change By: Nate McCurdy Attachment: structured external fact.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1356) External facts should be able to return structured data
Title: Message Title Jeremy Adams commented on FACT-1356 Re: External facts should be able to return structured data Could use a convention like facts.yaml.sh, facts.yaml.py, facts.yaml.pl facts.json.sh, facts.json.py, facts.yaml.pl Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1356) External facts should be able to return structured data
Title: Message Title Eric Sorenson commented on FACT-1356 Re: External facts should be able to return structured data I think we can just look at the output and use a little intelligence to see whether it's json (starts with a curly brace), yaml (starts with ---) or plain key=value. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1356) External facts should be able to return structured data
Title: Message Title Eric Sorenson updated an issue Facter / FACT-1356 External facts should be able to return structured data Change By: Eric Sorenson Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6042 `puppet agent --test` does not override cached catalog behavior Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5894) Metadata terminus should return file size
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5894 Metadata terminus should return file size Change By: Kylo Ginsberg Sprint: Direct Puppet Mop Up Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6063) Short circuit file insync check if lengths are different
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6063 Short circuit file insync check if lengths are different Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6063) Short circuit file insync check if lengths are different
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6063 Short circuit file insync check if lengths are different Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5894) Metadata terminus should return file size
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5894 Metadata terminus should return file size Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5714) Add a 'git' checksum type for file resource sources
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5714 Add a 'git' checksum type for file resource sources Change By: Kylo Ginsberg Sprint: Direct Puppet Mop Up Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6063) Short circuit file insync check if lengths are different
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6063 Short circuit file insync check if lengths are different Change By: Kylo Ginsberg Sprint: Direct Puppet Mop Up Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6042 `puppet agent --test` does not override cached catalog behavior Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5894) Metadata terminus should return file size
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5894 Metadata terminus should return file size Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5714) Add a 'git' checksum type for file resource sources
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5714 Add a 'git' checksum type for file resource sources Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6042 `puppet agent --test` does not override cached catalog behavior Change By: Kylo Ginsberg Sprint: Direct Puppet Mop Up Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5714) Add a 'git' checksum type for file resource sources
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5714 Add a 'git' checksum type for file resource sources Change By: Kylo Ginsberg Sprint: PCP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1436) Spike a sample facter.conf syntax for consumption by CPP-Hocon
Title: Message Title Branan Riley updated an issue Facter / FACT-1436 Spike a sample facter.conf syntax for consumption by CPP-Hocon Change By: Branan Riley Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1436) Spike a sample facter.conf syntax for consumption by CPP-Hocon
Title: Message Title Branan Riley updated an issue Facter / FACT-1436 Spike a sample facter.conf syntax for consumption by CPP-Hocon Change By: Branan Riley Sprint: Client 2016-07-13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1436) Spike a sample facter.conf syntax for consumption by CPP-Hocon
Title: Message Title Eric Sorenson created an issue Facter / FACT-1436 Spike a sample facter.conf syntax for consumption by CPP-Hocon Issue Type: Story Assignee: Unassigned Created: 2016/06/08 3:32 PM Priority: Normal Reporter: Eric Sorenson One of the first consumers of the CPP-Hocon work will be the proposed facter.conf. There's a lively discussion on the mailing list here: https://groups.google.com/d/topic/puppet-dev/bebmBUyRETg/discussion And a draft Puppet RFC here: https://docs.google.com/document/d/1xlj0NYESLHNv5ZO_NJ-1fCssAWzaHsTZIhyaK3uzHQY/edit It'd be helpful to ground the conversation with a proposal for syntax, PLUS this would give a solid example of a consumer for the C++ Hocon parser. So let's work to knock together a sample syntax, just drafting stuff in the google doc, and see what it to takes to get it parsed and usable by facter. Add Comment
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Eric Sorenson commented on FACT-718 Re: Allow for disabling certain facts within Facter There's an ongoing thread on the puppet-dev list about this: https://groups.google.com/d/topic/puppet-dev/bebmBUyRETg/discussion Could the watchers on this ticket take a minute to read through that and chime in if there's anything that seems wrong and/or crazy there? Alternately, a +1 with info about your must-have use cases would be super helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6395) file type documentation does not have quotes around modes in doc comments
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6395 file type documentation does not have quotes around modes in doc comments Issue Type: Bug Assignee: Unassigned Created: 2016/06/08 3:23 PM Priority: Normal Reporter: Henrik Lindberg The file resource type has several mentions of various modes without showing them as quoted strings. This is a source of confusion/error for users who take the information literally. This needs to be fixed in the file resource type source code. The end result is shown here: https://docs.puppet.com/puppet/latest/reference/type.html#file Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6375) Triage acceptance failures on zlinux (s390x) sles-11 and sles-12
Title: Message Title John Duarte updated an issue Puppet / PUP-6375 Triage acceptance failures on zlinux (s390x) sles-11 and sles-12 Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1098) Package/source should accept puppet:// files
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1098 Package/source should accept puppet:// files Ping Kylo Ginsberg Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6384 Acceptance: test that agent failover behavior works correctly Change By: Kylo Ginsberg Sprint: Client 2016 07 - 06-29 (client fail 13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6383) Acceptance: test that failover information is added to the report
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6383 Acceptance: test that failover information is added to the report Change By: Kylo Ginsberg Sprint: Client 2016 07 - 06-29 (client fail 13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6294) Add a proper 'noop' status to the report output
Title: Message Title John Duarte commented on PUP-6294 Re: Add a proper 'noop' status to the report output Chris Cowell, Steve Quin: I am putting this ticket in 'Ready to review' for you. I have validated that store based reports have the noop: true entry. Please feel free to test for your specific needs. I presume that full NM testing would be blocked by the completion of PDB-2495 implementing the consumption of this value in the PDB report terminus. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6294) Add a proper 'noop' status to the report output
Title: Message Title John Duarte updated an issue Puppet / PUP-6294 Add a proper 'noop' status to the report output Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6294) Add a proper 'noop' status to the report output
Title: Message Title John Duarte updated an issue Puppet / PUP-6294 Add a proper 'noop' status to the report output Change By: John Duarte QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6294) Add a proper 'noop' status to the report output
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6294 Add a proper 'noop' status to the report output Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1098) Package/source should accept puppet:// files
Title: Message Title Charlie Sharpsteen assigned an issue to Unassigned Puppet / PUP-1098 Package/source should accept puppet:// files Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Kylo Ginsberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet Sean Griffin I think we may have had similar-time-frame edits, but see my comment above for why I'm moving this back to Needs Information. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2367) Puppet master service dies on SIGHUP
Title: Message Title Charlie Sharpsteen assigned an issue to Unassigned Puppet / PUP-2367 Puppet master service dies on SIGHUP Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3827) Errors from indirected routes don't match error schema
Title: Message Title Justin Stoller assigned an issue to qa Puppet / PUP-3827 Errors from indirected routes don't match error schema Change By: Justin Stoller Status: Ready for CI Test Assignee: Justin Stoller qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5284) Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled
Title: Message Title Sean Griffin assigned an issue to Eric Sorenson Puppet / PUP-5284 Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled Change By: Sean Griffin Assignee: John Duarte Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Sean Griffin updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Sean Griffin Release Notes Summary: Not Needed. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte updated an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte updated an issue Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5284) Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled
Title: Message Title John Duarte updated an issue Puppet / PUP-5284 Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5284) Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5284 Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Kylo Ginsberg Assignee: qa Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Kylo Ginsberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet This was reverted at https://github.com/puppetlabs/puppet/commit/accea07e3a14f472c8a5097b2e07de41f4d46b30, while we sort out how to add support for windows, for puppetserver, and for puppetserver dev environments. Moving this to Needs Information, and assigning to myself for now. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1426) Triage acceptance failures on zlinux (s390x) sles-11
Title: Message Title Sean Griffin assigned an issue to qa Facter / FACT-1426 Triage acceptance failures on zlinux (s390x) sles-11 Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5284) Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5284 Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6385 No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6294) Add a proper 'noop' status to the report output
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6294 Add a proper 'noop' status to the report output Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PDB-2767) Document the state-overview endpoint
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2767 Document the state-overview endpoint Issue Type: Improvement Assignee: Unassigned Created: 2016/06/08 2:02 PM Priority: Normal Reporter: Wyatt Alt We've had a few users who have wanted to replicate the counts displayed in the PE dashboard for one reason or another, but we have no docs on the state-overview endpoint. We should document it and any other versioned PE endpoints we have. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-4096) Change puppet module generate skeleton to provide examples dir instead of tests
Title: Message Title Jean Bond updated an issue Puppet / PUP-4096 Change puppet module generate skeleton to provide examples dir instead of tests Change By: Jean Bond Release Notes Summary: Enhancement: Using `puppet module generate` now creates an examples directory instead of a tests directory. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4096) Change puppet module generate skeleton to provide examples dir instead of tests
Title: Message Title Jean Bond updated an issue Puppet / PUP-4096 Change puppet module generate skeleton to provide examples dir instead of tests Change By: Jean Bond Labels: docs-reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6393) /var/lib/puppet/state permission check within RPM
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6393 /var/lib/puppet/state permission check within RPM Change By: Henrik Lindberg Fix Version/s: PUP 3.8.8 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1425) Facter 3.1.7 incorrectly identifies itself as version 3.2.0
Title: Message Title Kylo Ginsberg commented on FACT-1425 Re: Facter 3.1.7 incorrectly identifies itself as version 3.2.0 Christoph Schug yeah we just internalized this last week, unfortunately shortly after 3.1.8 was tagged. So, two things: as a corrective action going forward, we're scrubbing our release sanity checks to catch this (/cc Rob Braden). meanwhile, here in tickets.puppet.com, we're essentially skipping 3.2.0. So the next release will be (and report itself as!) facter 3.3. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-2188) Debian client looking for init script even when it shouldn't be there.
Title: Message Title Joseph Yaworski commented on PUP-2188 Re: Debian client looking for init script even when it shouldn't be there. Is this ticket still valid? I can't seem to reproduce it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PDB-2766) (maint) don't execute unnecessary updates in maybe-activate-node
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2766 (maint) don't execute unnecessary updates in maybe-activate-node Issue Type: Bug Assignee: Unassigned Created: 2016/06/08 12:13 PM Priority: Normal Reporter: gepetto-bot Without this change we unnecessary lock the certname row even when we don't update anything. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2765) FIX: Unbreak on OpenBSD
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2765 FIX: Unbreak on OpenBSD Issue Type: Bug Assignee: Unassigned Created: 2016/06/08 11:26 AM Priority: Normal Reporter: gepetto-bot Seems since end of April/beginning of May, with the permission changes of puppetdb config ini files, it is broken on OpenBSD. This fixes is by setting the $puppetdb_user, and $puppetdb_group in OS specific case statements: Some more info: underprivileged users from packages start with _underscore, as well as such groups, therefore on OpenBSD, the user:group is _puppetdb:_puppetdb Because of that, instead of the single default in params.pp, move the definition of puppetdb_user and puppetdb_group into one of the OS specific case statement. As a side node not 100% related: I wonder why the config files have to be owned by the puppetdb user/group? From a security point of view, wouldn't it make more sense, to have the config files owned by root:$puppetdb_group, and permissions like 640? IIRC, puppetdb doesn't need to fiddle with the files, only read access should be fine? puppetdb is java, so the JIT requires memory regions being writable AND executable at the same time, so being a potentially valuable target for attackers. cheers, Sebastian
Jira (PUP-6394) Allow service resources to come from other code ids
Title: Message Title
Nick Lewis updated an issue
Puppet / PUP-6394
Allow service resources to come from other code ids
Change By:
Nick Lewis
In order to be more flexible around how nodes are run and whether dependencies are always respected Context from https://groups.google.com/a/puppet.com/forum/#!topic/orchestration-discuss/zbjks1faZAI{quote}Today , we should look when the master looks up service resources irrespective of in PuppetDB, it does so using code id. We should allow Puppet to lookup service resources without requiring they have It will specifically search for a matching service resource with the same code id , thus requiring that the producer node has run before the consumer and produced the "correct" service resource . In We do this to avoid the case consumer running against a soon-to-be-invalidated version of ambiguity the service resource; in particular , it should still choose we guard against the version of resource moving to a different node. If the corresponding service resource with isn't found, we fail compilation. This provides a strict guarantee that agent runs absolutely cannot happen out of order, regardless of how they're triggered.But many changes don't actually affect service resources. While we can't yet determine which changes those are, users often know. But our strict guarantee at the same compiler level prevents us from allowing them to say "trust me, I know what I'm doing".In order to enable features that put the power in the user's hands, we're proposing to prefer service resources with a matching code id , but not require them. This has two potential pitfalls: service resources could move between nodes and confuse us, and consumers could apply new code against an old service resource. For the former case, we can either find service resources by node, as we know from the environment catalog where they ought to exist, or fail only require a matching code id if there's ambiguity .For the latter case, it seems that coordination in time is as important as order. If changes that need to span multiple nodes happen over the course of 30 minutes, even if they happen in the right order, things are bound to break. It's more context: https://groups critical that consumers run immediately after the producer than that producers have run before consumers . google For that reason, the code id requirement seems insufficient . com/a/puppet If it's important that changes happen together in time, the user should use cached catalogs and coordinate change exclusively with the orchestrator . com/forum/#!topic/orchestration-discuss/zbjks1faZAI In addition to that, using service resource availability checks will help avoid breaking changes in consumers.{quote}
Jira (PUP-6394) Allow service resources to come from other code ids
Title: Message Title Nick Lewis moved an issue Puppet / PUP-6394 Allow service resources to come from other code ids Change By: Nick Lewis Component/s: DEV Component/s: DEV Key: ORCH PUP - 1386 6394 Project: Application Orchestration Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PDB-2657) Untangle the use of facter from the 2.3.x build tasks
Title: Message Title Rob Braden updated an issue PuppetDB / PDB-2657 Untangle the use of facter from the 2.3.x build tasks Change By: Rob Braden Sprint: RE Services 2016-06-15 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6393) /var/lib/puppet/state permission check within RPM
Title: Message Title Mihai-George Cornateanu updated an issue Puppet / PUP-6393 /var/lib/puppet/state permission check within RPM Change By: Mihai-George Cornateanu Component/s: Platform Component/s: Types and Providers Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6393) /var/lib/puppet/state permission check within RPM
Title: Message Title Mihai-George Cornateanu updated an issue Puppet / PUP-6393 /var/lib/puppet/state permission check within RPM Change By: Mihai-George Cornateanu Fix Version/s: PUP 3.8.8 Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3989) output of puppet module generate does not include a .fixtures.yml file causing tests to fail
Title: Message Title Andrew Meyer commented on PUP-3989 Re: output of puppet module generate does not include a .fixtures.yml file causing tests to fail I just noticed this same problem with puppet 4.5.1. The workaround did work, but only when running the tests as an administrator: regular Windows users can't create symlinks. Is there an alternative solution that doesn't require me to do all my development as an admin? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Kenn Hussey commented on PUP-6385 Re: No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Rob Braden did this not get through CI yet? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6393) /var/lib/puppet/state permission check within RPM
Title: Message Title Mihai-George Cornateanu updated an issue Puppet / PUP-6393 /var/lib/puppet/state permission check within RPM Change By: Mihai-George Cornateanu Affects Version/s: PUP 3.8.7 Scrum Team: Client Platform Component/s: Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6393) /var/lib/puppet/state permission check within RPM
Title: Message Title Mihai-George Cornateanu created an issue Puppet / PUP-6393 /var/lib/puppet/state permission check within RPM Issue Type: Improvement Assignee: Unassigned Created: 2016/06/08 8:33 AM Priority: Normal Reporter: Mihai-George Cornateanu Found the following issue when I tried to make the system PCI-DSS v3 compliant: [root@puppet-agent ~]# rpm -Va --nofiledigest | grep '^.M' .M.../var/lib/puppet/state [root@puppet-agent ~]# This is happening because of the permissions on /var/lib/puppet/state changes with each puppet run. RPM states that it should not have the sticky bit enabled or permissions of "others", but puppet is setting them after
Jira (PUP-6392) puppet fileserver does not honor source permissions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6392 puppet fileserver does not honor source permissions Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6387) Puppet agent hung waiting on read from puppetmaster
Title: Message Title Chris Price updated an issue Puppet / PUP-6387 Puppet agent hung waiting on read from puppetmaster Change By: Chris Price Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6387) Puppet agent hung waiting on read from puppetmaster
Title: Message Title Chris Price commented on PUP-6387 Re: Puppet agent hung waiting on read from puppetmaster The agent does have, effectively, an infinite timeout where it will wait for a response from the server, but this should only come into play if it has made a successful connection and then is awaiting a response without having detected the connection being closed. Off of the top of my head it seems like that'd be a pretty difficult situation to get into w/o something weird happening on the network. Definitely let us know if you discover any more details that would allow us to try to reproduce! Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6362) Warning should be easily visible when Plugin Sync overwrites files from another Module
Title: Message Title Josh Cooper commented on PUP-6362 Re: Warning should be easily visible when Plugin Sync overwrites files from another Module We can't issue a warning on the agent side during pluginsync, because it makes a recursive file_metadatas request, and the server returns the flattened set of file metadata. See https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/mount/plugins.rb#L3-L5. So the agent never knows there was a collision. We possibly could issue a warning on the master side, but we would have to keep track of which files we've already returned metadata for (for a given request). That might be possible though it may not be good to keep a bunch of paths in memory during the lifetime of the request... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6361 Validate and error if a class or define is given a name starting with :: Change By: Henrik Lindberg Fix Version/s: PUP 4.5.3 Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (HI-416) User defined node scope variable not available in hierarchies
Title: Message Title Henrik Lindberg assigned an issue to homer Hiera / HI-416 User defined node scope variable not available in hierarchies Change By: Henrik Lindberg Assignee: homer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (HI-416) User defined node scope variable not available in hierarchies
Title: Message Title Henrik Lindberg commented on HI-416 Re: User defined node scope variable not available in hierarchies Have you tried using ::nodetype instead of nodetype in your hiera.yaml ? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6387) Puppet agent hung waiting on read from puppetmaster
Title: Message Title Christopher Tapp commented on PUP-6387 Re: Puppet agent hung waiting on read from puppetmaster Sorry yes it can apparently happen to any node at any time. We only run Ubuntu 14.04 nodes at the moment. I don't think running puppet -t in a loop is very workable as I would expect it to be a couple of months before it failed, roughly. I've increased log retention on the puppetmaster so will hopefully get something next time it happens. Typically it hasn't since I opened this ticket! I'm increasingly thinking we have a network latency issue somewhere and I'm trying to get something set up to keep an eye on it to see if there's any correlation. Although I would have hoped that the puppet agent could handle losing contact with the puppetmaster without hanging, if this is the cause. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6385) No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs
Title: Message Title Henrik Lindberg commented on PUP-6385 Re: No title provided and "" is not a valid resource reference - caused by create_resources() not filtering out undefs Alexander Johnson - there will be a quick turn around on puppet 4.5.2 where this fix will be included. Meanwhile, and if there is desire to support 4.5.0 and 4.5.1 and there are modules that are affected by this problem; as suggested the use of require => undef can be replaced with require => []. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3116) The read_mounts function reads /proc/mounts for every file call and should instead cache.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3116 The read_mounts function reads /proc/mounts for every file call and should instead cache. Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6387) Puppet agent hung waiting on read from puppetmaster
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6387 Puppet agent hung waiting on read from puppetmaster Change By: Henrik Lindberg Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6294) Add a proper 'noop' status to the report output
Title: Message Title Steve Quin commented on PUP-6294 Re: Add a proper 'noop' status to the report output Hey Steve Filip is going to sync with you on this feature. He is looking at what needs to be done and he will grab you Steve On Wed, Jun 8, 2016 at 1:05 AM Steve Axthelm (JIRA) < – Regards Steve Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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.
