Jira (PDB-2797) Update version number in source (PDB 4.1.2)
Title: Message Title Molly Waggett commented on PDB-2797 Re: Update version number in source (PDB 4.1.2) Andrew Roetker Did you do this today (Fri 6/17)? Is that what I was seeing on the channel earlier? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2316) Attributes attribute will not accept a single value for the User resource in AIX
Title: Message Title William Hopper assigned an issue to Maggie Dreyer Puppet / PUP-2316 Attributes attribute will not accept a single value for the User resource in AIX Change By: William Hopper Assignee: Kylo Ginsberg Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2316) Attributes attribute will not accept a single value for the User resource in AIX
Title: Message Title William Hopper updated an issue Puppet / PUP-2316 Attributes attribute will not accept a single value for the User resource in AIX Change By: William Hopper Scope Change Category: Adopted Scope Change Reason: Quick onboarding ticket Story Points: 1 Sprint: Client 2016-06-29 (failover) Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PDB-2793) Add optional destination path argument to stockpile/discard
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2793 Add optional destination path argument to stockpile/discard Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2638) Refactor runtime validation of catalogs
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2638 Refactor runtime validation of catalogs Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2810) Update benchmark tool and samples
Title: Message Title Andrew Roetker commented on PDB-2810 Re: Update benchmark tool and samples Additions to think about here are unchanged resources on reports, cached_catalog_status, catalog_uuid, and code_id additions. Also the addition of producer in the latest wire-format version bump. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2810) Update benchmark tool and samples
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-2810 Update benchmark tool and samples Issue Type: Improvement Assignee: Unassigned Created: 2016/06/17 1:36 PM Fix Versions: PDB 4.2.0 Priority: Normal Reporter: Molly Waggett The benchmark tool currently uses out of date command versions for catalogs, reports, and factsets: catalogs -> 9 reports -> 8 factsets -> 5 The benchmark samples are also out of date. We need new ones that match the current wireformat schemas. Add Comment
Jira (PUP-6376) Add `server_urls` option to puppet with agent failover logic
Title: Message Title Josh Cooper commented on PUP-6376 Re: Add `server_urls` option to puppet with agent failover logic About the "not restricted part" is this saying if the agent has 3 servers, it tries to pluginsync, but fails, and falls over to the next master B, and then later does a catalog request, will it continue using master B, and if that fails go to C? Or does it start over at the beginning of the list each time the agent makes an HTTP request? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6377) Deprecate the `server` option (if we decide to actually deprecate it)
Title: Message Title Josh Cooper commented on PUP-6377 Re: Deprecate the `server` option (if we decide to actually deprecate it) I'd suggest not deprecating it, but ignoring it if both server and the new option are both specified. --server is used extensively in puppet, module and PE acceptance testing: https://github.com/search?l=ruby=user%3Apuppetlabs+--server=searchresults=Code=%E2%9C%93. Also modules use it: https://github.com/search?l=bash=user%3Apuppetlabs+--server=searchresults=Code=%E2%9C%93 Also mco puppet plugin supports it (though we're trying to unwind that). I imagine there are also cloudinit workflows that rely on passing --server... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2224) Create PDB CLI full stack tests
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2224 Create PDB CLI full stack tests Change By: Andrew Roetker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2224) Create PDB CLI full stack tests
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2224 Create PDB CLI full stack tests Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2224) Create PDB CLI full stack tests
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2224 Create PDB CLI full stack tests Change By: Andrew Roetker Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2768) Windows CLI support - Exceptions thrown from puppetdb-cli could crash kernelbase.dll / ntdll.dll
Title: Message Title Andrew Roetker commented on PDB-2768 Re: Windows CLI support - Exceptions thrown from puppetdb-cli could crash kernelbase.dll / ntdll.dll Does this affect the puppetdb-cli since were using Rust? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6125) verbose agent runs result data being sent to console and syslog
Title: Message Title William Hopper assigned an issue to Unassigned Puppet / PUP-6125 verbose agent runs result data being sent to console and syslog Change By: William Hopper Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6125) verbose agent runs result data being sent to console and syslog
Title: Message Title William Hopper updated an issue Puppet / PUP-6125 verbose agent runs result data being sent to console and syslog Change By: William Hopper Scope Change Category: Adopted Scope Change Reason: Community PR brought in for CI. Story Points: 0 Sprint: Client 2016-06-29 (failover) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-2799) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2799 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2809) Close all resolved tickets in Jira (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2809 Close all resolved tickets in Jira (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2808) Update dujour to notify users to use 4.1.2 (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2808 Update dujour to notify users to use 4.1.2 (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2803) Go/no-go meeting (before noon PST) (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2803 Go/no-go meeting (before noon PST) (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2802) Smoke test packages (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2802 Smoke test packages (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2796) Reconcile git commits and JIRA tickets (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2796 Reconcile git commits and JIRA tickets (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2797) Update version number in source (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2797 Update version number in source (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2805) Packages pushed (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Sara Meisburger PuppetDB / PDB-2805 Packages pushed (PDB 4.1.2) Change By: Wyatt Alt Assignee: Morgan Rhodes Sara Meisburger Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2795) Is the code ready for release? (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2795 Is the code ready for release? (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2798) Merge master into stable (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Molly Waggett PuppetDB / PDB-2798 Merge master into stable (PDB 4.1.2) Change By: Wyatt Alt Assignee: Wyatt Alt Molly Waggett Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2804) Push tag (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Sara Meisburger PuppetDB / PDB-2804 Push tag (PDB 4.1.2) Change By: Wyatt Alt Assignee: Morgan Rhodes Sara Meisburger Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2801) Tag the release and create packages (PDB 4.1.2)
Title: Message Title Wyatt Alt assigned an issue to Sara Meisburger PuppetDB / PDB-2801 Tag the release and create packages (PDB 4.1.2) Change By: Wyatt Alt Assignee: Morgan Rhodes Sara Meisburger Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2789) latest report id index makes /nodes queries slow
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2789 latest report id index makes /nodes queries slow Change By: Wyatt Alt Fix Version/s: PDB 4.1.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6412) Add the ability to pass a filter to classifier API requests.
Title: Message Title Erik Hansen commented on PUP-6412 Re: Add the ability to pass a filter to classifier API requests. This would be useful if you wanted to return only a list of nodes belonging to the group, for example. Node names would be listed in the 'rules' key and it would be a quick way to get a list of nodes in a group from the API. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6416) Module Skeleton should have a working beaker(-rspec) setup and broken test
Title: Message Title Eric Thompson created an issue Puppet / PUP-6416 Module Skeleton should have a working beaker(-rspec) setup and broken test Issue Type: New Feature Assignee: Unassigned Components: PMT Created: 2016/06/17 10:46 AM Priority: Normal Reporter: Eric Thompson tests/ was renamed, and appropriately so. we could enable more testing through the production of a "good" (acceptance) testing dir containing (but not limited to): vagrant hosts file script/Rakefile for running tests (one each for beaker and beaker-rspec?) broken/simple test (one each for beaker and beaker-rspec?)
Jira (PDB-2797) Update version number in source (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2797 Update version number in source (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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-2808) Update dujour to notify users to use 4.1.2 (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2808 Update dujour to notify users to use 4.1.2 (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:37 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) Update dujour to notify users to use 4.1.2. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2809) Close all resolved tickets in Jira (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2809 Close all resolved tickets in Jira (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:37 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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.1.2%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 (PDB-2796) Reconcile git commits and JIRA tickets (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2796 Reconcile git commits and JIRA tickets (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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
Jira (PDB-2798) Merge master into stable (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2798 Merge master into stable (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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
Jira (PDB-2794) puppetdb 4.1.2 2016-06-22 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2794 puppetdb 4.1.2 2016-06-22 Release Issue Type: Task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt puppetdb 4.1.2 2016-06-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 (PDB-2799) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2799 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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 =
Jira (PDB-2804) Push tag (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2804 Push tag (PDB 4.1.2) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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-2803) Go/no-go meeting (before noon PST) (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2803 Go/no-go meeting (before noon PST) (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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 Kurt Wall Morgan Rhodes
Jira (PDB-2795) Is the code ready for release? (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2795 Is the code ready for release? (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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.1.2%22
Jira (PDB-2807) Send out announcements (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2807 Send out announcements (PDB 4.1.2) Issue Type: Sub-task Assignee: Beth Cornils Created: 2016/06/17 10:37 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) Morgan Rhodes: 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"
Jira (PDB-2806) Docs pushed (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2806 Docs pushed (PDB 4.1.2) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/06/17 10:37 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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.13#64028-sha1:b7939e9)
Jira (PDB-2801) Tag the release and create packages (PDB 4.1.2)
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-2801
Tag the release and create packages (PDB 4.1.2)
Issue Type:
Sub-task
Assignee:
Morgan Rhodes
Created:
2016/06/17 10:36 AM
Priority:
Normal
Reporter:
Wyatt Alt
(Initial planned release date: 2016-06-22)
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-2805) Packages pushed (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2805 Packages pushed (PDB 4.1.2) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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-2802) Smoke test packages (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2802 Smoke test packages (PDB 4.1.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) 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-2800) Prepare long form release notes and short form release story (PDB 4.1.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2800 Prepare long form release notes and short form release story (PDB 4.1.2) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/06/17 10:36 AM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-06-22) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian
Jira (PUP-6125) verbose agent runs result data being sent to console and syslog
Title: Message Title William Hopper updated an issue Puppet / PUP-6125 verbose agent runs result data being sent to console and syslog Change By: William Hopper Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2793) Add optional destination path argument to stockpile/discard
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2793 Add optional destination path argument to stockpile/discard Issue Type: Improvement Assignee: Unassigned Created: 2016/06/17 9:57 AM Fix Versions: PDB 4.2.0 Priority: Normal Reporter: Rob Browning Aside from perhaps more general utility, this will support PDB's DLO. Also document that the discard transfer is best-effort, and that it's likely slower, and much less likely to be "safe" if the destination path's parent isn't on the same filesystem as the stockpile. Add Comment
Jira (PDB-2793) Add optional destination path argument to stockpile/discard
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2793 Add optional destination path argument to stockpile/discard Change By: Rob Browning Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6410) launchd service provider crashes if a zero-length file in the {System,}/Library/Launch{Daemon,Agent} directory exists
Title: Message Title
Branan Riley updated an issue
Puppet / PUP-6410
launchd service provider crashes if a zero-length file in the {System,}/Library/Launch{Daemon,Agent} directory exists
Change By:
Branan Riley
Story Points:
0
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6410) launchd service provider crashes if a zero-length file in the {System,}/Library/Launch{Daemon,Agent} directory exists
Title: Message Title
Branan Riley updated an issue
Puppet / PUP-6410
launchd service provider crashes if a zero-length file in the {System,}/Library/Launch{Daemon,Agent} directory exists
Change By:
Branan Riley
Sprint:
Client 2016-06-29 (failover)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Sean Griffin assigned an issue to qa Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2792) Release PuppetDB 4.1.2 for PE Only
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2792 Release PuppetDB 4.1.2 for PE Only Issue Type: Task Assignee: Andrew Roetker Created: 2016/06/17 8:58 AM Fix Versions: PDB 4.1.2 Priority: Normal Reporter: Andrew Roetker This is release is intended to quickly ship a PDB 4.1.2 to fix 2 performance issues related to a significant increase in IO from PDB Postgres usage. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-2791) Test stockpile/store's error cases more thoroughly.
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2791 Test stockpile/store's error cases more thoroughly. Change By: Rob Browning Summary: Test stockpile 's handling of / store's exceptional :stream-data error cases more thoroughly. Once we settle on the rest of the API details, test stockpile/store's error cases more thoroughly, i.e. handling of store's exceptional :stream-data, careful handling of temp file deletion, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2791) Test stockpile's handling of store's exceptional :stream-data
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2791 Test stockpile's handling of store's exceptional :stream-data Change By: Rob Browning Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2791) Test stockpile's handling of store's exceptional :stream-data
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2791 Test stockpile's handling of store's exceptional :stream-data Issue Type: Bug Affects Versions: PDB 4.2.0 Assignee: Unassigned Created: 2016/06/17 8:42 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received
Jira (PUP-6370) systemd provider does not honor documented enabled states
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6370 systemd provider does not honor documented enabled states Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6413) Pip provider fails when using ensure => latest
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6413 Pip provider fails when using ensure => latest Change By: Kylo Ginsberg Affects Version/s: PUP 4.5.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6413) Pip provider fails when using ensure => latest
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6413 Pip provider fails when using ensure => latest Change By: Kylo Ginsberg Summary: Pip provider on 3.x fails when using ensure => latest Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-287) Research snapshot usage within Vagrant
Title: Message Title John O'Connor updated an issue Puppet / PUP-287 Research snapshot usage within Vagrant Change By: John O'Connor Issue Type: Task Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-291) Vagrant: Investigate / document pry remote debugging
Title: Message Title John O'Connor updated an issue Puppet / PUP-291 Vagrant: Investigate / document pry remote debugging Change By: John O'Connor Issue Type: Task Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-289) Vagrant: Standard VM Delivery Mechanism (Boxen?)
Title: Message Title John O'Connor updated an issue Puppet / PUP-289 Vagrant: Standard VM Delivery Mechanism (Boxen?) Change By: John O'Connor Issue Type: Task Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-287) Research snapshot usage within Vagrant
Title: Message Title John O'Connor updated an issue Puppet / PUP-287 Research snapshot usage within Vagrant Change By: John O'Connor Sub-team: Platforms Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-289) Vagrant: Standard VM Delivery Mechanism (Boxen?)
Title: Message Title John O'Connor updated an issue Puppet / PUP-289 Vagrant: Standard VM Delivery Mechanism (Boxen?) Change By: John O'Connor Sub-team: Platforms Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina commented on PDB-2753 Re: Use noop_pending flag from puppet agent report Kenneth Barber Susan McNerney I've updated the description to reflect the implementation in puppet core. The puppet core dependency has been merged. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-2753 Use noop_pending flag from puppet agent report Change By: Karel Brezina The field reflects result of flag indicates that the report contains noop puppet run.Possible values:- "changed" resource events ( noop run + out- i.e. there are changes that we decided not to apply because of -sync),- "unchanged" ( noop run + in-sync ) ,- "failed" (noop run + failure),- nil (enforcement puppet run) . This field flag needs to be queryable from both reports and nodes entity. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2753) Use noop_pending flag from puppet agent report
Title: Message Title Karel Brezina updated an issue PuppetDB / PDB-2753 Use noop_pending flag from puppet agent report Change By: Karel Brezina Summary: Use noop_status field noop_pending flag from puppet agent report Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Jürgen Thomann commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Henrik Lindberg, I have some classes from ENC which I can't remove, but I replaced them with empty classes. At the end I have some empty classes plus the inline_template and it still breaks. I would say that just using inline_template is enough in my case to trigger this error. Jeremy Barlow I used puppet-agent 1.3.5 before with puppetserver 2.2.1 and that worked without any problems for several weeks. I updated puppet on Monday 08:56:10 UTC and this error started Tuesday 22:37:34 UTC. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
