Jira (PUP-5759) Windows: Puppet agent doesn't create directory when parent is a mounted volume
Title: Message Title Dirk Heinrichs commented on PUP-5759 Re: Windows: Puppet agent doesn't create directory when parent is a mounted volume That's been so long ago, I can't even remember why I was trying to do this. Windows version was Server 2008 R2 or 2012 R2, Puppet agent version could have been 1.5.x at that time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Acceptance Criteria: - Plan documented and proposed to discuss@agent-and-platform- If path forward is is clear, create tickets for any work needed to accomplish the end goal Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols created an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Issue Type: Task Assignee: Unassigned Created: 2016/10/25 9:12 PM Priority: Normal Reporter: Geoff Nichols Facter 2 is EOL at the end of 2016. We need to figure out what we’re going to do with rubygem facter, especially since we need a solution for running Facter from source in CI. In scope for Agent and Platform Team: Explore viability of Facter 3 as a rubygem Broadcast findings and gather feedback Add Comment
Jira (FACT-1523) (SPIKE) Explore viability of a Facter 3 rubygem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1523 (SPIKE) Explore viability of a Facter 3 rubygem Change By: Geoff Nichols Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3129) Docs pushed (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3129 Docs pushed (PDB 4.2.5) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/10/25 5:49 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3131) Update dujour to notify users to use 4.2.5 (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3131 Update dujour to notify users to use 4.2.5 (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:49 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) Update dujour to notify users to use 4.2.5. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3132) Close all resolved tickets in Jira (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3132 Close all resolved tickets in Jira (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:49 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) 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.5%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-3130) Send out announcements (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3130 Send out announcements (PDB 4.2.5) Issue Type: Sub-task Assignee: Beth Cornils Created: 2016/10/25 5:49 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependen
Jira (PDB-3128) Packages pushed (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3128 Packages pushed (PDB 4.2.5) Issue Type: Sub-task Assignee: Melissa Stone Created: 2016/10/25 5:49 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) 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-3122) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3122 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z'
Jira (PDB-3125) Smoke test packages (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3125 Smoke test packages (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) 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-3121) Merge master into stable (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3121 Merge master into stable (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout
Jira (PDB-3127) Push tag (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3127 Push tag (PDB 4.2.5) Issue Type: Sub-task Assignee: Melissa Stone Created: 2016/10/25 5:49 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) 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-3119) Reconcile git commits and JIRA tickets (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3119 Reconcile git commits and JIRA tickets (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier r
Jira (PDB-3120) Update version number in source (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3120 Update version number in source (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) 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-3117) PuppetDB 4.2.5 2016-10-26 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3117 PuppetDB 4.2.5 2016-10-26 Release Issue Type: Task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt PuppetDB 4.2.5 2016-10-26 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-3118) Is the code ready for release? (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3118 Is the code ready for release? (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) 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.5%22
Jira (PDB-3124) Tag the release and create packages (PDB 4.2.5)
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-3124
Tag the release and create packages (PDB 4.2.5)
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2016/10/25 5:48 PM
Priority:
Normal
Reporter:
Wyatt Alt
(Initial planned release date: 2016-10-26)
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-3123) Prepare long form release notes and short form release story (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3123 Prepare long form release notes and short form release story (PDB 4.2.5) Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA
Jira (PDB-3126) Go/no-go meeting (before noon PST) (PDB 4.2.5)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3126 Go/no-go meeting (before noon PST) (PDB 4.2.5) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2016/10/25 5:48 PM Priority: Normal Reporter: Wyatt Alt (Initial planned release date: 2016-10-26) This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Wyatt Alt Nicholas Fagerlund Beth Cornils Ryan Gard Melissa Stone
Jira (PUP-6761) [SPIKE] Find a workflow for POT file generation
Title: Message Title Larissa Lane commented on PUP-6761 Re: [SPIKE] Find a workflow for POT file generation Answered in the ticket description Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6761) [SPIKE] Find a workflow for POT file generation
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6761 [SPIKE] Find a workflow for POT file generation Change By: Larissa Lane POT files are generated automatically as a result of gettext_setup parsing of strings in code. In order to automate this process, we need to find out what needs to happen (and when).This may be part of one or more CI jobs. * Find answer to question "What is the directory structure for translation (PO and POT) files?" A: In the repo, you should have a 'locales' folder. The POT and PO files should be in the locales folder * Design a workflow for POT file generation* For the POC, this should be a close as possible to the workflow used for other languages.PE-15457 may provide additional context. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6762) [SPIKE] How and when do we get PO files from Transifex?
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6762 [SPIKE] How and when do we get PO files from Transifex? Change By: Larissa Lane Transifex is third-party translation-as-a-service provider that provides translation services in the form of PO files. * Workflow includes committing PO files from Transifex to a Github repository.* Design a workflow for getting files from Transifex to us.h5. Questions:* Does the Transifex integration use a push or pull model to obtain code/strings to be translated? A: Transifex watches the Github repo for changes to a PO file using a githook. When changes are made, it pulls the latest version of the PO file into Transifex. * Does the Transifex integration use a push or pull model to provide PO files? A: Transifex waits for a PO file in Transifex to reach 100% translated and reviewed. When the status of the PO file changes to 100% reviewed, Transifex pushes the latest version of the file to the source Github repo. * If push model, what are the security implications and design to mitigate? A: The configuration of the Transifex server is described in [OPS-9632|https://tickets.puppetlabs.com/browse/OPS-9632]. What specific security questions do you have? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PDB-3116) Cherry-pick for Everett
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3116 Cherry-pick for Everett Issue Type: Bug Assignee: Unassigned Created: 2016/10/25 3:09 PM Priority: Normal Reporter: gepetto-bot These are all of the non-stockpile related commits from master that are going out in 4.2.4 release that we will cut off of master. This PR is related to https://github.com/puppetlabs/puppetdb/pull/2108 in core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3115) Cherry-pick for Everett
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3115 Cherry-pick for Everett Issue Type: Bug Assignee: Unassigned Created: 2016/10/25 3:08 PM Priority: Normal Reporter: gepetto-bot These are all of the non-stockpile related commits from master that are going out in 4.2.4 release that we will cut off of master Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Alex Dreyer Release Notes Summary: This allows application components to consume capabilities from other environments. If multiple capabilities are found the capability from the current environment will be preferred. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Kenn Hussey commented on PUP-6789 Re: Prefer but don't require capabilities matching the node environment Alex Dreyer I assume this has made it through CI at this point. Could you please provide some release notes? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Kenn Hussey assigned an issue to qa Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Change By: Kenn Hussey Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-130) Add note to README about linebreaks and indentation for long tag docs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-130 Add note to README about linebreaks and indentation for long tag docs Change By: William Hopper QA Risk Assessment: Low Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-130) Add note to README about linebreaks and indentation for long tag docs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-130 Add note to README about linebreaks and indentation for long tag docs Change By: William Hopper Sprint: PDS 2016-11-02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-130) Add note to README about linebreaks and indentation for long tag docs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-130 Add note to README about linebreaks and indentation for long tag docs Change By: William Hopper Summary: Add note to RADME README about linebreaks and indentation for long tag docs Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6835) Puppet does not check for revoked cert against puppetdb connection
Title: Message Title Michael Smith commented on PUP-6835 Re: Puppet does not check for revoked cert against puppetdb connection The puppet master needs to restart to reload an updated CRL. Could that be what's happening? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3114) Track down and fix timeout in concurrent-catalog-resource-updates
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3114 Track down and fix timeout in concurrent-catalog-resource-updates Issue Type: Bug Assignee: Rob Browning Created: 2016/10/25 11:51 AM Labels: maintenance Priority: Normal Reporter: Rob Browning As seen here: https://travis-ci.org/puppetlabs/puppetdb/jobs/170187392#L882 lein test :only puppetlabs.puppetdb.command-test/concurrent-catalog-resource-updates ERROR in (concurrent-catalog-resource-updates) (command_test.clj:126) Uncaught exception, not in assertion. expected: nil The [database] classname setting has been retired and will be ignored. The [database] subprotocol setting has been retired and will be ignored. actual: java.lang.Exception: Channel take timed out after '30' ms at puppetlabs.puppetdb.command_test$take_with_timeout_BANG_BANG.invokeStatic (command_test.clj:126) puppetlabs.puppetdb.command_test$take_with_timeout_BANG_BANG.invoke (command_test.clj:120) puppetlabs.puppetdb.command_test$fn_52635$fn52636$fn_52643.invoke (command_test.clj:1299) clojure.core$with_redefs_fn.invokeStatic (core.clj:7216) clojure.core$with_redefs_fn.invoke (core.clj:7200) puppetlabs.puppetdb.command_test$fn_52635$fn_52636.invoke (command_test.clj:1266) puppetlabs.puppetdb.testutils.db$call_with_test_db$fn_85807$fn_85810.invoke (db.clj:213) clojure.core$with_redefs_fn.invokeStatic (core.clj:7216) clojure.core$with_redefs_fn.invoke (core.clj:7200) puppetlabs.puppetdb.testutils.db$call_with_test_db$fn__85807.invoke (db.clj:212) puppetlabs.puppetdb.testutils.db$call_with_db_info_on_failure_or_drop.invokeStatic
Jira (PDOC-130) Add note to RADME about linebreaks and indentation for long tag docs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-130 Add note to RADME about linebreaks and indentation for long tag docs Change By: William Hopper Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-130) Add note to RADME about linebreaks and indentation for long tag docs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-130 Add note to RADME about linebreaks and indentation for long tag docs Change By: William Hopper Summary: Add note to RADME about linebreaks cause problems and indentation for long tag docs Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-130) Add note to RADME about linebreaks and indentation for long tag docs
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-130 Add note to RADME about linebreaks and indentation for long tag docs Change By: William Hopper Story Points: 1 Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-101) Puppet strings examples
Title: Message Title William Hopper commented on PDOC-101 Re: Puppet strings examples I think this should also include a bunch of example code for best practices for how to document all of the things strings supports. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6758) Fix pkgng provider
Title: Message Title Zach L commented on PUP-6758 Re: Fix pkgng provider May I request a status here please? The PR is in and I believe its ready for commit. The test is failing, but Branan has commented that its erroneous due to the commit message, which has been corrected. The test for the code change itself is functional. If there is anything else I can help with on this change, please let me know. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2631) PDB is incapable of efficiently storing large dynamic structured facter facts
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2631 PDB is incapable of efficiently storing large dynamic structured facter facts Change By: Karen Van der Veer Sprint: SE 2016-11-16 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2631) PDB is incapable of efficiently storing large dynamic structured facter facts
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2631 PDB is incapable of efficiently storing large dynamic structured facter facts Change By: Karen Van der Veer Sprint: SE 2016-11-16 Next Up Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6842) Puppet 4.7.1 reports at 4.7.0 on Ubuntu 14.04
Title: Message Title Russell Anderson created an issue Puppet / PUP-6842 Puppet 4.7.1 reports at 4.7.0 on Ubuntu 14.04 Issue Type: Bug Assignee: Unassigned Created: 2016/10/25 10:39 AM Priority: Normal Reporter: Russell Anderson Inside a new ubuntu vagrant box, puppet (via puppet-agent=1.7.1) reports as 4.7.0. $ vagrant destroy -f ==> generic: Forcing shutdown of VM... ==> generic: Destroying VM and associated drives...
Jira (PDB-2908) Resolve conflict between i18n and structured-logging
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2908 Resolve conflict between i18n and structured-logging Change By: Rob Browning Sprint: SE 2016-11-02 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-128) Update README to explain: What's the deal with @example tags?
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-128 Update README to explain: What's the deal with @example tags? Change By: William Hopper Fix Version/s: PDOC 1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title Brian Cain commented on FACT-1441 Re: Add "virtualization" fact that identifies AWS, Azure, etc Sweet! That works for me. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc
Title: Message Title Kenaz Kwa commented on FACT-1441 Re: Add "virtualization" fact that identifies AWS, Azure, etc Brian Cain The DHCP 245 option is the only one that Microsoft has officially sanctioned as the way to determine whether a VM is running in Azure: https://gallery.technet.microsoft.com/scriptcenter/Detect-Windows-Azure-aed06d51 It's true that they might change the implementation – but that's what they've documented so far. The FACT-1383 ticket refers to an instance metadata feature with is currently in private preview on the Azure team (I have one of my VMs enabled to use it). It's not documented anywhere and we shouldn't trust it until it's gone officially GA. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1383) Azure Instance Metadata
Title: Message Title Kenaz Kwa commented on FACT-1383 Re: Azure Instance Metadata This feature is not yet at parity with AWS. It only provides maintenance information 5-15 minutes before maintenance is about to happen. The instance information is still very basic and is currently in the process of being updated by the Azure team to reach close to feature parity with EC2. However, that feature is not GA. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-130) linebreaks cause problems
Title: Message Title William Hopper commented on PDOC-130 Re: linebreaks cause problems William Yardley that's actually a YARD thing - the same goes for examples. We don't have control over that, but we can and should make note of that in the README. As for official puppet modules using strings, part of the reason we released 0.99.0 was so that our internal docs team could start using it on our modules. So, you should start to see that happening soon. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-131) generate README from puppet-strings
Title: Message Title William Hopper commented on PDOC-131 Re: generate README from puppet-strings Hey William Yardley! You are correct that README generation isn't currently possible. I had been thinking along similar lines, though. It makes sense and I think we'll make it so at some point (not for the 1.0 release, probably, but hopefully soon!) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2810) Update benchmark tool and samples
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2810 Update benchmark tool and samples Change By: Karen Van der Veer Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3113) (maint) Pursue serialization failure in two places
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3113 (maint) Pursue serialization failure in two places Change By: Karen Van der Veer Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3111) (MAINT) Fix concurrent command proc test issue
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3111 (MAINT) Fix concurrent command proc test issue Change By: Karen Van der Veer Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2908) Resolve conflict between i18n and structured-logging
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2908 Resolve conflict between i18n and structured-logging Change By: Karen Van der Veer Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6012) 'puppet module build ' creates empty module if is a symlink
Title: Message Title Joshua Partlow commented on PUP-6012 Re: 'puppet module build ' creates empty module if is a symlink This seems to be the case even if there is a symlink anywhere along the path. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-123) Support groups of parameters
Title: Message Title Dominic Cleal commented on PDOC-123 Re: Support groups of parameters The syntax I suggested here isn't correct: @!group Database connection @param db_adapter Database adapter name @param db_host Database server hostname @param db_username Username to authenticate with @!endgroup The directive will group classes, defines and other handled objects, but not group tags such as @param on a single object - at least, not with the group directive supplied by YARD as far as I can tell. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
