Jira (PUP-6835) Puppet does not check for revoked cert against puppetdb connection
Title: Message Title Klavs Klavsen commented on PUP-6835 Re: Puppet does not check for revoked cert against puppetdb connection We have restarted the puppetmaster several times.. (it does not always handle updating functions etc. when we change them the cert on puppetdb was updated several months ago - only issue we ever saw, was the puppet node deactivate issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6843) yum resync address
Title: Message Title Obaid Awan created an issue Puppet / PUP-6843 yum resync address Issue Type: Task Assignee: Unassigned Created: 2016/10/26 4:43 AM Environment: CentOS 7.2 Priority: Normal Reporter: Obaid Awan Hi there i want to create a local mirror of puppetlabs ,please would you help me to find out resync address for yum .i will be very thankful to you . Kindest Regards Obaid Add Comment
Jira (PDB-2851) reject POST query requests that are missing content-type
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2851 reject POST query requests that are missing content-type Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2836) perf dashboard queries for version every 5 seconds
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2836 perf dashboard queries for version every 5 seconds Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2938) (MAINT) Fix typo in dotted-query-to-path test
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2938 (MAINT) Fix typo in dotted-query-to-path test Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2962) (maint) Missing implicit inventory relationships
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2962 (maint) Missing implicit inventory relationships Change By: Ryan Senior Fix Version/s: PDB 4.3.0 Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2330) 'in' clause against a subquery doesn't work for fact-contents
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2330 'in' clause against a subquery doesn't work for fact-contents Change By: Ryan Senior Fix Version/s: PDB 4.3.0 Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3022) (MAINT) Bump to clj-i18n 0.4.3
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3022 (MAINT) Bump to clj-i18n 0.4.3 Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3044) (maint) Add MAINTAINERS file
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3044 (maint) Add MAINTAINERS file Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3047) PDB Changes required for 'corrective change' in CM's Event Inspector
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3047 PDB Changes required for 'corrective change' in CM's Event Inspector Change By: Ryan Senior Fix Version/s: pe everett Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3077) Integrate Ezbake service reload and logback/logrotate changes into PuppetDB
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3077 Integrate Ezbake service reload and logback/logrotate changes into PuppetDB Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3100) (MAINT) Bump beaker to 2.50.0
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3100 (MAINT) Bump beaker to 2.50.0 Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2939) Investigate convergence test timeout on 2016-08-02
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2939 Investigate convergence test timeout on 2016-08-02 Change By: Ryan Senior Fix Version/s: PDB 4.2.2 Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3065) Stop memoizing resource identity hashes
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3065 Stop memoizing resource identity hashes Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title daniel laval commented on PUP-6686 Re: Timespan sometimes parses fractions incorrectly. http://histoire-bateaux-aviron.fr/plombier-94/creteil-94000.html http://histoire-bateaux-aviron.fr/plombier-95/sarcelles-95200.html http://histoire-bateaux-aviron.fr/plombier-95/cergy-95127.html http://histoire-bateaux-aviron.fr/plombier-95/franconville-95130.html http://histoire-bateaux-aviron.fr/plombier-95/garges-les-gonesse-95140.html Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title
daniel laval updated an issue
Puppet / PUP-6686
Timespan sometimes parses fractions incorrectly.
Change By:
daniel laval
The following code, when applied,{code Voir plus : puppet} notice(strftime(Timespan('02 [http : 03 //histoire-bateaux-aviron . 4', '%M:%S fr/plombier-94/creteil-94000 . %L'), '%M html][http : %S //histoire-bateaux-aviron . %L')) fr/plombier-95/sarcelles-95200.html] {code}incorrectly notices{code}02 [http : 03 //histoire-bateaux-aviron . 004 fr/plombier-95/cergy-95127.html] {code}The reason is that the '4' is parsed by the '%L' format descriptor, and hence considered to be milliseconds [http://histoire-bateaux-aviron . While this is correct in some sense, it's not very intuitive fr/plombier-95/franconville-95130 . Puppet should instead do what Ruby's DateTime#strptime does and treat %L and %N as values to the right of a decimal point, i html][http://histoire-bateaux-aviron . e fr/plombier-95/garges-les-gonesse-95140 . a "4" is intepreted as "0.4", which means 4 nanoseconds. html]
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3118) Is the code ready for release? (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3118 Is the code ready for release? (PDB 4.2.4) Change By: Wyatt Alt Summary: Is the code ready for release? (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3120) Update version number in source (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3120 Update version number in source (PDB 4.2.4) Change By: Wyatt Alt Summary: Update version number in source (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3119) Reconcile git commits and JIRA tickets (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3119 Reconcile git commits and JIRA tickets (PDB 4.2.4) Change By: Wyatt Alt Summary: Reconcile git commits and JIRA tickets (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3117) PuppetDB 4.2.4 2016-10-26 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3117 PuppetDB 4.2.4 2016-10-26 Release Change By: Wyatt Alt Summary: PuppetDB 4.2. 5 4 2016-10-26 Release Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3121) Merge master into stable (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3121 Merge master into stable (PDB 4.2.4) Change By: Wyatt Alt Summary: Merge master into stable (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3124) Tag the release and create packages (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3124 Tag the release and create packages (PDB 4.2.4) Change By: Wyatt Alt Summary: Tag the release and create packages (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3123) Prepare long form release notes and short form release story (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3123 Prepare long form release notes and short form release story (PDB 4.2.4) Change By: Wyatt Alt Summary: Prepare long form release notes and short form release story (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3122) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3122 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.4) Change By: Wyatt Alt Summary: Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3126) Go/no-go meeting (before noon PST) (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3126 Go/no-go meeting (before noon PST) (PDB 4.2.4) Change By: Wyatt Alt Summary: Go/no-go meeting (before noon PST) (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3127) Push tag (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3127 Push tag (PDB 4.2.4) Change By: Wyatt Alt Summary: Push tag (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Ryan Senior Fix Version/s: PDB 4.2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3128) Packages pushed (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3128 Packages pushed (PDB 4.2.4) Change By: Wyatt Alt Summary: Packages pushed (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3131) Update dujour to notify users to use 4.2.4 (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3131 Update dujour to notify users to use 4.2.4 (PDB 4.2.4) Change By: Wyatt Alt Summary: Update dujour to notify users to use 4.2. 5 4 (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3132) Close all resolved tickets in Jira (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3132 Close all resolved tickets in Jira (PDB 4.2.4) Change By: Wyatt Alt Summary: Close all resolved tickets in Jira (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3129) Docs pushed (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3129 Docs pushed (PDB 4.2.4) Change By: Wyatt Alt Summary: Docs pushed (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3130) Send out announcements (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3130 Send out announcements (PDB 4.2.4) Change By: Wyatt Alt Summary: Send out announcements (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3125) Smoke test packages (PDB 4.2.4)
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3125 Smoke test packages (PDB 4.2.4) Change By: Wyatt Alt Summary: Smoke test packages (PDB 4.2. 5 4 ) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1510) Custom facts don't work correctly in Vagrant on Windows
Title: Message Title Rob Reynolds commented on FACT-1510 Re: Custom facts don't work correctly in Vagrant on Windows I'm seeing the same with facts in modules when the modules folder is symlinked in. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Rob Reynolds Summary: Custom Facts from symlinked folders ( facts .d / modules) don't work correctly in Vagrant on Windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3136) Update version number in source (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3136 Update version number in source (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:57 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Bump VERSION in lib/PDB/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? Reconcile git commits and JIRA tickets
Jira (PDB-3137) Merge master into stable (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3137 Merge master into stable (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:57 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) 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
Jira (PDB-3134) Is the code ready for release? (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3134 Is the code ready for release? (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:57 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) 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%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%224.3.0%22
Jira (PDB-3135) Reconcile git commits and JIRA tickets (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3135 Reconcile git commits and JIRA tickets (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:57 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier r
Jira (PDB-3133) PuppetDB 4.3.0 2016-11-03 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3133 PuppetDB 4.3.0 2016-11-03 Release Issue Type: Task Assignee: Wyatt Alt Created: 2016/10/26 9:57 AM Priority: Normal Reporter: Wyatt Alt PuppetDB 4.3.0 2016-11-03 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 (PDB-3139) Prepare long form release notes and short form release story (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3139 Prepare long form release notes and short form release story (PDB 4.3.0) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA
Jira (PDB-3140) Tag the release and create packages (PDB 4.3.0)
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-3140
Tag the release and create packages (PDB 4.3.0)
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2016/10/26 9:58 AM
Priority:
Normal
Reporter:
Wyatt Alt
(Initial planned release date: 2016-11-03)
Tag and create packages
Developer provides the SHA - Wyatt Alt - 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 (PDB-3145) Docs pushed (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3145 Docs pushed (PDB 4.3.0) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3143) Push tag (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3143 Push tag (PDB 4.3.0) Issue Type: Sub-task Assignee: Melissa Stone Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment
Jira (PDB-3144) Packages pushed (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3144 Packages pushed (PDB 4.3.0) Issue Type: Sub-task Assignee: Melissa Stone Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
Jira (PDB-3146) Send out announcements (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3146 Send out announcements (PDB 4.3.0) Issue Type: Sub-task Assignee: Beth Cornils Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependen
Jira (PDB-3142) Go/no-go meeting (before noon PST) (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3142 Go/no-go meeting (before noon PST) (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) 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 Participants: Wyatt Alt Nicholas Fagerlund Beth Cornils Ryan Gard Melissa Stone
Jira (PDB-3138) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3138 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) 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.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z'
Jira (PDB-3147) Update dujour to notify users to use 4.3.0 (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3147 Update dujour to notify users to use 4.3.0 (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Update dujour to notify users to use 4.3.0. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3141) Smoke test packages (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3141 Smoke test packages (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
Jira (PDB-3148) Close all resolved tickets in Jira (PDB 4.3.0)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3148 Close all resolved tickets in Jira (PDB 4.3.0) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/26 9:58 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-11-03) Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%224.3.0%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Facter 2 is EOL at the end of 2016. We need to figure out what we’re going to do with rubygem facter, especially since we need a solution to support users development workflows for running from source in CI.h5. In scope for Agent and Platform Team:- Explore viability of Facter 3 as a rubygem- Broadcast findings and gather feedback Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Facter 2 is EOL at the end of 2016. We need to figure out what we’re going to do with rubygem facter, especially since we need a solution for running Facter from source in CI.h5. In scope for Agent and Platform Team:- Explore viability of Facter 3 as a rubygem- Broadcast findings and gather feedback Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Facter 2 is EOL at the end of 2016. We need to figure out what we’re going to do with rubygem facter, especially since we need a solution to support users and development workflows for running from source in CI.h5. In scope for Agent and Platform Team:- Explore viability of Facter 3 as a rubygem- Broadcast findings and gather feedback Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Facter 2 is EOL at the end of 2016. We need to figure out what we’re going to do with rubygem facter, especially since we need a solution to support users and development workflows for running from source in CI.h5. In scope for Agent and Platform Team:- Explore viability of Facter 3 as a rubygem- Broadcast findings and gather feedback h5. Notes- Explore implications for toolchains (including distro toolchains)- Explore implications of linking Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Verne Lindner commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed Scott Walker Would you take a look at PE-17901: will that solve this ticket's issue? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3117) PuppetDB 4.2.4 2016-10-26 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3117 PuppetDB 4.2.4 2016-10-26 Release Change By: Wyatt Alt Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Alex Dreyer assigned an issue to Zach Reichert Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Alex Dreyer Assignee: qa Zach Reichert Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3117) PuppetDB 4.2.4 2016-10-26 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3117 PuppetDB 4.2.4 2016-10-26 Release Change By: Wyatt Alt Labels: maintenance Team: Foundational Features Sprint: FF 2016-11-02 PuppetDB 4.2. 5 4 2016-10-26 ReleaseWhen working through this ticket, add it to the board and then keep it in the Ready for Engineering column.Move the subtasks to In Progress when you are working on them and Resolved when you have completed them.In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. * The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. * Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. * When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-s
Jira (FACT-1384) Remove deprecated APIs necessitated by Server 2003 compat
Title: Message Title Michael Smith updated an issue Facter / FACT-1384 Remove deprecated APIs necessitated by Server 2003 compat Change By: Michael Smith Release Notes Summary: Related to OS support, should be documented in any change in supported platforms. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Sprint: AP Grooming 2016-11-16 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support
Title: Message Title Branan Riley updated an issue Puppet / PUP-6806 Update beaker version to 3.1.0 to allow MacOS Sierra testing Support Change By: Branan Riley Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6839) Bump version.rb for 1.8.0 release
Title: Message Title Branan Riley updated an issue Puppet / PUP-6839 Bump version.rb for 1.8.0 release Change By: Branan Riley Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6827) Address puppet acceptance test failures on windows server 2016
Title: Message Title Branan Riley updated an issue Puppet / PUP-6827 Address puppet acceptance test failures on windows server 2016 Change By: Branan Riley Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6790) acceptance: file resource with and without trailing slash
Title: Message Title Branan Riley updated an issue Puppet / PUP-6790 acceptance: file resource with and without trailing slash Change By: Branan Riley Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6779) acceptance: puppet generate
Title: Message Title Branan Riley updated an issue Puppet / PUP-6779 acceptance: puppet generate Change By: Branan Riley Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6791) acceptance: add then and other functions to calling_all_functions test
Title: Message Title Branan Riley updated an issue Puppet / PUP-6791 acceptance: add then and other functions to calling_all_functions test Change By: Branan Riley Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6807) referencing non-existant variable in custom function crashes puppetserver
Title: Message Title Justin Stoller updated an issue Puppet / PUP-6807 referencing non-existant variable in custom function crashes puppetserver Change By: Justin Stoller Release Notes Summary: Puppet extensions with Ruby errors (specifically noted in custom functions that referenced undefined local variables) would cause Puppet to create an error message that contained most of the Ruby object space. This message could be gigabytes in size and under load would cause the Puppet Server process to die with an OutOfMemoryError. Now failure to load a Puppet extension will create a reasonably short error string that will *not* use gigabytes of memory. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6844) ignore mercurial artifacts (.hg)
Title: Message Title garrett honeycutt created an issue Puppet / PUP-6844 ignore mercurial artifacts (.hg) Issue Type: Bug Assignee: Unassigned Created: 2016/10/26 12:04 PM Priority: Normal Reporter: garrett honeycutt Just as we ignore SVN, CVS, and Git artifacts, we should also ignore those of Mercurial. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6844) ignore mercurial artifacts (.hg)
Title: Message Title garrett honeycutt commented on PUP-6844 Re: ignore mercurial artifacts (.hg) PR - https://github.com/puppetlabs/puppet/pull/5348 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6844) ignore mercurial artifacts (.hg)
Title: Message Title garrett honeycutt updated an issue Puppet / PUP-6844 ignore mercurial artifacts (.hg) Change By: garrett honeycutt Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Kenn Hussey Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1524) Update Mountpoint tests to exclude the AIX platforms.
Title: Message Title Stan Duffy assigned an issue to Stan Duffy Facter / FACT-1524 Update Mountpoint tests to exclude the AIX platforms. Change By: Stan Duffy Assignee: Stan Duffy Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1524) Update Mountpoint tests to exclude the AIX platforms.
Title: Message Title Stan Duffy created an issue Facter / FACT-1524 Update Mountpoint tests to exclude the AIX platforms. Issue Type: Task Assignee: Unassigned Created: 2016/10/26 1:59 PM Environment: Puppet Agent Manual Pipeline Priority: Normal Reporter: Stan Duffy This test is new and does not work correctly on AIX. It has been recommended by Branan Riley to go ahead and confine the test to exclude AIX. Add Comment
Jira (PUP-6845) Enable mount tests on AIX
Title: Message Title Michael Smith created an issue Puppet / PUP-6845 Enable mount tests on AIX Issue Type: New Feature Assignee: Unassigned Created: 2016/10/26 2:03 PM Fix Versions: PUP 4.y Priority: Normal Reporter: Michael Smith /etc/fstab doesn't exist on Solaris. The alternative seems to be /etc/vfstab (http://docs.oracle.com/cd/E23824_01/html/821-1459/fscreate-6.html), but there are other issues with these tests on Solaris as well. The mount tests at tests/resource/mount are disabled on Solaris in https://github.com/puppetlabs/puppet/pull/4219. Add Comment
Jira (PUP-6845) Enable mount tests on AIX
Title: Message Title Stan Duffy updated an issue Puppet / PUP-6845 Enable mount tests on AIX Change By: Stan Duffy Fix Version/s: PUP 4.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6845) Enable mount tests on AIX
Title: Message Title Stan Duffy updated an issue Puppet / PUP-6845 Enable mount tests on AIX Change By: Stan Duffy Reporter: Michael Smith Stan Duffy Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6845) Enable mount tests on AIX
Title: Message Title
Stan Duffy updated an issue
Puppet / PUP-6845
Enable mount tests on AIX
Change By:
Stan Duffy
{{/etc/fstab}} doesn't exist on Solaris AIX . The alternative seems to be {{/etc/vfstab}} (http://docs.oracle.com/cd/E23824_01/html/821-1459/fscreate-6.html), but there are other issues with these tests on Solaris as well.The mount tests at tests/resource/mount are disabled on Solaris in https://github.com/puppetlabs/puppet/pull/4219.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-126 Ruby quoting constructs are incompletely stripped from some docstrings Change By: William Hopper Sprint: PDS 2016-11-02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-126 Ruby quoting constructs are incompletely stripped from some docstrings Change By: William Hopper Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-126 Ruby quoting constructs are incompletely stripped from some docstrings Change By: William Hopper Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-126 Ruby quoting constructs are incompletely stripped from some docstrings Change By: William Hopper Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-130) Add note to README about linebreaks and indentation for long tag docs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-130 Add note to README about linebreaks and indentation for long tag docs Change By: William Hopper QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6845) Enable mount tests on AIX
Title: Message Title Stan Duffy commented on PUP-6845 Re: Enable mount tests on AIX Mount tests are disable in this PR: https://github.com/puppetlabs/facter/pull/1458 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1524) Update Mountpoint tests to exclude the AIX platforms.
Title: Message Title Stan Duffy commented on FACT-1524 Re: Update Mountpoint tests to exclude the AIX platforms. Test excluded on AIX here: https://github.com/puppetlabs/facter/pull/1458 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3125) Smoke test packages (PDB 4.2.4)
Title: Message Title Melissa Stone commented on PDB-3125 Re: Smoke test packages (PDB 4.2.4) Packages for this release have been built and staged at http://builds.puppetlabs.lan/puppetdb/4.2.4/ because automation is awesome. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3124) Tag the release and create packages (PDB 4.2.4)
Title: Message Title Melissa Stone commented on PDB-3124 Re: Tag the release and create packages (PDB 4.2.4) Packages are available for testing at http://builds.puppetlabs.lan/puppetdb/4.2.4/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1525) Swap facts are incorrect on AIX in Facter 3
Title: Message Title Adam Bottchen created an issue Facter / FACT-1525 Swap facts are incorrect on AIX in Facter 3 Issue Type: Bug Affects Versions: FACT 3.1.8 Assignee: Unassigned Created: 2016/10/26 3:18 PM Priority: Normal Reporter: Adam Bottchen Running PE 2016.2.0 on AIX 6, the swapsize and swapsize_mb facts report incorrect values. # swap -l device maj,mintotal free /dev/hd6 10, 2 17216MB 17206MB
Jira (FACT-1525) Swap facts are incorrect on AIX in Facter 3
Title: Message Title Adam Bottchen commented on FACT-1525 Re: Swap facts are incorrect on AIX in Facter 3 Recreated this issue on Facter 3.4.1 as well. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1525) Swap facts are incorrect on AIX in Facter 3
Title: Message Title Adam Bottchen updated an issue Facter / FACT-1525 Swap facts are incorrect on AIX in Facter 3 Change By: Adam Bottchen Affects Version/s: FACT 3.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1525) Swap facts are incorrect on AIX in Facter 3
Title: Message Title
Adam Bottchen updated an issue
Facter / FACT-1525
Swap facts are incorrect on AIX in Facter 3
Change By:
Adam Bottchen
Running PE 2016.2.0 on AIX 6, the swapsize and swapsize_mb facts report incorrect values.{code:java}# swap -ldevice maj,mintotal free/dev/hd6 10, 2 17216MB 17206MB# facter -p swapsize832.00 MiB# facter -p swapsize_mb832{code} Recreated this issue on PE 2016.4.0 as well:{code:java}# facter -p osfamilyAIX# facter -p kernelversion6100# facter --version3.4.1 (commit d0f32490f41ca12722c13e4c48d4572ae4f9bfdc)# lsps -aPage Space Physical Volume Volume Group Size %Used Active Auto Type Chksumhd6 hdisk0rootvg 17216MB 1 yes yeslv 0# swap -ldevice maj,mintotal free/dev/hd6 10, 2 17216MB 17206MB# facter -p swapsize832.00 MiB# facter -p swapsize_mb832{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3125) Smoke test packages (PDB 4.2.4)
Title: Message Title Wyatt Alt commented on PDB-3125 Re: Smoke test packages (PDB 4.2.4) tested on debian 8 and centos 7. looks good. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1525) Swap facts are incorrect on AIX in Facter 3
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1525 Swap facts are incorrect on AIX in Facter 3 Change By: Geoff Nichols Sprint: AP Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1356 External facts should be able to return structured data Change By: Geoff Nichols Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6803 puppet run status should be "failed" if there are failed generated resources Change By: Geoff Nichols Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
