Jira (PUP-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Eric Thompson commented on PUP-3786 Re: Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter verified on ubuntu 14.04 at SHA: 264abcc with: (see charlie's parser call script above) root@j96kz70z3wi10wy:/opt/puppet-git-repos/puppet/lib/puppet# ruby literal_hash.rb param_one: 2 param_two: 3 param_three: 8 param_four: 2 param_five: 3 param_six: 3 Add Comment
Jira (PUP-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Nicholas Fagerlund commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match Henrik Lindberg Eric Sorenson Hmm, so it looks like this fix expects that non-regexp node definitions will never have a name that conflicts with the name of a class, right? Given the behavior around truncated hostnames (https://docs.puppetlabs.com/puppet/3.7/reference/lang_node_definitions.html#matching), I believe we can't rely on that. We should probably apply a (different) prefix to literal node names, as well. Obligatory reminder that we have no reliable abstract way to refer to node scope, so it's effectively anonymous. Obligatory reminder of that problem where Puppet can sometimes reduce disjoint regexes to identical node names if their special characters are removed, although I might be the only one who's mortally offended by that. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3829 pip package provider is broken on EL (where osfamily is RedHat) Change By: Kenn Hussey Sprint: RE2015-01-21 ,RE2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3832) Remove Warning on Ruby 2.1/ Windows about DL is deprecated, please use Fiddle
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3832 Remove Warning on Ruby 2.1/ Windows about DL is deprecated, please use Fiddle Change By: Kenn Hussey Sprint: RE2015-01-21 ,RE2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3801) HP-UX User Provider not resetting password expiration after changing password hash.
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3801 HP-UX User Provider not resetting password expiration after changing password hash. Change By: Kenn Hussey Sprint: RE2015-01-21 ,RE2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3848) Puppet 4.0.0 should update to Facter 2.4.0 and MCO 2.7.1
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3848 Puppet 4.0.0 should update to Facter 2.4.0 and MCO 2.7.1 Change By: Rob Reynolds Summary: Puppet4.0.0shouldupdatetoFacter2.4.0andMCO2. 8 7 . 0 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3678) Invalid module name .DS_Store error running puppet apply
Title: Message Title Michael Smith assigned an issue to Anderson Mills Puppet / PUP-3678 Invalid module name .DS_Store error running puppet apply Change By: Michael Smith Assignee: AndersonMills Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3319) client should retry if connection to master fails
Title: Message Title Michael Smith updated an issue Puppet / PUP-3319 client should retry if connection to master fails Change By: Michael Smith Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3838) puppet console output for warning is red, which is unnecessarily alarming
Title: Message Title Nicholas Fagerlund commented on PUP-3838 Re: puppet console output for warning is red, which is unnecessarily alarming Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3319) client should retry if connection to master fails
Title: Message Title Michael Smith updated an issue Puppet / PUP-3319 client should retry if connection to master fails Change By: Michael Smith Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Nicholas Fagerlund commented on PUP-2564 Re: Specify UTF-8 as a default encoding for puppet I agree. Also, I consider the docs component done. In this file (https://docs.puppetlabs.com/puppet/latest/reference/lang_summary.html#files) we already said manifests should use UTF8; I'll change that to a stronger must and call it a day. I think we should resolve this ticket and open new tickets for implementation issues. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Nicholas Fagerlund assigned an issue to Kylo Ginsberg Puppet / PUP-2564 Specify UTF-8 as a default encoding for puppet Change By: Nicholas Fagerlund Assignee: NicholasFagerlund KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3844) Puppet MSI filename should be puppet-agent.msi by default
Title: Message Title Matthaus Owens commented on PUP-3844 Re: Puppet MSI filename should be puppet-agent.msi by default Ethan Brown Yep, what Rob Reynolds said. For the 3.x puppet series, it absolutely makes sense to keep puppet.msi as the x86 version, but being specific and updating the naming to always have the arch seems like a good change to make for puppet 4/AIO 1.0. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3639) Green: Puppet 4.0 Changes/Deprecations
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3639 Green: Puppet 4.0 Changes/Deprecations Change By: Steve Barlow Sub-team: EmeraldJade Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3640) Green: Puppet 5.0 Changes
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3640 Green: Puppet 5.0 Changes Change By: Steve Barlow Sub-team: EmeraldJade Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3832) Remove Warning on Ruby 2.1/ Windows about DL is deprecated, please use Fiddle
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-3832 Remove Warning on Ruby 2.1/ Windows about DL is deprecated, please use Fiddle Change By: Geoff Nichols Assignee: GeoffNichols Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3632) Update paths and defaults for the unified FS layout
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: William Hopper Assignee: WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3640) Green: Puppet 5.0 Changes
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3640 Green: Puppet 5.0 Changes Change By: Steve Barlow Scrum Team: PuppetServer Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Eric Thompson commented on PUP-3755 Re: Catalogs are transformed to resources outside of node environments Henrik Lindberg Josh Cooper using charlie's reproduction method above, i'm still getting production environment on first agent run: root@kutt1wfrtfey617:/etc/puppet# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: No file(s) found for import of '/tmp/bogus/*.pp' at /etc/puppet/environments/production/manifests/site.pp:2 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run ran against stable SHA 5818ce6. i can see the fix in the log... (commit c26c4ec5e2db174dbb91ceeb34faa8dade4b073d) Add Comment
Jira (PUP-3844) Puppet MSI filename should be puppet-agent.msi by default
Title: Message Title Ethan Brown commented on PUP-3844 Re: Puppet MSI filename should be puppet-agent.msi by default OK, just making sure that this was a change that we had discussed and had a reasoning behind. Sounds like you guys figured it out while I was away. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3548 4x function API's call_function cannot call a 3x function Change By: Henrik Lindberg Fix Version/s: PUP3.7.5 Fix Version/s: PUP3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Henrik Lindberg commented on PUP-3548 Re: 4x function API's call_function cannot call a 3x function Merged to stable at: 8c1a589 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3548 4x function API's call_function cannot call a 3x function Change By: Henrik Lindberg Fix Version/s: PUP3.7.4 Fix Version/s: PUP3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Henrik Lindberg commented on PUP-3548 Re: 4x function API's call_function cannot call a 3x function And the merge from stable to master did not apply cleanly and too much to figure out for 3.7.4 - The above merged was reverted at https://github.com/puppetlabs/puppet/commit/5818ce69f5205f4022f5a7641c35c75cdd9173df Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3166) Debian service provider on docker with insserv (dep boot sequencing)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3166 Debian service provider on docker with insserv (dep boot sequencing) Change By: Josh Cooper Component/s: Community Scrum Team: ReleaseEngineering Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3848) Puppet 4.0.0 should update to Facter 2.4.0 and MCO 2.7.1
Title: Message Title Ethan Brown commented on PUP-3848 Re: Puppet 4.0.0 should update to Facter 2.4.0 and MCO 2.7.1 Kylo Ginsberg to add release tickets for Facter and MCO as blockers here once they're created. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2531) Provide validation tool for EPP
Title: Message Title Nick Lewis commented on PUP-2531 Re: Provide validation tool for EPP Merged to master in 5224ead. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title Justin May assigned an issue to Justin May Puppet / PUP-3812 Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type Change By: Justin May Assignee: JustinMay Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3332) There should be a value? method to compliment the value and value= methods in properties
Title: Message Title Michael Smith updated an issue Puppet / PUP-3332 There should be a value? method to compliment the value and value= methods in properties Change By: Michael Smith Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3855) auth.conf no longer restricting based on environment
Title: Message Title Jeremy Barlow assigned an issue to Jeremy Barlow Puppet / PUP-3855 auth.conf no longer restricting based on environment Change By: Jeremy Barlow Assignee: JeremyBarlow Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3664) Invalid metadata.json in module root causes Error 400
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3664 Invalid metadata.json in module root causes Error 400 Change By: Josh Cooper Scrum Team: CodeManagement Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3850) Two User provider spec tests fail on RedHat systems
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-3850 Two User provider spec tests fail on RedHat systems Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3786) Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3786 Empty LiteralHash and LiteralList parameters get parsed with positioning information that excludes their closing delimiter Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3826) Update API docs for Puppet 4 URL changes
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3826 Update API docs for Puppet 4 URL changes Change By: Steve Barlow Sprint: SERVERnextcandidates Server2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3851) Remove v2.0 endpoints?
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3851 Remove v2.0 endpoints? Change By: Steve Barlow Sprint: SERVERnextcandidates Server2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3855) auth.conf no longer restricting based on environment
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3855 auth.conf no longer restricting based on environment Change By: Steve Barlow Sprint: SERVERnextcandidates Server2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing Change By: Rob Reynolds Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing Change By: Rob Reynolds Scrum Team: Windows ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing Change By: Rob Reynolds Component/s: Windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2638) Missing dependent directory from Puppet Agent install causes issues with resource graphing
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install causes issues with resource graphing Change By: Rob Reynolds Summary: MissingdependentdirectoryfromPuppetAgentinstall onWindowscausing causes issueswithresourcegraphing Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing Change By: Rob Reynolds Sprint: Windows2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1343) Service provider in RedHat will not create K?? stop scripts
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1343 Service provider in RedHat will not create K?? stop scripts Change By: Kenn Hussey Sprint: RE2015-01-07,RE2015-01-21 ,RE2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3854) Update the automation in puppet_for_the_win to retrieve cfacter from the right location
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3854 Update the automation in puppet_for_the_win to retrieve cfacter from the right location Change By: Kenn Hussey Sprint: RE2015-01-21 ,RE2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3853) Add cfacter to puppet/ext/build_defaults
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3853 Add cfacter to puppet/ext/build_defaults Change By: Kenn Hussey Sprint: RE2015-01-21 ,RE2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-3548 4x function API's call_function cannot call a 3x function Change By: Henrik Lindberg Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3639) Green: Puppet 4.0 Changes/Deprecations
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3639 Green: Puppet 4.0 Changes/Deprecations Change By: Steve Barlow Scrum Team: PuppetServer Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3812 Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type Change By: Steve Barlow Sprint: SERVERnextcandidates Server2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3843) Remove PE / FOSS branching (and branding) logic from puppet_for_the_win
Title: Message Title Ethan Brown commented on PUP-3843 Re: Remove PE / FOSS branching (and branding) logic from puppet_for_the_win puppet.wxs and puppet.wxi both have documentation / comment refs to 'enterprise', so it's not a huge deal (and why I still marked the ticket resolved) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Ethan Brown commented on PUP-2638 Re: Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing As noted in the PR, PUP-2638 should be implemented in a platform agnostic way, rather than in the Windows installer. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3865) Order dependent rspec failures in unit/service/provider/init_spec.rb
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-3865 Order dependent rspec failures in unit/service/provider/init_spec.rb Issue Type: Bug Assignee: Unassigned Created: 2015/01/21 7:53 AM Environment: 64-bit Fedora Core 21 Priority: Normal Reporter: Thomas Hallgren I get the spec failures with traces similar to the one below when running one of the following commands on a Fedora 21 (64-bit): bundle exec rake parallel:spec[4] or bundle exec rspec --seed 222 spec/unit/provider/service/init_spec.rb
Jira (PUP-3875) Tag the release and create packages
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-3875
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/01/21 12:47 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
Tag and create packages
Developer provides the SHA - Henrik Lindberg - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m 1.7.3 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PUP-3877) Go/no-go meeting (before 4pm)
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3877 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/01/21 12:47 PM Priority: Normal Reporter: Kylo Ginsberg This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Add Comment
Jira (PUP-3872) Merge master into stable
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3872 Merge master into stable Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/01/21 12:47 PM Priority: Normal Reporter: Kylo Ginsberg For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout stable
Jira (FACT-781) Facter 2.4.0 2014-01-22 Release
Title: Message Title William Hopper updated an issue Facter / FACT-781 Facter 2.4.0 2014-01-22 Release Change By: William Hopper Summary: puppet Facter 2.4.02014-01-22Release Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Change By: Steve Barlow Fix Version/s: PUP3.7.4 Fix Version/s: PUP3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3867) puppet 3.7.4 2014-01-27 Release
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3867 puppet 3.7.4 2014-01-27 Release Change By: Steve Barlow Scrum Team: ClientPlatform Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-784) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-784 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: William Hopper Created: 2015/01/21 12:13 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets targeted at the release have a corresponding commit git log old tag..new tag This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with Is there a JIRA ticket targeted at the release for every commit? and Is there a commit for every JIRA ticket targeted at the release? (it beats doing it manually, but requires manual steps and hacking the script for the specific release) There is also the release-inquisition, which also helps a lot with this task. Add Comment
Jira (FACT-783) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-783 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: William Hopper Created: 2015/01/21 12:13 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets referenced in the commit log have a bug targeted at the release git log old tag..new tag look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with Is there a JIRA ticket targeted at the release for every commit? and Is there a commit for every JIRA ticket targeted at the release? (it beats doing it manually, but requires manual steps and hacking the script for the specific release). There is also the release-inquisition, which also helps a lot with this task.
Jira (FACT-782) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-782 Is the code ready for release? Issue Type: Sub-task Assignee: William Hopper Created: 2015/01/21 12:13 PM Priority: Normal Reporter: Kylo Ginsberg If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20FACT%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.4.0%22
Jira (FACT-781) puppet 2.4.0 2014-01-22 Release
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-781 puppet 2.4.0 2014-01-22 Release Issue Type: Task Assignee: Release Engineering Created: 2015/01/21 12:13 PM Priority: Normal Reporter: Kylo Ginsberg puppet 2.4.0 2014-01-22 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the Prepare notes and Tag release/create packages tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for Tag Release/create packages, you should move Smoke test packages to Ready for Engineering or In Progress if you are ready.
Jira (FACT-786) Merge master into stable
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-786 Merge master into stable Issue Type: Sub-task Assignee: William Hopper Created: 2015/01/21 12:13 PM Priority: Normal Reporter: Kylo Ginsberg For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout stable
Jira (FACT-785) Update version number in source
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-785 Update version number in source Issue Type: Sub-task Assignee: William Hopper Created: 2015/01/21 12:13 PM Priority: Normal Reporter: Kylo Ginsberg Bump VERSION in lib/FACT/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m (packaging) Update FACTERVERSION to 1.7.3. If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Is there a commit for every JIRA ticket targeted at the release?
Jira (FACT-787) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-787 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: William Hopper Created: 2015/01/21 12:14 PM Priority: Normal Reporter: Kylo Ginsberg This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as Released in the Project Admin - Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the Release story ticket): 'project = XX AND affectedVersion = 'X.Y.Y', Save as Introduced in X.Y.Y, click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as Fixes for X.Y.Z, click Details, add permission for Everyone
Jira (FACT-788) Prepare long form release notes and short form release story
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-788 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/01/21 12:14 PM Priority: Normal Reporter: Kylo Ginsberg Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment
Jira (PUP-3866) File checksum should not be triggered when 'replace = false'
Title: Message Title
Marc Villacorta updated an issue
Puppet / PUP-3866
File checksum should not be triggered when 'replace = false'
Change By:
Marc Villacorta
WhenIapplythismanifest...{code:none} [root@kvm02~]#cattest.pp exec{'/usr/bin/ddif=/dev/urandomof=/tmp/big_file_01bs=1MBcount=100':creates='/tmp/big_file_01',}-file{['/tmp/big_file_02','/tmp/big_file_03','/tmp/big_file_04']:ensure=file,replace=false,source='/tmp/big_file_01',owner='root',group='root',mode='0644',}{code}...Igetthis_'strace'_count:{code:none}[root@kvm02~]#strace-eread-c-p`pgreppuppet`Process22667attached%timesecondsusecs/callcallserrorssyscall--100.000.2945072148649read--100.000.294507148649total{code}AndwhenIapplythisothermanifest...{code:none} [root@kvm02~]#cattest.pp exec{'/usr/bin/ddif=/dev/urandomof=/tmp/big_file_01bs=1MBcount=100':creates='/tmp/big_file_01',}-file{['/tmp/big_file_02','/tmp/big_file_03','/tmp/big_file_04']:ensure=file,replace=false,checksum='mtime',source='/tmp/big_file_01',owner='root',group='root',mode='0644',}{code}...Igetthisother_'strace'_count:{code:none}[root@kvm02~]#strace-eread-c-p`pgreppuppet`Process22931attached%timesecondsusecs/callcallserrorssyscall--100.000.145334275746read--100.000.14533475746total{code}SoevenifIset_'replace=false'_thechecksumseemstobecomputed.Setting_'checksum=none'_isnotallowedwhen_'source'_ispresent.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3866) File checksum should not be triggered when 'replace = false'
Title: Message Title
Marc Villacorta updated an issue
Puppet / PUP-3866
File checksum should not be triggered when 'replace = false'
Change By:
Marc Villacorta
WhenIapplythismanifest...{code:none}[root@kvm02~]#cattest.ppexec{'/usr/bin/ddif=/dev/urandomof=/tmp/big_file_01bs=1MBcount=100':creates='/tmp/big_file_01',}-file{['/tmp/big_file_02','/tmp/big_file_03','/tmp/big_file_04']:ensure=file,replace=false,source='/tmp/big_file_01',owner='root',group='root',mode='0644',}{code}...Igetthis_'strace'_count:{code:none}[root@kvm02~]#strace-eread-c-p`pgreppuppet` |teedefault_checksum.log Process22667attached%timesecondsusecs/callcallserrorssyscall--100.000.2945072148649read--100.000.294507148649total{code}AndwhenIapplythisothermanifest...{code:none}[root@kvm02~]#cattest.ppexec{'/usr/bin/ddif=/dev/urandomof=/tmp/big_file_01bs=1MBcount=100':creates='/tmp/big_file_01',}-file{['/tmp/big_file_02','/tmp/big_file_03','/tmp/big_file_04']:ensure=file,replace=false,checksum='mtime',source='/tmp/big_file_01',owner='root',group='root',mode='0644',}{code}...Igetthisother_'strace'_count:{code:none}[root@kvm02~]#strace-eread-c-p`pgreppuppet`Process22931attached%timesecondsusecs/callcallserrorssyscall--100.000.145334275746read--100.000.14533475746total{code}SoevenifIset_'replace=false'_thechecksumseemstobecomputed.Setting_'checksum=none'_isnotallowedwhen_'source'_ispresent.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (HI-311) puppet 1.4.0 2014-01-28 Release
Title: Message Title Kylo Ginsberg created an issue Hiera / HI-311 puppet 1.4.0 2014-01-28 Release Issue Type: Task Assignee: Release Engineering Created: 2015/01/21 12:53 PM Priority: Normal Reporter: Kylo Ginsberg puppet 1.4.0 2014-01-28 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the Prepare notes and Tag release/create packages tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for Tag Release/create packages, you should move Smoke test packages to Ready for Engineering or In Progress if you are ready.
Jira (PUP-3883) Support for user resource with a DOMAIN\User title
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-3883
Support for user resource with a DOMAIN\User title
Issue Type:
New Feature
Affects Versions:
PUP 3.7.0
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2015/01/21 1:00 PM
Labels:
customer
Priority:
Normal
Reporter:
Jay Wallace
User resource with a DOMAIN\User title should be supported behavior with Puppet. Puppet is not inherently aware of domain style names when defining a user in such a manner. For this to even theoretically work, the account that Puppet is running on would have to have domain administration credentials for this to ever work properly.
user { domain\\bud:
Jira (PUP-3867) puppet 3.7.4 2014-01-27 Release
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3867 puppet 3.7.4 2014-01-27 Release Change By: Steve Barlow Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-781) Facter 2.4.0 2014-01-22 Release
Title: Message Title Steve Barlow updated an issue Facter / FACT-781 Facter 2.4.0 2014-01-22 Release Change By: Steve Barlow Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1125) PuppetDB terminus fetches unstructured facts instead of structured
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1125 PuppetDB terminus fetches unstructured facts instead of structured Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1125) PuppetDB terminus fetches unstructured facts instead of structured
Title: Message Title Kenneth Barber commented on PDB-1125 Re: PuppetDB terminus fetches unstructured facts instead of structured I don't think this is a bug, I believe it was by design. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-311) hiera 1.4.0 2014-01-28 Release
Title: Message Title Steve Barlow updated an issue Hiera / HI-311 hiera 1.4.0 2014-01-28 Release Change By: Steve Barlow Sprint: Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Matthaus Owens created an issue Puppet / PUP-3884 Craft migration/upgrade script for use in the AIO puppet agent Issue Type: Bug Assignee: Unassigned Created: 2015/01/21 1:06 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Matthaus Owens To smooth the upgrade path for users, having an automated migration would be ideal. After discussion with platform team, the following list of steps was devised (copied from email): For puppet, we will copy their current puppet.conf and then do the following: Capture ssldir and copy all certs into new ssldir Copy any configuration files from old confdir into new confdir (routes.yaml, puppetdb.conf, hiera.yaml) Remove (or comment out) any deprecated settings in puppet.conf Remove disable_warnings If set, update environmentpath and basemodulepath to include new default paths. (if not present, do nothing)
Jira (PUP-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Change By: Steve Barlow Sprint: Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1640) Provide agnostic mechanism for Hiera Based Data in Modules
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1640 Provide agnostic mechanism for Hiera Based Data in Modules Change By: Steve Barlow Sprint: PlatformServer2014-11-26,PlatformServer2014-12-17,Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2531) Provide validation tool for EPP
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2531 Provide validation tool for EPP Change By: Steve Barlow Sprint: PlatformServer2014-12-17,Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2105) Puppet config face and the --configprint option operate directly on environment.conf.
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2105 Puppet config face and the --configprint option operate directly on environment.conf. Change By: Steve Barlow Sprint: Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3567) Remove current_environment check in Puppet::Indirector::Request#environment=
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3567 Remove current_environment check in Puppet::Indirector::Request#environment= Change By: Steve Barlow Sprint: Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3548) 4x function API's call_function cannot call a 3x function
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3548 4x function API's call_function cannot call a 3x function Change By: Steve Barlow Sprint: Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-658) facter doesn't parse gnu uptime output
Title: Message Title William Hopper updated an issue Facter / FACT-658 facter doesn't parse gnu uptime output Change By: William Hopper Fix Version/s: FACT2.3.1 Fix Version/s: FACT2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3884) Craft migration/upgrade script for use in the AIO puppet agent
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3884 Craft migration/upgrade script for use in the AIO puppet agent Change By: Kylo Ginsberg Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-311) hiera 1.4.0 2014-01-28 Release
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Hiera / HI-311 hiera 1.4.0 2014-01-28 Release Change By: Henrik Lindberg Assignee: KyloGinsberg ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3843) Remove PE / FOSS branching (and branding) logic from puppet_for_the_win
Title: Message Title Rob Reynolds commented on PUP-3843 Re: Remove PE / FOSS branching (and branding) logic from puppet_for_the_win Followed up with a maint commit into master at 17c75bfc. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-311) hiera 1.4.0 2014-01-28 Release
Title: Message Title Steve Barlow updated an issue Hiera / HI-311 hiera 1.4.0 2014-01-28 Release Change By: Steve Barlow Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3868) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3868 Is the code ready for release? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/01/21 12:47 PM Priority: Normal Reporter: Kylo Ginsberg If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.7.4%22
Jira (PUP-3871) Update version number in source
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3871 Update version number in source Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/01/21 12:47 PM Priority: Normal Reporter: Kylo Ginsberg Bump VERSION in lib/PUP/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m (packaging) Update FACTERVERSION to 1.7.3. If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-3867) puppet 3.7.4 2014-01-27 Release
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3867 puppet 3.7.4 2014-01-27 Release Issue Type: Task Assignee: Release Engineering Created: 2015/01/21 12:47 PM Priority: Normal Reporter: Kylo Ginsberg puppet 3.7.4 2014-01-27 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the Prepare notes and Tag release/create packages tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for Tag Release/create packages, you should move Smoke test packages to Ready for Engineering or In Progress if you are ready.
Jira (PUP-3870) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3870 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/01/21 12:47 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets targeted at the release have a corresponding commit git log old tag..new tag This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with Is there a JIRA ticket targeted at the release for every commit? and Is there a commit for every JIRA ticket targeted at the release? (it beats doing it manually, but requires manual steps and hacking the script for the specific release) There is also the release-inquisition, which also helps a lot with this task. Add Comment
Jira (PUP-3869) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3869 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/01/21 12:47 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets referenced in the commit log have a bug targeted at the release git log old tag..new tag look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with Is there a JIRA ticket targeted at the release for every commit? and Is there a commit for every JIRA ticket targeted at the release? (it beats doing it manually, but requires manual steps and hacking the script for the specific release). There is also the release-inquisition, which also helps a lot with this task.
Jira (FACT-546) facter fails when on non standard nic
Title: Message Title William Hopper updated an issue Facter / FACT-546 facter fails when on non standard nic Change By: William Hopper Fix Version/s: FACT2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3341) Puppet apply breaks when an ENC returns an environment
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3341 Puppet apply breaks when an ENC returns an environment Change By: Steve Barlow Sprint: Language2015-01-21 ,Language2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-311) hiera 1.4.0 2014-01-28 Release
Title: Message Title Steve Barlow updated an issue Hiera / HI-311 hiera 1.4.0 2014-01-28 Release Change By: Steve Barlow Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1343) Service provider in RedHat will not create K?? stop scripts
Title: Message Title
Kurt Wall commented on PUP-1343
Re: Service provider in RedHat will not create K?? stop scripts
Verified in stable at SHA=5818ce6. K?? and S?? symlinks are created when packages are enabled.
After installing the package, the K?? symlinks are created:
# puppet resource package httpd ensure=latest
Warning: The package type's allow_virtual parameter will be changing its default
value from false to true in a future release. If you do not want to allow virtual
packages, please explicitly set allow_virtual to false.
(at /usr/lib/ruby/site_ruby/1.8/puppet/type/package.rb:430:in `default')
Notice: /Package[httpd]/ensure: created
package { 'httpd':
ensure = '2.2.3-87.el5.centos',
}
# ls -l
Jira (PUP-1073) Common package name in two different providers
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1073 Common package name in two different providers Change By: Steve Barlow Sprint: PlatformClient2014-11-26,PlatformClient2014-12-17,PlatformClient2015-01-07,PlatformClient2015-01-21 ,PlatformClient2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-2402) Add acceptance tests for sshkey type
Title: Message Title Steve Barlow updated an issue Puppet / PUP-2402 Add acceptance tests for sshkey type Change By: Steve Barlow Sprint: PlatformClient2015-01-21 ,PlatformClient2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3656 Prefetch eats all exceptions, there is no way to fail out. Change By: Steve Barlow Sprint: PlatformClient2015-01-21 ,PlatformClient2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3850) Two User provider spec tests fail on RedHat systems
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3850 Two User provider spec tests fail on RedHat systems Change By: Steve Barlow Sprint: PlatformClient2015-01-21 ,PlatformClient2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-314) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Hiera / HI-314 Is there a commit for every JIRA ticket targeted at the release? Change By: Henrik Lindberg Assignee: HenrikLindberg ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
