Jira (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title Henrik Lindberg commented on HI-530 Re: Hiera silently drops malformed hierarchy sources Rich tea Thanks for the contribution. I did some housekeeping on the ticket. Once something has been merged, the next state is "Ready for CI", which means that there needs to be a complete acceptance test run with the version in question before the ticket progresses to "Ready for Test" - this is manual testing and a review that the test coverage is suitable (in this case it should be quick). Finally, the ticket goes to Resolved, and it is finally closed/done when the release goes out (In this case the next Hiera release). 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 (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-530 Hiera silently drops malformed hierarchy sources Change By: Henrik Lindberg Story Points: 1 Sprint: Language 2016-08-24 Release Notes: Not Needed 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 (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Hiera / HI-530 Hiera silently drops malformed hierarchy sources Change By: Henrik Lindberg Assignee: Rich tea 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 (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-530 Hiera silently drops malformed hierarchy sources Change By: Henrik Lindberg Fix Version/s: HI 3.2.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 (PUP-6646) Could not find terminus file/rest for indirection file_metadata/node/catalog
Title: Message Title Henrik Lindberg commented on PUP-6646 Re: Could not find terminus file/rest for indirection file_metadata/node/catalog First, Puppet 4.6.0 was pulled today because of PUP-6608 which causes the compiler to not do the correct thing. The consequences of this problem are hard to predict. Suggest you try again with Puppet 4.6.1 (to be released today if all goes well). Secondly, without a reproducible case it is very hard for us to figure out what is going wrong in your environment. I am therefore going to close this ticket. Feel free to reopen if there are steps to take that reproduces the problem. 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-3016) Document the behavior regarding deactivated/expired nodes for the experimental root endpoint in the PuppetDB v4 API
Title: Message Title Wyatt Alt assigned an issue to Unassigned PuppetDB / PDB-3016 Document the behavior regarding deactivated/expired nodes for the experimental root endpoint in the PuppetDB v4 API Change By: Wyatt Alt Assignee: Wyatt Alt 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-3016) Document the behavior regarding deactivated/expired nodes for the experimental root endpoint in the PuppetDB v4 API
Title: Message Title Wyatt Alt commented on PDB-3016 Re: Document the behavior regarding deactivated/expired nodes for the experimental root endpoint in the PuppetDB v4 API Isaac Eldridge moved to the PDB project. thanks for the ping. 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-3016) Document the behavior regarding deactivated/expired nodes for the experimental root endpoint in the PuppetDB v4 API
Title: Message Title Wyatt Alt moved an issue PuppetDB / PDB-3016 Document the behavior regarding deactivated/expired nodes for the experimental root endpoint in the PuppetDB v4 API Change By: Wyatt Alt Scrum Team: PuppetDB Workflow: Documentation Scrum Teams Workflow Key: DOC PDB - 2890 3016 Project: Documentation [Internal] PuppetDB 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
Jira (PUP-6627) Puppet file `show_diff` setting leaks information
Title: Message Title
Eric Thompson commented on PUP-6627
Re: Puppet file `show_diff` setting leaks information
note that the redacted data will still show up in the cached catalog on the agent:
{"type":"File","title":"/tmp/sensitive_content_tdfxmzlv.txt","tags":["file","class"],"file":"/etc/puppetlabs/code/environments/se
nsitive_data_type_e01mn3qi/manifests/site.pp","line":13,"exported":false,"parameters":{"content":"sekritD"}
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-6646) Could not find terminus file/rest for indirection file_metadata/node/catalog
Title: Message Title Dan Dunckel updated an issue Puppet / PUP-6646 Could not find terminus file/rest for indirection file_metadata/node/catalog Change By: Dan Dunckel Attachment: screenshot-puppet-run.png 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-6646) Could not find terminus file/rest for indirection file_metadata/node/catalog
Title: Message Title
Dan Dunckel updated an issue
Puppet / PUP-6646
Could not find terminus file/rest for indirection file_metadata/node/catalog
Change By:
Dan Dunckel
After upgrading our environment from Foreman 1.11 to 1.12 and Puppet 3.75 to 4.6.0, this issue showed up on our 2 CentOS nodes: IMAGE TO BE ADDED !screenshot-puppet-run.png|thumbnail! It happens intermittenly, and I just don't know what to do to fix this.I read a bit about https://docs.puppet.com/puppet/latest/reference/indirection.html but I don't think my setup is proper (e.g. my {{puppet.conf}} has {{node_terminus = exec}}, which makes sense since we're using Foreman as an ENC)Please let me know what other info I may provide to help.Thanks
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-6646) Could not find terminus file/rest for indirection file_metadata/node/catalog
Title: Message Title Dan Dunckel created an issue Puppet / PUP-6646 Could not find terminus file/rest for indirection file_metadata/node/catalog Issue Type: Bug Affects Versions: PUP 4.6.0 Assignee: Unassigned Components: Puppet Server Created: 2016/08/23 3:17 PM Environment: Client: OS: CentOS (6.6 / 7.2) Puppet version: 4.6.0 Puppetserver: OS: Ubuntu 14.04 Version: 2.5.0 Priority: Normal Reporter: Dan Dunckel
Jira (PDB-3009) Go/no-go meeting (before noon PST) (PDB 4.2.2)
Title: Message Title Wyatt Alt commented on PDB-3009 Re: Go/no-go meeting (before noon PST) (PDB 4.2.2) Ryan Gard Chun Du nothing for you guys to do here really. I just needed a name to stick in there and Kurt Wall's been getting tired of the pings 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 (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title Rich tea commented on HI-530 Re: Hiera silently drops malformed hierarchy sources resolved by Pull #360 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-3009) Go/no-go meeting (before noon PST) (PDB 4.2.2)
Title: Message Title Ryan Gard commented on PDB-3009 Re: Go/no-go meeting (before noon PST) (PDB 4.2.2) Wyatt Alt I'll be on PTO starting tomorrow. Talk with Chun Du instead. 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-3009) Go/no-go meeting (before noon PST) (PDB 4.2.2)
Title: Message Title Ryan Gard updated an issue PuppetDB / PDB-3009 Go/no-go meeting (before noon PST) (PDB 4.2.2) Change By: Ryan Gard (Initial planned release date: 2016-08-25)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 testingParticipants: * [~wyatt] * [~nick.fagerlund] * [~beth.cornils] * - [~ryan.gard] - [~chun] * [~morgan] 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-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Ryan Senior commented on PDB-2985 Re: Fix excessive CPU usage by clj-i18n I used a JVM profiler. Specifically just tested command ingestion (i.e. set the mq message processing threads to 0) and submitted a bunch of commands using the benchmark utility we ship with PuppetDB. 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-3013) Send out announcements (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3013 Send out announcements (PDB 4.2.2) Issue Type: Sub-task Assignee: Beth Cornils Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3008) Smoke test packages (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3008 Smoke test packages (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3012) Docs pushed (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3012 Docs pushed (PDB 4.2.2) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3004) Merge master into stable (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3004 Merge master into stable (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3005) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3005 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3006) Prepare long form release notes and short form release story (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3006 Prepare long form release notes and short form release story (PDB 4.2.2) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian
Jira (PDB-3007) Tag the release and create packages (PDB 4.2.2)
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-3007
Tag the release and create packages (PDB 4.2.2)
Issue Type:
Sub-task
Assignee:
Morgan Rhodes
Created:
2016/08/23 2:23 PM
Priority:
Normal
Reporter:
Wyatt Alt
(Initial planned release date: 2016-08-25)
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-3003) Update version number in source (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3003 Update version number in source (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3010) Push tag (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3010 Push tag (PDB 4.2.2) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3015) Close all resolved tickets in Jira (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3015 Close all resolved tickets in Jira (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:24 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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.2.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-3009) Go/no-go meeting (before noon PST) (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3009 Go/no-go meeting (before noon PST) (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Wyatt Alt Nicholas Fagerlund Beth Cornils Ryan Gard Morgan Rhodes
Jira (PDB-3002) Reconcile git commits and JIRA tickets (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3002 Reconcile git commits and JIRA tickets (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3011) Packages pushed (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3011 Packages pushed (PDB 4.2.2) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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-3014) Update dujour to notify users to use 4.2.2 (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3014 Update dujour to notify users to use 4.2.2 (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:23 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) Update dujour to notify users to use 4.2.2. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-3000) PDB 4.2.2 2016-08-25 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3000 PDB 4.2.2 2016-08-25 Release Issue Type: Task Assignee: Wyatt Alt Created: 2016/08/23 2:22 PM Priority: Normal Reporter: Wyatt Alt PDB 4.2.2 2016-08-25 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-3001) Is the code ready for release? (PDB 4.2.2)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3001 Is the code ready for release? (PDB 4.2.2) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/08/23 2:22 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-08-25) 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.2.2%22
Jira (PUP-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6627 Puppet file `show_diff` setting leaks information Change By: Eric Thompson QA Risk Assessment: High 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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6627 Puppet file `show_diff` setting leaks information Change By: Eric Thompson QA Status: Reviewed 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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6627
Puppet file `show_diff` setting leaks information
Change By:
Eric Thompson
Release Notes Summary:
prior to this change, {{--show_diff}} for {{puppet agent}} and {{puppet apply}} could problematically show redacted data when a resource contained a Senstive data type.
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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6627 Puppet file `show_diff` setting leaks information Change By: Eric Thompson Release Notes: Bug Fix 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-1494) acceptance: facter.conf with external-dir and custom-dir
Title: Message Title Phong Ly created an issue Facter / FACT-1494 acceptance: facter.conf with external-dir and custom-dir Issue Type: Task Assignee: Phong Ly Created: 2016/08/23 1:34 PM Priority: Normal Reporter: Phong Ly Verify external and custom facts are loading correctly with external-dir and custom-dir defined in facter.conf file Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Doug Rosser commented on PDB-2985 Re: Fix excessive CPU usage by clj-i18n Any word of how to repro? 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-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2985 Fix excessive CPU usage by clj-i18n Change By: Susan McNerney Fix Version/s: PDB 4.2.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 (PDB-2999) evaluate usage of query-with-resultset for replacement with with-query-results-cursor
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2999 evaluate usage of query-with-resultset for replacement with with-query-results-cursor Issue Type: Improvement Assignee: Unassigned Created: 2016/08/23 12:19 PM Priority: Normal Reporter: Wyatt Alt query-with-resultset will hold all query results in memory, while with-query-results-cursor will not. Look at all usage of query-with-resultset and assess whether with-query-results-cursor would be better. This bleeds into a lot of cases due to the fact that query-with-resultset is called by query-to-vec. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title
Jeff Sparrow created an issue
Facter / FACT-1493
Could not retrieve local facts: failed to parse display name of moniker
Issue Type:
Bug
Affects Versions:
FACT 2.4.4
Assignee:
Unassigned
Components:
Windows
Created:
2016/08/23 12:14 PM
Priority:
Normal
Reporter:
Jeff Sparrow
Attempting to run puppet as a remote user on a windows install (so running under SYSTEM). The puppet run starts and I get:
Could not retrieve local facts: failed to parse display name of moniker `winmgmts:{impersonationLevel=impersonate}!//./root/cimv2' HRESULT error code:0x800401e4 Invalid syntax
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title
Jeff Sparrow updated an issue
Facter / FACT-1493
Could not retrieve local facts: failed to parse display name of moniker
Change By:
Jeff Sparrow
Attempting to run puppet , in a powershell script as a remote user , on a windows install script (so running under SYSTEM). The puppet run starts and I get:{code:} Could not retrieve local facts: failed to parse display name of moniker `winmgmts:{impersonationLevel=impersonate}!//./root/cimv2' HRESULT error code:0x800401e4 Invalid syntax{code}Not quite sure where to even begin on this. Any help is appreciated.
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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title
Eric Thompson commented on PUP-6627
Re: Puppet file `show_diff` setting leaks information
validated on ubuntu1404 at stable puppet-agent SHA:
#where vv tmpfile contains "old_content"
file{"/tmp/sensitive_content_jew2muk6.txt":content => Sensitive.new('sekritD')}
# puppet agent -t --show_diff --debug
Notice: /Stage[main]/Main/File[/tmp/sensitive_content_jew2muk6.txt]/content: [diff redacted]
Info: Computing checksum on file /tmp/sensitive_content_jew2muk6.txt
Info: FileBucket got a duplicate file {md5}459c0443d733636dfd11ebd8503fc1c0
Info: /Stage[main]/Main/File[/tmp/sensitive_content_jew2muk6.txt]: Filebucketed /tmp/sensitive_content_jew2muk6.txt to puppet with sum 459c0443d733636dfd11ebd8503fc1c0
Notice: /Stage[main]/Main/File[/tmp/sensitive_content_jew2muk6.txt]/content: changed [redacted] to [redacted]
Jira (PUP-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Adrien Thebo commented on PUP-6627 Re: Puppet file `show_diff` setting leaks information Ehh it's a bit weird, we can fix it in the next Puppet y release since it's basically cosmetic. 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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Eric Thompson commented on PUP-6627 Re: Puppet file `show_diff` setting leaks information Notify in first case, File in second case (as show-diff doesn't show anything for notifies as they don't really change) 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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Adrien Thebo commented on PUP-6627 Re: Puppet file `show_diff` setting leaks information Notify redaction, or from the notice function? 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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Eric Thompson commented on PUP-6627 Re: Puppet file `show_diff` setting leaks information is it strange that notify redaction says [value redacted] but show_diff redaction says changed [redacted] to [redacted] it shouldn't hold up this ticket/release, but it's a bit inconsistent (shrug) 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-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2985 Fix excessive CPU usage by clj-i18n Change By: Susan McNerney Labels: davis-triage pdb-ss 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-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2985 Fix excessive CPU usage by clj-i18n Change By: Susan McNerney Labels: pdb-ss 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-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: Kenn Hussey Flagged: Impediment 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-6623) Add function for unwrapping sensitive data
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6623 Add function for unwrapping sensitive data Change By: Kenn Hussey Flagged: Impediment 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Eric Thompson commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type this needs a release notes blurb 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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Eric Thompson commented on PUP-6627 Re: Puppet file `show_diff` setting leaks information this needs a release notes blurb 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-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6627 Puppet file `show_diff` setting leaks information Change By: Eric Thompson Assignee: qa Eric Thompson 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-2998) Merge stable into master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2998 Merge stable into master Issue Type: Bug Assignee: Unassigned Created: 2016/08/23 10:13 AM Priority: Normal Reporter: gepetto-bot 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-2997) OOM on upgrade to PDB 4.2.0
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2997 OOM on upgrade to PDB 4.2.0 Change By: Susan McNerney Summary: OOM on upgrade to PDB 4.2.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-2997) OOM on upgrade to 4.2.0
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2997 OOM on upgrade to 4.2.0 Change By: Susan McNerney Labels: davis-triage pdb-ss 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-2997) OOM on upgrade to 4.2.0
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2997 OOM on upgrade to 4.2.0 Change By: Susan McNerney Scrum Team: PuppetDB 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-2982) Create shorter command names for the stockpile metadata
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2982 Create shorter command names for the stockpile metadata Change By: Rob Browning Currently the command name is used in the Stockpile metadata string. There's nothing technical wrong with this, but it's long and it's less user friendly as there's spaces. Now we have "replace catalog" in the middle of a stockpile command name, instead we should just output "rc" or "cat" or something similar .This may also affect the DLO since it follows the queue metadata encoding. 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-2997) OOM on upgrade to 4.2.0
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2997 OOM on upgrade to 4.2.0 Change By: Susan McNerney Labels: davis-triage 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-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6557 Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Change By: Ethan Brown Flagged: Impediment 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-1477) SELinux fact not being correctly detected
Title: Message Title Bill Niestempski updated an issue Facter / FACT-1477 SELinux fact not being correctly detected Change By: Bill Niestempski CS Priority: Needs Priority Reviewed 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-2997) OOM on upgrade to 4.2.0
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2997 OOM on upgrade to 4.2.0 Change By: Wyatt Alt Affects Version/s: PDB 4.2.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-2997) OOM on upgrade to 4.2.0
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2997 OOM on upgrade to 4.2.0 Issue Type: Bug Assignee: Unassigned Created: 2016/08/23 8:59 AM Priority: Normal Reporter: Wyatt Alt User frozenfoxx in IRC reported an OOM upgrading from 4.0.0 to 4.2.1. We have traced it down to the migration of facts/resources data through the application for conversion to jsonb, here: https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/scf/migrate.clj#L1108 Initially it seemed like the batch size of 500 might be the problem, but it looks like the JDBC functions we're using aren't actually behaving as expected, i.e this retains the head: (jdbc/with-transacted-connection my-db (sql/query my-db "select encode(resource::bytea, 'hex') as resource, parameters from resource_params_cache"
Jira (PUP-6338) Allow arrow syntax on the contain keyword by making include and contain return resource references
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6338 Allow arrow syntax on the contain keyword by making include and contain return resource references Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-6512) Change hiera.yaml (v4) to lookup.conf (v5)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6512 Change hiera.yaml (v4) to lookup.conf (v5) Change By: Henrik Lindberg Summary: Change hiera.yaml (v4) to lookup.conf (v5) 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Henrik Lindberg commented on PUP-6496 Re: Add support for using hocon for main hiera config file Closing this in favor of PUP-6512. It is not very meaningful to first ask users to transition to a version 3 of a hiera.yaml to a hiera.conf, only to be superseded by a lookup.conf. Better to just keep things as they are and switch directly to lookup.conf (which will use a format known as version 5). If we add a global lookup layer, it would follow the same pattern as lookup.conf. 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-6645) Remove the hiera_xxx functions
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6645 Remove the hiera_xxx functions Issue Type: Improvement Assignee: Unassigned Created: 2016/08/23 7:44 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Henrik Lindberg In Puppet 5.0.0 it is expected that the data management features of of Puppet has evolved to only use the "lookup" functionality introduced during the 4.x series which replaces the "hiera project" provided functionality while retaining the hierarchical data structures and data integration syntax. In this ticket, the puppet functions hiera, hiera_include, hiera_array and hiera_hash will be removed from the puppet code base. Users should have transitioned to use the lookup function during the 4.x series. Add Comment
Jira (PUP-6539) add removal tickets for puppet 5.0 for hiera_xxx
Title: Message Title John Duarte updated an issue Puppet / PUP-6539 add removal tickets for puppet 5.0 for hiera_xxx Change By: John Duarte QA Status: Reviewed 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-6414) Update forgeapi.puppetlabs.com to forgeapi.puppet.com
Title: Message Title John Duarte updated an issue Puppet / PUP-6414 Update forgeapi.puppetlabs.com to forgeapi.puppet.com Change By: John Duarte QA Risk Assessment Reason: Risk of broken forge access 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-6414) Update forgeapi.puppetlabs.com to forgeapi.puppet.com
Title: Message Title John Duarte updated an issue Puppet / PUP-6414 Update forgeapi.puppetlabs.com to forgeapi.puppet.com Change By: John Duarte QA Risk Assessment: High 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-6414) Update forgeapi.puppetlabs.com to forgeapi.puppet.com
Title: Message Title John Duarte updated an issue Puppet / PUP-6414 Update forgeapi.puppetlabs.com to forgeapi.puppet.com Change By: John Duarte QA Status: Reviewed 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.
