Jira (PUP-5736) Remove usage of win32-process gem
Title: Message Title Glenn Sarti commented on PUP-5736 Re: Remove usage of win32-process gem Raised three tickets for the tasks mentioned by Ethan PUP-5780, PUP-5781 and PUP-5782 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5752) Replace win32-process calls with internal API implementations that are wide-string compatible
Title: Message Title Glenn Sarti commented on PUP-5752 Re: Replace win32-process calls with internal API implementations that are wide-string compatible Closing task is it is no longer required due to investigation work in PUP-5736 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5787) Merge master into stable (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5787 Merge master into stable (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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
Jira (PUP-5792) Go/no-go meeting (before 4pm) (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5792 Go/no-go meeting (before 4pm) (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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: Morgan Rhodes Jorie Tappa Morgan Rhodes qa Morgan Rhodes
Jira (PUP-5785) Reconcile git commits and JIRA tickets (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5785 Reconcile git commits and JIRA tickets (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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
Jira (PUP-5736) Add tests of win32-process gem with unicode paths
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5736 Add tests of win32-process gem with unicode paths The parent investigation ticket was closed as it was not required. Instead a few integration tests are to be created to ensure against regression failures Change By: Glenn Sarti Scope Change Category: Adopted Scope Change Reason: Parent ticket was closed as not required and this ticket brought into sprint to complete the trivial test work Sprint: Windows 2016-02-10 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this
Jira (PUP-5736) Investigate use of win32-process gem with unicode paths
Title: Message Title Glenn Sarti commented on PUP-5736 Re: Investigate use of win32-process gem with unicode paths PR Raised https://github.com/puppetlabs/puppet/pull/4613 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1337) facter#master fails to compile on AIX: Undefined symbol: pthread_cancel
Title: Message Title Michael Smith updated an issue Facter / FACT-1337 facter#master fails to compile on AIX: Undefined symbol: pthread_cancel Change By: Michael Smith Scope Change Category: Found Scope Change Reason: Blocks AIX builds Story Points: 2 Sprint: Client 2016-02-10 Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from
Jira (PUP-5782) Re-vendor Win32-Process gem inside of puppet-win32-ruby
Title: Message Title Glenn Sarti created an issue Puppet / PUP-5782 Re-vendor Win32-Process gem inside of puppet-win32-ruby Issue Type: Task Assignee: Unassigned Created: 2016/02/01 11:00 AM Labels: windows Priority: Normal Reporter: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because
Jira (PUP-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5703 Handle cached catalog and pluginsync inconsistencies Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5736) Investigate use of win32-process gem with unicode paths
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5736 Investigate use of win32-process gem with unicode paths Change By: Glenn Sarti Summary: Add tests Investigate use of win32-process gem with unicode paths Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5736) Remove usage of win32-process gem
Title: Message Title Glenn Sarti commented on PUP-5736 Re: Remove usage of win32-process gem Changing Story Points to 1 as it just required 3 tickets to be raised and a few integration tests to be written. Adding to the current sprint Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5736) Remove usage of win32-process gem
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5736 Remove usage of win32-process gem Change By: Glenn Sarti Story Points: 3 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5780) Create minor patch for Win32-Process gem
Title: Message Title Glenn Sarti created an issue Puppet / PUP-5780 Create minor patch for Win32-Process gem Issue Type: Task Assignee: Unassigned Created: 2016/02/01 10:52 AM Labels: windows i18n Priority: Minor Reporter: Glenn Sarti The investigation into the use non-english characters with the Win32-Process found found little work to be required. It was decided to submit a patch to the Win32-Process gem source code to protect Puppet from any future dependency on the gem. https://github.com/djberg96/win32-process/issues/21 No Puppetlabs QA required. Add Comment
Jira (PUP-5736) Add tests usage of win32-process gem with unicode
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5736 Add tests usage of win32-process gem with unicode Change By: Glenn Sarti Summary: Remove Add tests usage of win32-process gem with unicode Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2369) dashboard metrics are broken
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2369 dashboard metrics are broken Issue Type: Bug Affects Versions: PDB 4.0.0 Assignee: Unassigned Created: 2016/02/01 1:13 PM Priority: Normal Reporter: Wyatt Alt commands/sec and commands processed are both empty, and all non-retried messages appear to be counted as discarded Add Comment This message was sent by Atlassian JIRA
Jira (PUP-5781) Verify new Win32-Process gem includes upstream patch from Puppetlabs
Title: Message Title Glenn Sarti created an issue Puppet / PUP-5781 Verify new Win32-Process gem includes upstream patch from Puppetlabs Issue Type: Task Assignee: Unassigned Created: 2016/02/01 10:55 AM Labels: windows Priority: Trivial Reporter: Glenn Sarti Verify that the Puppetlabs supplied patch from PUP-5780 is included in new versions of the Win32-Security Gem and that puppet now includes that gem in the agent Add Comment
Jira (PUP-5788) Is the Jira tidy-up done for this release and prepared for the next one? (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5788 Is the Jira tidy-up done for this release and prepared for the next one? (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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
Jira (PUP-5784) Is the code ready for release? (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5784 Is the code ready for release? (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.8.6%22
Jira (PUP-5736) Add tests of win32-process gem with unicode paths
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-5736 Add tests of win32-process gem with unicode paths Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5795) Docs pushed (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5795 Docs pushed (PUP 3.8.6) Issue Type: Sub-task Assignee: Jorie Tappa Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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.12#64027-sha1:e3691cc)
Jira (PUP-5794) Packages pushed (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5794 Packages pushed (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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 (PUP-5796) Send out announcements (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5796 Send out announcements (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-03) 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 (PUP-5789) Prepare long form release notes and short form release story (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5789 Prepare long form release notes and short form release story (PUP 3.8.6) Issue Type: Sub-task Assignee: Jorie Tappa Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-03) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian
Jira (PUP-5797) Close all resolved tickets in Jira (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5797 Close all resolved tickets in Jira (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-03) Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.8.6%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 (PUP-5786) Update version number in source (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5786 Update version number in source (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-03) Bump VERSION in lib/PUP/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PUP-5793) Push tag (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5793 Push tag (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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 (PUP-5791) Smoke test packages (PUP 3.8.6)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5791 Smoke test packages (PUP 3.8.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2016-02-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 (PUP-5790) Tag the release and create packages (PUP 3.8.6)
Title: Message Title
Morgan Rhodes created an issue
Puppet / PUP-5790
Tag the release and create packages (PUP 3.8.6)
Issue Type:
Sub-task
Assignee:
Morgan Rhodes
Created:
2016/02/01 11:47 AM
Priority:
Normal
Reporter:
Morgan Rhodes
(Initial planned release date: 2016-02-03)
Tag and create packages
Developer provides the SHA - Morgan Rhodes - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PUP-5783) puppet 3.8.6 2016-02-03 Release
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-5783 puppet 3.8.6 2016-02-03 Release Issue Type: Task Assignee: Morgan Rhodes Created: 2016/02/01 11:47 AM Priority: Normal Reporter: Morgan Rhodes puppet 3.8.6 2016-02-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 (PUP-5569) acceptance: to ensure Resource Collectors can use resource references in search expressions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5569 acceptance: to ensure Resource Collectors can use resource references in search expressions Change By: Eric Thompson there is not currently a yaml terminus for the resource indirection. [~branan] and I to spike on creating one to fulfill this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2370) sample reports data is unsuitable for testing unchanged resources
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2370 sample reports data is unsuitable for testing unchanged resources Issue Type: Bug Assignee: Unassigned Created: 2016/02/01 1:15 PM Priority: Normal Reporter: Wyatt Alt our sample reports only contain resources for events, as they would in FOSS. We probably want 50-100x as many in there, or maybe a separate unshipped set for testing PE. We need to fix this so we can get a real sense of the size of unchanged resources at scale. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5560) Look at Improving Unicode for all Windows gems
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-5560
Look at Improving Unicode for all Windows gems
Change By:
Glenn Sarti
h4. win32-security - PUP-5538 / PUP-5735* {{win32-security}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.2.5/lib/win32/security/windows/functions.rb - see {{ConvertSidToStringSidA}}, {{ConvertStringSidToSidA}}, {{LookupAccountNameA}}, {{LookupAccountSidA}}* PUP-5538 for the majority of the work + minor cleanup in PUP-5735h4. win32-service - PUP-5757 / PUP-5758* https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-service-0.8.6/lib/win32/windows/functions.rb#L24-L75 - see {{CreateEventA}}, {{FormatMessageA}}, {{ChangeServiceConfigA}}, {{ChangeServiceConfig2A}}, {{CreateServiceA}}, {{EnumServicesStatusExA}}, {{GetServiceDisplayNameA}}, {{GetServiceKeyNameA}}, {{LookupPrivilegeValueA}}, {{OpenSCManagerA}}, {{OpenServiceA}}, {{QueryServiceConfigA}}, {{QueryServiceConfig2A}}, {{RegisterServiceCtrlHandlerExA}}, {{StartServiceA}}, {{StartServiceCtrlDispatcherA}}h4. win32-process - PUP-5752 / PUP-5736 / PUP-5780 / PUP-5781 / PUP-5782 * https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.7.4/lib/win32/process/functions.rb - see {{GetModuleHandleA}}, {{GetVersionExA}}, {{GetVolumeInformationA}}, {{CreateJobObjectA}}, {{OpenJobObjectA}}, {{ConvertSidToStringSidA}}h4. win32-eventlog - PUP-5755 / PUP-5756 * https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-eventlog-0.6.2/lib/win32/windows/functions.rb - see {{ClearEventLogA}}, {{LookupAccountSidA}}, {{OpenEventLogA}}, {{OpenBackupEventLogA}}, {{ReadEventLogA}}, {{RegConnectRegistryA}}, {{RegCreateKeyExA}}, {{RegisterEventSourceA}}, {{RegOpenKeyExA}}, {{RegQueryValueExA}}, {{RegSetValueExA}}, {{ReportEventA}}, {{CreateEventA}}, {{ExpandEnvironmentStringsA}}, {{FormatMessageA}}, {{LoadLibraryExA}}I have filed upstream tickets* https://github.com/djberg96/win32-security/issues/8* https://github.com/djberg96/win32-service/issues/32* https://github.com/djberg96/win32-process/issues/21* https://github.com/djberg96/win32-eventlog/issues/19
Add Comment
Jira (PUP-5736) Add tests of win32-process gem with unicode paths
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-5736 Add tests of win32-process gem with unicode paths Change By: Glenn Sarti Summary: Add tests usage of win32-process gem with unicode paths Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5779) Tree view of modules incomplete
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5779 Tree view of modules incomplete Change By: Kylo Ginsberg Scrum Team: Code Management Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5799) Can we send email specific to a host?
Title: Message Title Teena Abraham created an issue Puppet / PUP-5799 Can we send email specific to a host? Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2016/02/01 2:10 PM Priority: Normal Reporter: Teena Abraham Please let me know if Puppet has a feature which can send emails specific to an environment? The tagmail feature sends emails of all the agents communicating to the master and that is not what we want in our implementation. Please advise. Br, Teena Add Comment
Jira (PDB-1411) KahaDB scheduler log files pile up
Title: Message Title Ryan Senior commented on PDB-1411 Re: KahaDB scheduler log files pile up I think is is a regression in ActiveMQ. I have created a ticket on the ActiveMQ side here. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5736) Investigate use of win32-process gem with unicode paths
Title: Message Title Ryan Gard assigned an issue to Glenn Sarti Puppet / PUP-5736 Investigate use of win32-process gem with unicode paths Change By: Ryan Gard Resolution: Fixed Assignee: Ryan Gard Glenn Sarti Status: Ready for Merge Resolved Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5117) Inline file checksums
Title: Message Title
Josh Cooper commented on PUP-5117
Re: Inline file checksums
Created a module with file content, when running the master with static_catalogs enabled, the compiler inlines checksum and checksum_value for file resources with a source parameter and puppet URI, using a checksum algorithm that the client and server share:
On the master with static_catalogs enabled:
class ntp {
file { '/tmp/ntpd.conf':
ensure => file,
source => 'puppet:///modules/ntp/ntpd.conf'
}
file { '/tmp/content':
ensure => file,
content => 'some content'
}
Jira (PUP-5800) Filenames in recursive directories appear to be shell expanded
Title: Message Title Ben Ford created an issue Puppet / PUP-5800 Filenames in recursive directories appear to be shell expanded Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2016/02/01 2:37 PM Priority: Normal Reporter: Ben Ford When a file in a directory used as a source for a recursive file resource starts with a ~, then it's evaluated as a username. I didn't check to see if other patterns expand. This is a real edge case, except that some editors save backup files with a prepended ~. root@ip-172-31-8-159:~ # puppet apply test.pp Notice: Compiled catalog for puppetfactory.puppetlabs.vm in environment production in 0.03 seconds Notice: /Stage[main]/Main/File[/tmp/test]/ensure: created
Jira (PUP-5736) Investigate use of win32-process gem with unicode paths
Title: Message Title Ryan Gard assigned an issue to Ryan Gard Puppet / PUP-5736 Investigate use of win32-process gem with unicode paths Change By: Ryan Gard Assignee: Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5560) Look at Improving Unicode for all Windows gems
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-5560
Look at Improving Unicode for all Windows gems
Change By:
Glenn Sarti
h4. win32-security - PUP-5538 / PUP-5735* {{win32-security}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.2.5/lib/win32/security/windows/functions.rb - see {{ConvertSidToStringSidA}}, {{ConvertStringSidToSidA}}, {{LookupAccountNameA}}, {{LookupAccountSidA}}* PUP-5538 for the majority of the work + minor cleanup in PUP-5735h4. win32-service - PUP-5757 / PUP-5758* https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-service-0.8.6/lib/win32/windows/functions.rb#L24-L75 - see {{CreateEventA}}, {{FormatMessageA}}, {{ChangeServiceConfigA}}, {{ChangeServiceConfig2A}}, {{CreateServiceA}}, {{EnumServicesStatusExA}}, {{GetServiceDisplayNameA}}, {{GetServiceKeyNameA}}, {{LookupPrivilegeValueA}}, {{OpenSCManagerA}}, {{OpenServiceA}}, {{QueryServiceConfigA}}, {{QueryServiceConfig2A}}, {{RegisterServiceCtrlHandlerExA}}, {{StartServiceA}}, {{StartServiceCtrlDispatcherA}}h4. win32-process - PUP-5752 / PUP-5736 / PUP-5780 / PUP-5781 / PUP-5782 / PUP-5798 * https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.7.4/lib/win32/process/functions.rb - see {{GetModuleHandleA}}, {{GetVersionExA}}, {{GetVolumeInformationA}}, {{CreateJobObjectA}}, {{OpenJobObjectA}}, {{ConvertSidToStringSidA}}h4. win32-eventlog - PUP-5755 / PUP-5756 * https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-eventlog-0.6.2/lib/win32/windows/functions.rb - see {{ClearEventLogA}}, {{LookupAccountSidA}}, {{OpenEventLogA}}, {{OpenBackupEventLogA}}, {{ReadEventLogA}}, {{RegConnectRegistryA}}, {{RegCreateKeyExA}}, {{RegisterEventSourceA}}, {{RegOpenKeyExA}}, {{RegQueryValueExA}}, {{RegSetValueExA}}, {{ReportEventA}}, {{CreateEventA}}, {{ExpandEnvironmentStringsA}}, {{FormatMessageA}}, {{LoadLibraryExA}}I have filed upstream tickets* https://github.com/djberg96/win32-security/issues/8* https://github.com/djberg96/win32-service/issues/32* https://github.com/djberg96/win32-process/issues/21* https://github.com/djberg96/win32-eventlog/issues/19
Add Comment
Jira (PDB-2371) (maint) Fix misnamed mq metric
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2371 (maint) Fix misnamed mq metric Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Quick bug fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2371) (maint) Fix misnamed mq metric
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2371 (maint) Fix misnamed mq metric Change By: Andrew Roetker Fix Version/s: PDB 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1338) facter#master fails to compile on AIX: Undefined symbol: pthread_cancel
Title: Message Title Michael Smith moved an issue Facter / FACT-1338 facter#master fails to compile on AIX: Undefined symbol: pthread_cancel Change By: Michael Smith Key: LTH FACT - 80 1338 Project: Leatherman Facter Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2371) (maint) Fix misnamed mq metric
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2371 (maint) Fix misnamed mq metric Issue Type: Bug Assignee: Unassigned Created: 2016/02/01 2:02 PM Priority: Normal Reporter: gepetto-bot This commit renames the processed metric from discarded to processed. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2371) (maint) Fix misnamed mq metric
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2371 (maint) Fix misnamed mq metric Change By: gepetto-bot Sprint: PuppetDB 2016-02-10 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5799) Can we send email specific to a host?
Title: Message Title Henrik Lindberg commented on PUP-5799 Re: Can we send email specific to a host? This kind of question is better asked on the Puppet Ask site, or on the google Puppet user group. I am closing this ticket as incomplete. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5798) Puppet::Util::Execution.execute does not support UTF8 chars reported from STDOUT
Title: Message Title
Glenn Sarti created an issue
Puppet / PUP-5798
Puppet::Util::Execution.execute does not support UTF8 chars reported from STDOUT
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/02/01 1:40 PM
Environment:
Puppet Agent 4.3.2
Priority:
Normal
Reporter:
Glenn Sarti
Puppet::Util::Execution.execute does not support UTF8 chars reported from STDOUT.
Example Integration spec test;
describe "#execute (Windows) STDOUT", :if => Puppet.features.microsoft_windows? do
let(:utf8text) do
"utf8testfile" + [195, 164].pack('c*').force_encoding(Encoding::UTF_8)
Jira (PDB-2287) Add styling to small ERD diagram
Title: Message Title Verne Lindner assigned an issue to Verne Lindner PuppetDB / PDB-2287 Add styling to small ERD diagram Change By: Verne Lindner Assignee: Jason Gurley Verne Lindner Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5485) Update docs URLs in puppet source
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5485 Update docs URLs in puppet source Change By: Kylo Ginsberg Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5485) Update docs URLs in puppet source
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5485 Update docs URLs in puppet source Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5731) Specify that Puppet Language Source must be in UTF-8
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5731 Specify that Puppet Language Source must be in UTF-8 Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5724) Backport PUP-5693 (benchmark function loading) to stable 4.3.3
Title: Message Title Henrik Lindberg commented on PUP-5724 Re: Backport PUP-5693 (benchmark function loading) to stable 4.3.3 For FR, simply run bundle exec rake benchmark:function_loading Before this it blew up, now it doesn't. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5724) Backport PUP-5693 (benchmark function loading) to stable 4.3.3
Title: Message Title Henrik Lindberg commented on PUP-5724 Re: Backport PUP-5693 (benchmark function loading) to stable 4.3.3 merged to stable at: 2dbe8d2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5399) changes in environment.conf does not trigger env cache eviction
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5399 changes in environment.conf does not trigger env cache eviction Change By: Henrik Lindberg Fix Version/s: PUP 4.4.0 Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5399) changes in environment.conf does not trigger env cache eviction
Title: Message Title Henrik Lindberg commented on PUP-5399 Re: changes in environment.conf does not trigger env cache eviction So, looks like there is not a lot of problems around this - taking it off from PUP 4.4.0 and marking it 4.x instead (so we at least do not forget about this). Long term direction is different anyway (this problem goes away on its own). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5731) Specify that Puppet Language Source must be in UTF-8
Title: Message Title Henrik Lindberg commented on PUP-5731 Re: Specify that Puppet Language Source must be in UTF-8 Nicholas Fagerlund The spec is updated - see lexical_structure.md (at the very top). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-16) Refactor command line options to support commands
Title: Message Title Henrik Lindberg commented on NPUP-16 Re: Refactor command line options to support commands merged to master: fdfaa45 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5744) Remove non-JSON safe default_literal objects from classes_per_environment response
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5744 Remove non-JSON safe default_literal objects from classes_per_environment response Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5731) Specify that Puppet Language Source must be in UTF-8
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5731 Specify that Puppet Language Source must be in UTF-8 Change By: Henrik Lindberg Labels: DOCS Release Notes Summary: The language specification now specifies that all Puppet Language source text must be in UTF-8. Earlier this was expected, but not specified. See lexical_structure.md in the spec for more details. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5485) Update docs URLs in puppet source
Title: Message Title Kylo Ginsberg commented on PUP-5485 Re: Update docs URLs in puppet source This was fixed in a maint commit. Closing this. Watchers: feel free to reopoen if you feel that's an error! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5401) spec/integration/data_binding.rb fails when run in isolation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5401 spec/integration/data_binding.rb fails when run in isolation Change By: Henrik Lindberg Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5736) Remove usage of win32-process gem
Title: Message Title Ethan Brown commented on PUP-5736 Re: Remove usage of win32-process gem Yeah, not worth wholesale replacing if we're not exposed (I was mostly concerned about Unicode paths to binaries for create). As we talked about a little bit, I think there are a few things we should do (as a lower priority thing): Send a minor patch up to the win32-process gem code and replace any lingering A calls in https://github.com/djberg96/win32-process/blob/ffi/lib/win32/process/functions.rb - should be pretty quick, and will give us some piece of mind Wait for a new gem to be cut Re-vendor the updated gem inside of puppet-win32-ruby at some point Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5485) Update docs URLs in puppet source
Title: Message Title Susan McNerney commented on PUP-5485 Re: Update docs URLs in puppet source This issue shows a fix version of PUP 4.4.0. As this is a burnside-associated version, we need a scrum team associated with the ticket. Please update the scrum team field Susan, your friendly neighborhood release manager Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5485) Update docs URLs in puppet source
Title: Message Title Garrett Guillotte commented on PUP-5485 Re: Update docs URLs in puppet source The cited PR was merged in November. Not sure where this should go next. Does someone need to review, or is this OK to close? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2329) Revise sticky terminus failover
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2329 Revise sticky terminus failover Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2153) Update HA-guide for classification-based install procedure
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2153 Update HA-guide for classification-based install procedure Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5485) Update docs URLs in puppet source
Title: Message Title Garrett Guillotte assigned an issue to Hailee Kenney Puppet / PUP-5485 Update docs URLs in puppet source Change By: Garrett Guillotte Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2151) Update PE Modules for PuppetDB HA
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2151 Update PE Modules for PuppetDB HA Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2276) Remove usage of robert.hooke for tk-config
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2276 Remove usage of robert.hooke for tk-config Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2356) PQL: Design a methodology for descending into hashes for facts and such
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2356 PQL: Design a methodology for descending into hashes for facts and such Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2209) Surrogate keyify all the certnames
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2209 Surrogate keyify all the certnames Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2360) PQL: min(report_timestamp) on nodes returns 'column "report_timestamp" does not exist'
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2360 PQL: min(report_timestamp) on nodes returns 'column "report_timestamp" does not exist' Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2187) PQL: Design and investigate work for document aware projection
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2187 PQL: Design and investigate work for document aware projection Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2357) PQL: Decide on final group by syntax
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2357 PQL: Decide on final group by syntax Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2326) PQL: For docs, split out model from endpoints into a single doc
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2326 PQL: For docs, split out model from endpoints into a single doc Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2358) PQL: Investigate and potentialy implement the viability of missing filters being a valid query
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2358 PQL: Investigate and potentialy implement the viability of missing filters being a valid query Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2366) PQL: Create command line examples in docs for PQL
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2366 PQL: Create command line examples in docs for PQL Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1337) facter#master fails to compile on AIX: Undefined symbol: pthread_cancel
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-1337 facter#master fails to compile on AIX: Undefined symbol: pthread_cancel Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2213) Clean up our acceptance test helpers
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2213 Clean up our acceptance test helpers Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2311) Change command names to use `_` instead of `" "` or `-`
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2311 Change command names to use `_` instead of `" "` or `-` Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5779) Tree view of modules incomplete
Title: Message Title Henrik Lindberg commented on PUP-5779 Re: Tree view of modules incomplete Max Mustermann thanks for experimenting and confirming. Much appreciated. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5682) yumrepo doesn't handle enabled => false correctly
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5682 yumrepo doesn't handle enabled => false correctly Change By: Josh Cooper Sprint: Client Triage 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5527) (Control Catalog Compilation) As a puppet administrator, I can update the manifests on my master without causing agents to get those updates.
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5527 (Control Catalog Compilation) As a puppet administrator, I can update the manifests on my master without causing agents to get those updates. Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5531) (Static Catalog) As a puppet administrator, I want the agents to only attempt to fetch out-of-band file content when they know that the local content does not match desired state.
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5531 (Static Catalog) As a puppet administrator, I want the agents to only attempt to fetch out-of-band file content when they know that the local content does not match desired state. Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5534 (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/* Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5536) (Static Catalog) As a puppet administrator, when I enable direct puppet on my master, agents that do not support it should continue to update file content as they did previously
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5536 (Static Catalog) As a puppet administrator, when I enable direct puppet on my master, agents that do not support it should continue to update file content as they did previously Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5535 (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5706) As a puppet administrator, I want to know if and why a cached catalog was applied
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5706 As a puppet administrator, I want to know if and why a cached catalog was applied Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Severity: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5526 (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5705) As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5705 As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes Change By: Sean Griffin QA Risk Assessment Reason: This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2319) PQL: Pagination support
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2319 PQL: Pagination support Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2341) Unify example data to reflect real Puppet runs
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2341 Unify example data to reflect real Puppet runs Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5682) yumrepo doesn't handle enabled => false correctly
Title: Message Title Susan McNerney updated an issue Puppet / PUP-5682 yumrepo doesn't handle enabled => false correctly Change By: Susan McNerney Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2320) PQL: Produce a blog post about PQL
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2320 PQL: Produce a blog post about PQL Change By: Susan McNerney Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5121) Add profiling for file inlining
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5121 Add profiling for file inlining Change By: Sean Griffin QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1337) facter#master fails to compile on AIX: Undefined symbol: pthread_cancel
Title: Message Title Branan Riley commented on FACT-1337 Re: facter#master fails to compile on AIX: Undefined symbol: pthread_cancel Threading on AIX is pretty amazing. I'm unsure how a pthread_cancel snuck in, but generally we shouldn't be doing thread stuff at all there if we want to keep our sanity. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5779) Tree view of modules incomplete
Title: Message Title Max Mustermann commented on PUP-5779 Re: Tree view of modules incomplete Yes, then the output will change to: ├── stahnma-epel (v1.2.2) └─┬ puppetlabs-ntp (v4.1.2) └── puppetlabs-stdlib (v4.11.0) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5119) Handle file sources outside per-environment codedir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5119 Handle file sources outside per-environment codedir Change By: Josh Cooper Summary: Handle file sources outside per-environment codedir Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
