Jira (PUP-2410) Create method to switch skeletons when creating new modules
Title: Message Title Corey Osman created an issue Puppet / PUP-2410 Create method to switch skeletons when creating new modules Issue Type: New Feature Assignee: Unassigned Created: 30/Apr/14 11:11 PM Labels: module generate skeleton Priority: Normal Reporter: Corey Osman Having generalized some puppet code down to a generic level where providing data is the only requirement to making puppet code. And very similar to std mod https://github.com/stdmod/puppet-skeletons. I want a way how to tell puppet generate to use a different skeleton without swapping skeleton code out. We need a way to specify types of skeletons. Example: ```bash puppet module generate --type standard lmc-mynewmod puppet module generate --type simple lmc-myothernewmod ``` With this functionality I can produce skeleton code to easily create modules that I have generalized and I can just use puppet generate --type javaapp to create a more specific module based on the skeleton. Add Comment
Jira (PUP-2390) puppet doesn't generate report when files have special characters
Title: Message Title
Luke McClelland updated an issue
Puppet / PUP-2390
puppet doesn't generate report when files have special characters
Change By:
Luke McClelland
Summary:
puppet failsto doesn't generate a report whenfileshavespecialcharacters
Agentruncompletes,butthereportcannotbesent:code:{code}file{'/path/to/directory/a':ensure=directory,source='file:///path/to/directory/b',noop=true,recurse=true,purge=true,}{code} Each In directory containsabout5k-15kfileseach. 'a': {code} #touch^? { code}{ quote}notice:Finishedcatalogrunin 159 1 . 48 41 seconds/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/indirector/rest.rb:168:in`is_http_200?'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/indirector/rest.rb:146:in`save'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/indirector/indirection.rb:271:in`save'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/configurer.rb:175:in`send_report'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/configurer.rb:169:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/agent.rb:43:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/agent/locker.rb:23:in`lock'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/agent.rb:43:in`run'/opt/puppet/pup-puppet/lib/ruby/1.8/sync.rb:230:in`synchronize'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/agent.rb:43:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/agent.rb:95:in`with_client'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/agent.rb:41:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application.rb:172:in`call'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application.rb:172:in`controlled_run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/agent.rb:39:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application/agent.rb:339:in`onetime'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application/agent.rb:313:in`run_command'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application.rb:309:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application.rb:416:in`hook'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application.rb:309:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application.rb:407:in`exit_on_fail'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/application.rb:309:in`run'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/lib/puppet/util/command_line.rb:69:in`execute'/opt/puppet/pup-puppet/lib/ruby/gems/1.8/gems/puppet-2.7.25/bin/puppet:4/usr/bin/puppet:23:in`load'/usr/bin/puppet:23err:Couldnotsendreport:Error400onSERVER:Couldnotinternfromyaml:syntaxerroronline 38198 1738 ,col14:`!binary?
Jira (PUP-2390) puppet doesn't generate report when files have special characters
Title: Message Title
Luke McClelland updated an issue
Puppet / PUP-2390
puppet doesn't generate report when files have special characters
Change By:
Luke McClelland
Agentruncompletes,butthereportcannotbesent:code:{code}file{'/ path/to/directory/a mnt ':ensure=directory,source='file:/// path/to/directory/b mnt2 ',noop=true,recurse=true,purge=true,}{code}Indirectory' a /mnt2 ':{code}#touch^?{code}{quote}notice: /Stage[main]/Compare/File[/mnt]/owner:current_valuebin,shouldberoot(noop)notice:/Stage[main]/Compare/File[/mnt]/group:current_valuebin,shouldbesystem(noop)notice:/File[/mnt/]/ensure:current_valueabsent,shouldbefile(noop)notice:/mnt:Wouldhavetriggered'refresh'from3eventsnotice:Class[Compare]:Wouldhavetriggered'refresh'from1eventsnotice:Stage[main]:Wouldhavetriggered'refresh'from1eventsinfo:Creatingstatefile/var/lib/puppet/state/state.yamlnotice:
Jira (PDB-309) Update Schema config conversion logic for 2.0
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-309 Update Schema config conversion logic for 2.0 Change By: Ryan Senior Assignee: RyanSenior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 01/May/14 5:20 AM Fix Versions: 4.0.0 Priority: Normal Reporter: Henrik Lindberg There is support for Ruby 1.8.7 multibyte strings in the Lexer. Since Suport for Ruby 1.8.7 is being dropped for 4.0 (PUP-1805). This logic can be removed. Add Comment
Jira (PUP-2412) Remove 1.8.7 function API support
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2412 Remove 1.8.7 function API support Issue Type: Improvement Assignee: Andy Parker Components: DSL Created: 01/May/14 5:23 AM Fix Versions: 4.0.0 Priority: Normal Reporter: Henrik Lindberg Since support for Ruby 1.8.7 is being dropped (PUP-1805), the alternative path taken in the function API for getting information about arity and optional arguments for Ruby 1.8.7 can be removed. Add Comment
Jira (PDB-626) PR (956): Updated the release notes for the 2.0.0 release - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-626 PR (956): Updated the release notes for the 2.0.0 release - senior Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-627) PR (958): DOCS: We now need Puppet 3.5.1, not 3.4.2 - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-627 PR (958): DOCS: We now need Puppet 3.5.1, not 3.4.2 - kbarber Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-627) PR (958): DOCS: We now need Puppet 3.5.1, not 3.4.2 - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-627 PR (958): DOCS: We now need Puppet 3.5.1, not 3.4.2 - kbarber Change By: Kenneth Barber Sprint: 20140423to20140507 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-626) PR (956): Updated the release notes for the 2.0.0 release - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-626 PR (956): Updated the release notes for the 2.0.0 release - senior Change By: Kenneth Barber Fix Version/s: 2.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-625) PR (955): Fix environment end-point links to be compatible with our docs site - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-625 PR (955): Fix environment end-point links to be compatible with our docs site - kbarber Change By: Kenneth Barber Story Points: 0 Fix Version/s: 2.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-627) PR (958): DOCS: We now need Puppet 3.5.1, not 3.4.2 - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-627 PR (958): DOCS: We now need Puppet 3.5.1, not 3.4.2 - kbarber Change By: Kenneth Barber Fix Version/s: 2.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2413) Attempting to log the output of service initialization on CentOS 6.5 causes SELinux violations
Title: Message Title
Logan Attwood created an issue
Puppet / PUP-2413
Attempting to log the output of service initialization on CentOS 6.5 causes SELinux violations
Issue Type:
Bug
Assignee:
Unassigned
Created:
01/May/14 8:12 AM
Environment:
CentOS 6.5 Puppet 3.5.0
Priority:
Normal
Reporter:
Logan Attwood
It looks like puppet is creating a file in /tmp to connect to the stdout of service httpd start to. Out of the box CentOS 6 (and I can only assume RHEL 6) does not permit Apache to write to /tmp, causing an SELinux violation similar to the following:
kernel: type=1400 audit(1398909812.247:10): avc: denied { read write }
for pid=20375 comm=httpd path=/tmp/puppet20140501-19869-xtobvy-0 dev=xvde ino=18584 scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=file
I suspect this had to do with bringing the service resource providers up to feature parity with the exec resource providers.
The workaround would be to accept not getting Apache's startup output when using Puppet, or create an selinux module to permit apache writing to /tmp.
Jira (PUP-1973) future parser doesn't bind variables from inherited scope
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1973 future parser doesn't bind variables from inherited scope Change By: Rob Reynolds Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1979) future parser Class reference with leading :: doesn't work
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1979 future parser Class reference with leading :: doesn't work Change By: Rob Reynolds Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1978) future parser doesn't accept empty array as title
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1978 future parser doesn't accept empty array as title Change By: Rob Reynolds Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1937) Acceptance tests assume ruby is in path on windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1937 Acceptance tests assume ruby is in path on windows Change By: Rob Reynolds Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1937) Acceptance tests assume ruby is in path on windows
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1937 Acceptance tests assume ruby is in path on windows Change By: Rob Reynolds Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2325) Update version number
Title: Message Title Rob Reynolds commented on an issue Re: Update version number Version updated at https://github.com/puppetlabs/puppet/commit/67241097aa839b1a4cc06f61f69e9c260287ebcd Add Comment Puppet / PUP-2325 Update version number Update version number This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2326) Tag the release and create packages
Title: Message Title Rob Reynolds commented on an issue Re: Tag the release and create packages Here is the commit sha - https://github.com/puppetlabs/puppet/commit/67241097aa839b1a4cc06f61f69e9c260287ebcd Add Comment Puppet / PUP-2326 Tag the release and create packages Tag the release and create packages This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2010) have test repos pushed to hosts during acceptance testing
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2010 have test repos pushed to hosts during acceptance testing Change By: Adrien Thebo Assignee: AliceNodelman AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-474) ipaddress fact should use the interface with the default route.
Title: Message Title Martin Hovmller created an issue Facter / FACT-474 ipaddress fact should use the interface with the default route. Issue Type: Improvement Affects Versions: 1.7.6, 1.7.5, 2.0.1, 1.7.4 Assignee: Unassigned Created: 01/May/14 9:04 AM Environment: Linux Labels: facter Priority: Normal Reporter: Martin Hovmller The ipaddress fact in linux chooses the first non 127.0.0.0/8 IP address found when running ifconfig. This is not very intelligent. A better way is to look at the routing table and take the IP of the interface with the default route.
Jira (PUP-2292) Insufficient tests on yumrepo's = absent
Title: Message Title Joshua Partlow assigned an issue to Kurt Wall Puppet / PUP-2292 Insufficient tests on yumrepo's = absent Change By: Joshua Partlow Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2291) yumrepo priority can not be sent to absent
Title: Message Title Joshua Partlow assigned an issue to Kurt Wall Puppet / PUP-2291 yumrepo priority can not be sent to absent Change By: Joshua Partlow Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2073) PR (2477) Multiple values for diff_args causes diff execution failure
Title: Message Title Joshua Partlow assigned an issue to Kurt Wall Puppet / PUP-2073 PR (2477) Multiple values for diff_args causes diff execution failure Change By: Joshua Partlow Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Title: Message Title Joshua Cooper assigned an issue to Joshua Cooper Puppet / PUP-1840 Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts Change By: Joshua Cooper Assignee: JoshuaCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Title: Message Title Jared Jennings commented on an issue Re: Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts About the digest parser function, I've replaced gh-2453 with gh-2603 https://github.com/puppetlabs/puppet/pull/2603. Add Comment Puppet / PUP-1840 Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts I'm using Puppet in part to ensure [Federal Information Processing Standard 140-2](http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf) (FIPS 140-2) compliance on my network. Part of this compliance for the system underlying Puppet is to make sure that only [FIPS Approved](http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexa.pdf) algo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2409) Find out how to configure hashing algorithm for FIPS
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2409 Find out how to configure hashing algorithm for FIPS Change By: Nicholas Fagerlund PUP- 1940 1840 allowsyoutochangethehashingalgorithm.ButIdon'tknowhowtodothat;can'tseeasettingoranything.I'mnotsurewherethisshouldbedocumented;we'llhavetofigurethatoutonceweknowhowitworks. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1699) Cache environments
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1699 Cache environments Need pre-docs for this regarding the new environment_timeout setting and environment caching behavior. Change By: Joshua Partlow Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2401) Add acceptance tests for ssh_authorized_key type
Title: Message Title John Duarte commented on an issue Re: Add acceptance tests for ssh_authorized_key type See PR 2604. Add Comment Puppet / PUP-2401 Add acceptance tests for ssh_authorized_key type Add basic acceptance tests for ssh_authorized_key type This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2344) Functions unable to call functions in different modules
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2344 Functions unable to call functions in different modules Change By: Joshua Partlow Assignee: JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2395) Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10
Title: Message Title Matthaus Owens commented on an issue Re: Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10 I have thoughts! Saucy is the first ubuntu/debian to move to apache 2.4, and it almost certainly causes this break. Debian 7 (wheezy) still ships apache 2.2. I seem to recall a similar bug hitting launchpad, I'll see if I can dig up what their fix was. Add Comment Puppet / PUP-2395 Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10 While doing smoke testing for Puppet, I found this weird issue: https://gist.github.com/kbarber/1661a6ff53cc7639bf6a It seems there is something up with the puppetmaster-passenger installation, its returning an about the site missing. Not sure what is going on here, the package works fine on Debian 7.0. I had to install apache2 up front, before it w... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2395) Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10
Title: Message Title Kenneth Barber updated an issue Puppet / PUP-2395 Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10 Change By: Kenneth Barber Whiledoingsmoketestingfor PuppetDB(whichrequirestheinstallationof Puppet ) ,Ifoundthisweirdissue:https://gist.github.com/kbarber/1661a6ff53cc7639bf6aItseemsthereissomethingupwiththepuppetmaster-passengerinstallation,itsreturninganaboutthesitemissing.Notsurewhatisgoingonhere,thepackageworksfineonDebian7.0.Ihadtoinstallapache2upfront,beforeitwasonlyinstallingapache2-binforwhateverreason,anditcouldn'tevencreatethesites-enabledlink.Icouldbecompletelywronghere,wouldn'tmindasecondsiteofeyesonthis. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2395) Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10
Title: Message Title Kenneth Barber updated an issue Puppet / PUP-2395 Installation problem for puppetmaster-puppet 3.5.1 on Ubuntu 13.10 Change By: Kenneth Barber WhiledoingsmoketestingforPuppetDB(whichrequirestheinstallationofPuppet),Ifoundthisweirdissue:https://gist.github.com/kbarber/1661a6ff53cc7639bf6aItseemsthereissomethingupwiththepuppetmaster-passengerinstallation,itsreturningan error aboutthesitemissing.Notsurewhatisgoingonhere,thepackageworksfineonDebian7.0.Ihadtoinstallapache2upfront,beforeitwasonlyinstallingapache2-binforwhateverreason,anditcouldn'tevencreatethesites-enabledlink.Icouldbecompletelywronghere,wouldn'tmindasecondsiteofeyesonthis. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2283) Release Azure agent for 3.2.2
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2283 Release Azure agent for 3.2.2 Change By: Ethan Brown Assignee: EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2344) Functions unable to call functions in different modules
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2344 Functions unable to call functions in different modules Change By: Andy Parker Assignee: JoshuaPartlow AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1699) Cache environments
Title: Message Title Andy Parker assigned an issue to Joshua Partlow Puppet / PUP-1699 Cache environments Change By: Andy Parker Assignee: JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2409) Find out how to configure hashing algorithm for FIPS
Title: Message Title Nicholas Fagerlund commented on an issue Re: Find out how to configure hashing algorithm for FIPS OH ALSO, that setting has to be set globally-and-i-do-mean-globally. If there's a mismatch between agent and master, the agents can't filebucket and will abort. Add Comment Puppet / PUP-2409 Find out how to configure hashing algorithm for FIPS PUP-1840 allows you to change the hashing algorithm. But I don't know how to do that; can't see a setting or anything. I'm not sure where this should be documented; we'll have to figure that out once we know how it works. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2406) Run all acceptance jobs in parallel
Title: Message Title Andy Parker assigned an issue to Roger Ignazio Puppet / PUP-2406 Run all acceptance jobs in parallel Change By: Andy Parker Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-233) Fact to add DHCP Server Details
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-233 Fact to add DHCP Server Details Change By: Adrien Thebo Assignee: KyloGinsberg AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2414) Get Puppet acceptance to use the new internal forge being set up by the module team.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-2414 Get Puppet acceptance to use the new internal forge being set up by the module team. Issue Type: Task Assignee: Eric Sorenson Components: QA Created: 01/May/14 10:32 AM Priority: Normal Reporter: Joshua Partlow Currently Puppet Acceptance relies on being able to reach a testing forge instance forge-aio01-petest.puppetlabs.com. This is an external node hosted on linode, and susceptible to all the same connectivity issues which have caused us to create local rubygem, github and packaging mirrors. So a request was put in for an internal forge instance for testing PF-558. This is currently being worked on and should be done soon. But we need to update Puppet's acceptance configuration to use it. Currently acceptance/bin/ci-bootstrap-from-artifacts.sh has a :forge_host setting in the local_options.rb created for Beaker. This ensures acceptance tests in our current Jenkin's jobs will get the external forge host. There is a small issue with this in that manually running acceptance requires remembering to set the forge_host locally (as opposed to if it was a setting handled by the acceptance/Rakefile default options directly). There is also an issue to just changing to the new internal host address, as a hard setting, as that would prevent an external user from running the tests unless they override the option themselves. Which actually is not a big deal, it just needs to be documented. Not sure what the best solution is.
Jira (PUP-2415) Read Old sysconfig file (puppetagent) for compatibility
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2415 Read Old sysconfig file (puppetagent) for compatibility Issue Type: Task Assignee: Unassigned Created: 01/May/14 10:32 AM Fix Versions: 3.6.0 Priority: Minor Reporter: Rob Reynolds For compatibility reasons read the old sysconfig file although new one overrides it. But people who have some interesting settings in the old sysconfig file can still use them unless the are set to something else in the new one. Add Comment This message was sent by
Jira (PUP-2415) Read old sysconfig file (puppetagent) for compatibility
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2415 Read old sysconfig file (puppetagent) for compatibility Change By: Rob Reynolds Summary: Read Old old sysconfigfile(puppetagent)forcompatibility Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2414) Get Puppet acceptance to use the new internal forge being set up by the module team.
Title: Message Title Joshua Partlow assigned an issue to Roger Ignazio Puppet / PUP-2414 Get Puppet acceptance to use the new internal forge being set up by the module team. Change By: Joshua Partlow Assignee: EricSorenson RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2414) Get Puppet acceptance to use the new internal forge being set up by the module team.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2414 Get Puppet acceptance to use the new internal forge being set up by the module team. Change By: Joshua Partlow Sprint: Week2014-5-7to2014-5-14 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2415) Read old sysconfig file (puppetagent) for compatibility
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2415 Read old sysconfig file (puppetagent) for compatibility Change By: Rob Reynolds *Makerelationbetweenserviceandsysconfigfileobvious-Thereispuppetservicebutit'senvironmentfileiscalledpuppetagent(probablyduetohistoricalreasons).Makingthenamingmoreconsistentandobvious.* Forcompatibilityreasonsreadtheoldsysconfigfilealthoughnewoneoverridesit.Butpeoplewhohavesomeinterestingsettingsintheoldsysconfigfilecanstillusethemunlessthearesettosomethingelseinthenewone. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2415) Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2415 Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet Change By: Rob Reynolds Summary: Readold Rename/etc/ sysconfig file( / puppetagent )forcompatibility to/etc/sysconfig/puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2415) Puppet Service - Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2415 Puppet Service - Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet Change By: Rob Reynolds Summary: PuppetService- Rename/etc/sysconfig/puppetagentto/etc/sysconfig/puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2416) Puppet Service - Use no-daemonize and no forking (Master and Agent)
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2416 Puppet Service - Use no-daemonize and no forking (Master and Agent) Issue Type: Task Assignee: Unassigned Created: 01/May/14 10:48 AM Fix Versions: 3.6.0 Priority: Normal Reporter: Rob Reynolds From b9035cf: Use no-daemonize and not forking service Making puppet fork and systemd to read PID file seems unnecessary complicated. Add Comment This message was sent
Jira (PUP-2415) Puppet Agent Service - Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2415 Puppet Agent Service - Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet Change By: Rob Reynolds Summary: Puppet Agent Service-Rename/etc/sysconfig/puppetagentto/etc/sysconfig/puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2399) Add acceptance tests for mailalias type
Title: Message Title John Duarte commented on an issue Re: Add acceptance tests for mailalias type Any testing of the aliases.db has been removed from the tests in PR-2599 as per the decision in PUP-1143 . Add Comment Puppet / PUP-2399 Add acceptance tests for mailalias type Add basic acceptance tests for the mailalias type This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2417) Puppet Agent Should wait for Puppet Master to finish starting, if puppet master is installed
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2417 Puppet Agent Should wait for Puppet Master to finish starting, if puppet master is installed Issue Type: Task Assignee: Unassigned Created: 01/May/14 10:54 AM Fix Versions: 3.6.0 Priority: Normal Reporter: Rob Reynolds From 4ebcfda Adding dependency on puppetmaster to puppet Sounds like a good idea to wait with start of puppet agent to finish starting of puppet mater first. Add Comment This message was
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2415) Puppet Agent Service - Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2415 Puppet Agent Service - Rename /etc/sysconfig/puppetagent to /etc/sysconfig/puppet Change By: Rob Reynolds Sprint: Week2014-4-30to2014-5-7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2014) Make gem provider match on a single gem name
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2014 Make gem provider match on a single gem name Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2417) Puppet Agent Should wait for Puppet Master to finish starting, if puppet master is installed
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2417 Puppet Agent Should wait for Puppet Master to finish starting, if puppet master is installed Change By: Rob Reynolds Sprint: Week2014-4-30to2014-5-7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2416) Puppet Service - Use no-daemonize and no forking (Master and Agent)
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2416 Puppet Service - Use no-daemonize and no forking (Master and Agent) Change By: Rob Reynolds Sprint: Week2014-4-30to2014-5-7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2418) Remove Tar::Solaris from module_tool
Title: Message Title Rob Reynolds created an issue Puppet / PUP-2418 Remove Tar::Solaris from module_tool Issue Type: Task Assignee: Unassigned Created: 01/May/14 11:02 AM Fix Versions: 3.6.0 Priority: Normal Reporter: Rob Reynolds Commit 4500f9fafeca5221a0d627e4547b45dc9a6920f9 Author: Reid Vandewiele reid at puppetlabs.com Date: Fri Mar 7 12:47:40 2014 -0800 Remove now-redundant Tar::Solaris from module_tool Changes to the way Puppet::ModuleTool::Tar::Gnu works means that the *::Tar::Solaris variant should now be redundant. It existed to require gtar when the underlying platform did not support GNU-tar options, but the changes to the core Tar::Gnu class mean that we no longer use any flags or options that don't work just fine with oldschool unix tar executables. Remove Puppet::ModuleTool::Tar::Solaris. On a side note, Tar::Gnu should probably be renamed to something more generic. Add Comment
Jira (PUP-2418) Remove Tar::Solaris from module_tool
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2418 Remove Tar::Solaris from module_tool Change By: Rob Reynolds Sprint: Week2014-4-30to2014-5-7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2321) Is there a bug targeted at the release for every commit?
Title: Message Title Rob Reynolds commented on an issue Re: Is there a bug targeted at the release for every commit? This is good to go now https://gist.github.com/ferventcoder/7c259f0a615b17399da7#file-v3-6-0-cleaned Add Comment Puppet / PUP-2321 Is there a bug targeted at the release for every commit? Is there a bug targeted at the release for every commit? This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2419) Deprecate req_bits setting
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2419 Deprecate req_bits setting Issue Type: Task Assignee: Unassigned Created: 01/May/14 11:25 AM Priority: Normal Reporter: Joshua Cooper The `req_bits` setting is not used (except for the test_helper.rb), and duplicates `keylength`, which determines the length of RSA keys to generate (in bits). Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2419) Deprecate req_bits Setting
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2419 Deprecate req_bits Setting Change By: Joshua Cooper Summary: Deprecate req_bitsSetting Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2419)
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2419 Change By: Joshua Cooper Summary: Deprecatereq_bitssetting Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1893) ACL module permissions are not formatted correctly
Title: Message Title
Rob Reynolds commented on an issue
Re: ACL module permissions are not formatted correctly
Still goes back to my comments on how puppet produces booleans when using self.format_value_for_display(value) - specifically https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parameter.rb#L570
Add Comment
Puppet / PUP-1893
ACL module permissions are not formatted correctly
The ACL module uses {code} C:\work\puppet [master +8 ~0 -0 !] bundle exec puppet resource acl c:\ acl { 'c:\': ensure = 'present', group = 'S-1-5-80-...', inherit_parent_permissions = 'false', owner = 'S-1-5-80-...', permissions = [ '{identity = '...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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-2420) CRLs should be signed with SHA256 when available
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2420 CRLs should be signed with SHA256 when available Issue Type: Bug Assignee: Unassigned Created: 01/May/14 11:49 AM Priority: Normal Reporter: Joshua Cooper Certificate revocation lists are always signed with SHA1WithRSAEncryption, but when signing certificate signing requests and certificates, we default to SHA256WithRSAEncryption. If SHA256 is not available, we fall back to SHA1WithRSAEncryption. We should refactor the CRL code to use the CertificateSigner code so that we use more secure defaults. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2420) CRLs should be signed with SHA256 when available
Title: Message Title Joshua Cooper commented on an issue Re: CRLs should be signed with SHA256 when available There is also some duplicated logic in `Puppet::SSL::Host#suitable_digest_algorithms` Add Comment Puppet / PUP-2420 CRLs should be signed with SHA256 when available Certificate revocation lists are always signed with SHA1WithRSAEncryption, but when signing certificate signing requests and certificates, we default to SHA256WithRSAEncryption. If SHA256 is not available, we fall back to SHA1WithRSAEncryption. We should refactor the CRL code to use the CertificateSigner code so that we use more secure defaults. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-233) Fact to add DHCP Server Details
Title: Message Title Adrien Thebo commented on an issue Re: Fact to add DHCP Server Details Spec failures on Solaris where nmcli doesn't exist (https://jenkins.puppetlabs.com/job/Facter-Specs-Solaris-2.0/224/) indicates incomplete stubbing, fixed that up and pushed. Add Comment Facter / FACT-233 Fact to add DHCP Server Details Add per interface fact that shows the DHCP server IP for that interface if the interface IP is DHCP assigned. e.g. 'dhcp_server_eth0' Also add a 'dhcp_server' fact if the interface the machine uses to reach the default gateway is dhcp enabled. PR created: https://github.com/puppetlabs/facter/pull/559 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2421) stringify_facts needs to be in agent, not master conf file
Title: Message Title Jascha Lee created an issue Puppet / PUP-2421 stringify_facts needs to be in agent, not master conf file Issue Type: Bug Affects Versions: 3.5.0 Assignee: Eric Sorenson Components: DOCS Created: 01/May/14 12:09 PM Priority: Minor Reporter: Jascha Lee http://docs.puppetlabs.com/puppet/3.5/reference/release_notes.html state: You have to manually enable this by setting stringify_facts = false in puppet.conf on your puppet master(s) I believe this is incorrect. This should be set in the [main] section on each agent. I think this is also true for the global facts hash Add Comment
Jira (PUP-2402) Add acceptance tests for sshkey type
Title: Message Title John Duarte commented on an issue Re: Add acceptance tests for sshkey type See PR 2607. Add Comment Puppet / PUP-2402 Add acceptance tests for sshkey type Add basic acceptance tests for sshkey type This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2422) versioncmp does not check version length before comparing values
Title: Message Title chris pisano created an issue Puppet / PUP-2422 versioncmp does not check version length before comparing values Issue Type: Improvement Affects Versions: 3.5.1 Assignee: Unassigned Created: 01/May/14 1:21 PM Environment: Puppet 3.x on CentOS 6.x Priority: Normal Reporter: chris pisano When running versioncmp it fails to properly compare version numbers that are of unequal length. For example 6.0 and 6.0.3 are not compared correctly. Add Comment
Jira (PUP-2327) Smoke test packages
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2327 Smoke test packages Change By: Rob Reynolds Smoketest packages platforms:*rhel7*centos5*Windows2003/2012*ubuntu--14--12.04*debian7Otherplatformsasyouseefit.Smoketestprocedure:*Start/stop/restartamasterwiththeinitscripts(ondebiantrythepassengermaster)*Start/stop/restartanagent*Help/man*Writeandrunsomemanifests Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2327 Smoke test packages Change By: Rob Reynolds Smoketestplatforms:*rhel7*centos 5 6 *Windows2003/2012*ubuntu--14--12.04*debian7Otherplatformsasyouseefit.Smoketestprocedure:*Start/stop/restartamasterwiththeinitscripts(ondebiantrythepassengermaster)*Start/stop/restartanagent*Help/man*Writeandrunsomemanifests Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2327 Smoke test packages Change By: Rob Reynolds Smoketestplatforms:*rhel7*centos6*Windows2003/2012*ubuntu --14-- 12.04*debian7Otherplatformsasyouseefit.Smoketestprocedure:*Start/stop/restartamasterwiththeinitscripts(ondebiantrythepassengermaster)*Start/stop/restartanagent*Help/man*Writeandrunsomemanifests Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages I can grab centos 6 Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2423) Filebucket server should warn, not fail, if checksum type is not supported
Title: Message Title
Joshua Cooper created an issue
Puppet / PUP-2423
Filebucket server should warn, not fail, if checksum type is not supported
Issue Type:
Bug
Affects Versions:
3.6.0
Assignee:
Unassigned
Created:
01/May/14 2:21 PM
Priority:
Normal
Reporter:
Joshua Cooper
PUP-1840 allows users to specify the digest algorithm to use for file bucketing and the file checksum parameter. However, if you reconfigure the master to use SHA256:
[main]
digest_algorithm=sha256
Then it will reject file bucket requests from agents that haven't switched over:
# puppet agent -td
...
Error: /Stage[main]/Main/File[/tmp/foo]/content: change from {md5}ad8d557625a565312d6998496a357b7b to {md5}5d41402abc4b2a76b9719d911017c592 failed: Could not back up /tmp/foo: Error 400 on SERVER: Bad Request
Specifically, if you are using puppet to manage its own puppet.conf, then the agent will try to file bucket the old puppet.conf before overwriting it. Since it's using the old digest algorithm, it will fail the catalog run, without making the change.
The workaround is to disable filebuckets globally, then apply the digest_algorithm change.
Jira (PUP-2423) Filebucket server should warn, not fail, if checksum type is not supported
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2423 Filebucket server should warn, not fail, if checksum type is not supported Change By: Joshua Cooper Fix Version/s: 3.6.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages I'm taking rhel7 Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages I'll check debian 7 Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-869) Deprecate file Face
Title: Message Title
Joshua Cooper commented on an issue
Re: Deprecate file Face
And the actions are not consistent:
puppet file find md5/checksum
puppet file download {md5}checksum
Add Comment
Puppet / PUP-869
Deprecate file Face
The file face is described as {{Retrieve and store files in a filebucket}}. The filebucket command is described as {{Store and retrieve files in a filebucket}}. In puppet help output these are shown right after one another. It isn't clear which one a user should use. In reality they will have a very difficult time getting {{file}} to behave in a reason...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-1840) Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Title: Message Title
Joshua Cooper commented on an issue
Re: Let user change hashing algorithm, to avoid crashing on FIPS-compliant hosts
Verified MD5 is not used for any certificate signing operation. CSR and certs signatures default to SHA256WithRSAEncryption, fall back to SHA1WithRSAEncryption, otherwise fail. CRLs default to SHA1, see PUP-2420.
This change requires that the digest_algorithm=sha256 setting be applied globally. Filed PUP-2423. Once agent and master settings are modified, the agent can successfully backup files:
In site.pp, create a filebucket resource, the path = false part is important:
filebucket { 'main':
path = false,
}
File { backup = 'main' }
Notice: /Stage[main]/Main/File[/Users/josh/.puppet/puppet.conf]/content: content changed
'{sha256}415e8d4611cefaffa4392d3cd282451b076c650fe7f56bb836d26b801b471be2' to
'{sha256}84c3582c512959fc92ad3bde581f8ec58c34ebfc6f89fca4459cb670e90e2d9f'
Verified that the puppet file application works:
$ bundle exec puppet file download {sha256}415e8d4611cefaffa4392d3cd282451b076c650fe7f56bb836d26b801b471be2 --digest_algorithm sha256
[main]
server = puppetmaster.solar.lan
And the puppet filebucket application works also:
$ bundle exec puppet filebucket get 415e8d4611cefaffa4392d3cd282451b076c650fe7f56bb836d26b801b471be2 --digest_algorithm=sha256
[main]
server = puppetmaster.solar.lan
Add Comment
Puppet / PUP-1840
Jira (PUP-2424) Deprecate Puppet::Plugins
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-2424 Deprecate Puppet::Plugins Issue Type: Task Assignee: Andy Parker Components: Modules Created: 01/May/14 2:58 PM Priority: Normal Reporter: Charlie Sharpsteen The Puppet::Plugins system operates by loading any file named plugin_init.rb found in $LOAD_PATH. These plugin files can define hook functions that are called via Puppet::Plugins through a method_missing overload. The whole thing is very magical. As far as I can tell, the Puppet::Plugins system was added nearly 3 years ago as a workaround for hacks shipped in PE 1.0 that implemented license checks. PE ended up shipping a different workaround and Puppet::Plugins was never actually used. If nothing is actually using this system, we should deprecate it and consider a replacement with a well-defined architecture. Add Comment
Jira (PUP-2212) rrdgraph report processor should be deprecated
Title: Message Title Andy Parker commented on an issue Re: rrdgraph report processor should be deprecated In addition to the rrdgraph processor, also deprecate any settings related to rrd. Add Comment Puppet / PUP-2212 rrdgraph report processor should be deprecated This report processor is unreasonable hard to configure properly and it's surprisingly easy to break PE installations accidentally. I've done it more than once demoing it for training classes. The Console already provides this functionality and better reporting tools, such as Graphite, can be configured quite easily as well. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1515) Invalid parameter provider for custom types/providers
Title: Message Title Andreas Ntaflos commented on an issue Re: Invalid parameter provider for custom types/providers Me, too. Our Puppet master currently runs in the 'production' environment while a growing number of nodes run in a different environment (called 'production_redux', as we are overhauling the Puppet infrastructure on that site). Using the puppetlabs-mysql module in the 'production_redux' environment (but not in 'production') we get the invalid parameter provider exception trying to manage MySQL users and databases. Do I understand correctly that switching the Puppet master's own environment to (in our case) 'production_redux' would work around this problem? FWIW, running puppet plugin download --environment production_redux on the Puppet master results in this: # puppet plugin download --environment production_redux Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': undefined method `intern' for nil:NilClass Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file metadata for puppet://puppet01.example.com/plugins: undefined method `intern' for nil:NilClass Wrapped exception: undefined method `intern' for nil:NilClass Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional resources using 'eval_generate': undefined method `intern' for nil:NilClass Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet://puppet01.example.com/pluginfacts: undefined method `intern' for nil:NilClass Wrapped exception: undefined method `intern' for nil:NilClass No plugins downloaded. I have no idea what to make of this. Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers
Jira (PUP-2344) Functions unable to call functions in different modules
Title: Message Title Andy Parker assigned an issue to Unassigned Puppet / PUP-2344 Functions unable to call functions in different modules Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages I'm on ubuntu 12.04 Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Andy Parker commented on an issue Re: Smoke test packages rhel7 looks good Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2425) Various places in docs assume md5 is the only checksum
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-2425
Various places in docs assume md5 is the only checksum
Change By:
Joshua Cooper
Variousplacesindocsassumethatmd5istheonlychecksumbeingused.DuetoPUP-1840,itmaynotbe.lib/puppet/application/filebucket.rb{ quote noformat }backup:Sendoneormorefilestothespecifiedfilebucket.Eachsentfileisprintedwithitsresultingmd5sum.{ quote noformat }Really,thespecifiedfileshouldbethesumthatmatchesthecurrent{{Puppet\[:digest_algorithm]}}forthefileyouwant.Alsosee[lib/puppet/face/file.rb|https://github.com/puppetlabs/puppet/blob/3.5.1-rc1/lib/puppet/face/file.rb#L27]{ quote noformat }file.argumentsmd5/md5sum{ quote noformat }And[lib/puppet/face/file/download.rb|https://github.com/puppetlabs/puppet/blob/3.5.1-rc1/lib/puppet/face/file/download.rb#L5]{ quote noformat }arguments({md5}checksum|puppet_url){ quote noformat }
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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-2425) Various places in docs assume md5 is the only checksum
Title: Message Title Joshua Cooper created an issue Puppet / PUP-2425 Various places in docs assume md5 is the only checksum Issue Type: Bug Affects Versions: 3.6.0 Assignee: Eric Sorenson Components: DOCS Created: 01/May/14 3:16 PM Priority: Normal Reporter: Joshua Cooper Various places in docs assume that md5 is the only checksum being used. Due to PUP-1840 , it may not be. lib/puppet/application/filebucket.rb backup: Send one or more files to the specified file bucket. Each sent file is printed with its resulting md5 sum. Really, the specified file should be the sum that matches the current Puppet[:digest_algorithm] for the file you want. Also see lib/puppet/face/file.rb file.arguments md5/md5sum And lib/puppet/face/file/download.rb arguments (
Jira (PUP-2327) Smoke test packages
Title: Message Title Rob Reynolds commented on an issue Re: Smoke test packages centos 6 looks good. Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2327) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages debian 7 is fine checking 12.04 now for Andy Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2326) Tag the release and create packages
Title: Message Title Rob Reynolds commented on an issue Re: Tag the release and create packages We are ready for MSI builds. Thanks! Add Comment Puppet / PUP-2326 Tag the release and create packages Tag the release and create packages This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Ethan Brown commented on an issue Re: Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed Sorry I never responded to this one back in March. We have a couple of options Remove it Switch to a C-based alternative that doesn't rely on the .NET Framework, like http://code.kliu.org/misc/elevate/ Add a configuration file that overrides the .NET runtime used to run elevate.exe I've submitted a PR for the third option. At the very least, I think this is a good idea until we decide if one of the other options is better and we can properly vet it. https://github.com/puppetlabs/puppet-win32-ruby/pull/28 If we are not wildcard including files in our Wix projects, then the relevant Wix project will likely need modification as well. Add Comment Puppet / PUP-1951 Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed With Windows 2012, installing the puppet MSI (3.5.0-rc1 in this case) and then trying to run the Run Facter or Run Puppet Agent commands from the Start Menu will result in an error that it needs the .NET Framework version 3.5 in order to run and it cannot install it. However Start Command Prompt With Puppet works without issue.
Jira (PUP-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1951 Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed Change By: Ethan Brown Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1951 Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed Change By: Ethan Brown Sprint: Week2014-5-7to2014-5-14 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1951 Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed Change By: Ethan Brown Sprint: Week2014- 5 4 - 7 30 to2014-5- 14 7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-475) Default external-dir should be exposed as a core fact
Title: Message Title R Tyler created an issue Facter / FACT-475 Default external-dir should be exposed as a core fact Issue Type: New Feature Assignee: Eric Sorenson Created: 01/May/14 3:44 PM Priority: Normal Reporter: R Tyler The Facter documentation gives a series of external fact locations on different platforms. Gee golly it would be handy to have a $external_fact_dir core fact which allowed my Puppet code to intelligently drop external facts across platforms into aforementioned directory. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2426) Puppet's v2 environment listing does not display config_version and environment_timeout as well.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-2426 Puppet's v2 environment listing does not display config_version and environment_timeout as well. Issue Type: Bug Affects Versions: 3.6.0 Assignee: Eric Sorenson Components: DOCS Created: 01/May/14 3:47 PM Fix Versions: 3.7.0 Priority: Normal Reporter: Joshua Partlow We added config_version and environment_timeout settings to directory environment environment.conf. Puppet's v2 environments listing needs to show these environment parameters as well. (lib/puppet/network/http/api/v2/environments.rb) Will also need to update the API docs for v2.0/environments
Jira (PUP-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config
Title: Message Title Aaron Zauner commented on an issue Re: PR (2494) Insecure shipped Cipher settings in Passenger example config The current passenger configuration that puppet ships and is packaged for linux distributions is far less secure: https://github.com/puppetlabs/puppet/pull/2494#issuecomment-41861469 Still working on a proper fix. It isn't as easy as it seems with a ton of OpenSSL versions and a ciphersuite this big though. I'll keep you posted. Add Comment Puppet / PUP-2177 PR (2494) Insecure shipped Cipher settings in Passenger example config https://github.com/puppetlabs/puppet/pull/2494 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1951) Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed
Title: Message Title Ethan Brown commented on an issue Re: Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed Also – I verified in Azure that 2008R2 is unaffected 2012 is affected 2012R2 is affected Basically anything without a .NET 2.0 CLR installed / enabled by default. As long as the .exe.config is dropped in, we're back in business. Add Comment Puppet / PUP-1951 Unable to Run Facter or Run Puppet Agent from Start Menu on Windows 8/2012 - Requires .NET Framework 3.5 installed With Windows 2012, installing the puppet MSI (3.5.0-rc1 in this case) and then trying to run the Run Facter or Run Puppet Agent commands from the Start Menu will result in an error that it needs the .NET Framework version 3.5 in order to run and it cannot install it. However Start Command Prompt With Puppet works without issue. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2327) Smoke test packages
Title: Message Title Joshua Partlow commented on an issue Re: Smoke test packages 12.04 is good Add Comment Puppet / PUP-2327 Smoke test packages Smoke test platforms: * rhel7 * centos 6 * Windows 2003/2012 * ubuntu 12.04 * debian 7 Other platforms as you see fit. Smoke test procedure: * Start/stop/restart a master with the init scripts (on debian try the passenger master) * Start/stop/restart an agent * Help/man * Write and run some manifests This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.
