Jira (PUP-4436) With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
Title: Message Title
Josh Cooper commented on PUP-4436
Re: With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
Fixes merged in 8f5fa37 and f476f17
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1207/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-2630
Server-set global variables like $::environment get overwritten by client facts
Change By:
Eric Thompson
REPORTED PROBLEM---As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environment.The same happens with other server-set global variables, like $::servername and $::serverip.As a result, modules can't reliably use these variables for whatever their intended purpose is.If this is the intended behavior, then the docs should clarify this and discourage use of the server-set variables, because a misbehaving node can override them.SOLUTION---Add a function that returns the server facts (e.g. {{server_facts()}} since that makes it possible for module authors to depend on puppet 4.1.0 and get expected values without any opt-in. This is preferred over setting yet another global variable name.* Separate the logic in node (see comment from Andy Parker below with the details) to make it possible to retrieve the server side facts later* Add a function {{server_facts()}} that returns a hash of the server side facts (that were set aside in the node)* If there are no server side facts (puppet apply case), an empty hash is returned* Issue a warning when a fact overwrites a server side fact (but perform the overwrite since not doing so breaks API)* Decide on real resolution of this issue: (Ping [~eric.sorenson] i.e. possibly deprecate setting server facts as variables in top scope? (Add deprecation ticket, add removal ticket for PUP 5.0.0)* For DOCS, should mention that {{server_facts()}} should be used instead of using top scope variables as they cannot be relied upon. h3. an example $server_facts hash{serverversion => 4.0.0, servername => v85ix8blah.delivery.puppetlabs.net, serverip => 10.32.115.182, environment => production}QA---risk: highprobability: mediumseverity: high (hard to debug, somewhat of a security issue, can spoof environment)test layer: acceptance
Add Comment
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-2630
Server-set global variables like $::environment get overwritten by client facts
Change By:
Eric Thompson
REPORTED PROBLEM---As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environment.The same happens with other server-set global variables, like $::servername and $::serverip.As a result, modules can't reliably use these variables for whatever their intended purpose is.If this is the intended behavior, then the docs should clarify this and discourage use of the server-set variables, because a misbehaving node can override them.SOLUTION---Add a function that returns the server facts (e.g. {{server_facts()}} since that makes it possible for module authors to depend on puppet 4.1.0 and get expected values without any opt-in. This is preferred over setting yet another global variable name.* Separate the logic in node (see comment from Andy Parker below with the details) to make it possible to retrieve the server side facts later* Add a function {{server_facts()}} that returns a hash of the server side facts (that were set aside in the node)* If there are no server side facts (puppet apply case), an empty hash is returned* Issue a warning when a fact overwrites a server side fact (but perform the overwrite since not doing so breaks API)* Decide on real resolution of this issue: (Ping [~eric.sorenson] i.e. possibly deprecate setting server facts as variables in top scope? (Add deprecation ticket, add removal ticket for PUP 5.0.0)* For DOCS, should mention that {{server_facts()}} should be used instead of using top scope variables as they cannot be relied upon. an example $server_facts hash{serverversion => 4.0.0, servername => v85ix8blah.delivery.puppetlabs.net, serverip => 10.32.115.182, environment => production} QA---risk: highprobability: mediumseverity: high (hard to debug, somewhat of a security issue, can spoof environment)test layer: acceptance
Add Comment
Jira (PUP-4568) Puppet agent does not resend certificate request to master
Title: Message Title Kylo Ginsberg commented on PUP-4568 Re: Puppet agent does not resend certificate request to master Josh Cooper or Christopher Price: is there an epic around cert handshake behavior that we could add this to? (I vaguely recall one but couldn't find it.) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1482) PR (1378): (maint) allow ordering on non-extracted fields - wkalt
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1482 PR (1378): (maint) allow ordering on non-extracted fields - wkalt Change By: Wyatt Alt Story Points: 1 2 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4601) Puppet gem should require at least 1.9+ ruby version
Title: Message Title Peter Huene updated an issue Puppet / PUP-4601 Puppet gem should require at least 1.9+ ruby version Change By: Peter Huene Labels: Community Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4601) Puppet gem should require at least 1.9+ ruby version
Title: Message Title Peter Huene created an issue Puppet / PUP-4601 Puppet gem should require at least 1.9+ ruby version Issue Type: Improvement Affects Versions: PUP 4.0.0 Assignee: Unassigned Created: 2015/05/12 4:56 PM Fix Versions: PUP 4.2.0 Priority: Normal Reporter: Peter Huene The puppet gem specification should require a ruby that is >= 1.9.3 because 1.8 is no longer supported in Puppet 4. This will prevent the 4.x gem from installing on systems that only have a 1.8 ruby. Add Comment
Jira (PUP-4568) Puppet agent does not resend certificate request to master
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4568 Puppet agent does not resend certificate request to master Change By: Kylo Ginsberg [I am refiling # See redmine 4680 because the fix applied was unrelated to the original request] : http://projects.puppetlabs.com/issues/4680 [Actual]Once the agent sends the certificate request once to the master, it never does it again (even if the master does not have it anymore)[Expected]In the case the master does not have a copy of the certificate request, the agent should send it to the master, instead of assuming it still does. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4594) Smoke test packages
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4594 Smoke test packages Change By: Kylo Ginsberg 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 Gem only smoke testing can therefore be limited to other package formats than deb and rpm.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. * When all platforms picked have been smoke tested, move this ticket to done.IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to smoke test on, and the smoke test procedure.Example:Smoke test platforms: * pick some platforms such as * Windows 2003/2008/2012 (msi) * Solaris 10/11 (tarball or gem?) * OSX (dmg) * (Note if you are smoke testing Puppet and pick an rpm or deb based platform, concentrate on testing a gem or tarball, since acceptance should have adequately smoke tested those packages.)* RHEL/CentOS 5/6/7* Fedora 19/20* Debian 6/7* Ubuntu 10.04/12.04/14.04Smoke test procedure: * Start/stop/restart a master (if the platform supports that) * Start/stop/restart an agent * Help/man * Write and run some manifestsDependencies: * Tag and create packages * For Windows MSIs - Push tag Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-994) Smoke test packages
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-994 Smoke test packages Change By: Kylo Ginsberg 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 Gem only smoke testing can therefore be limited to other package formats than deb and rpm.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. * When all platforms picked have been smoke tested, move this ticket to done.IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to smoke test on, and the smoke test procedure.Example:Smoke test platforms: * pick some platforms such as * Windows 2003/2008/2012 (msi) * Solaris 10/11 (tarball or gem?) * OSX (dmg) * (Note if you are smoke testing Puppet and pick an rpm or deb based platform, concentrate on testing a gem or tarball, since acceptance should have adequately smoke tested those packages.)* RHEL/CentOS 5/6/7* Fedora 19/20* Debian 6/7* Ubuntu 10.04/12.04/14.04Smoke test procedure: * Start/stop/restart a master (if the platform supports that) * Start/stop/restart an agent * Help/man * Write and run some manifestsDependencies: * Tag and create packages * For Windows MSIs - Push tag Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-985) facter 2.4.4 2015-05-18 Release
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-985 facter 2.4.4 2015-05-18 Release Change By: Kylo Ginsberg Sprint: Client 2015-05-27 Scrum Team: Client Platform Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-995) Go/no-go meeting (before 4pm)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-995 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg 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 Add Comment
Jira (FACT-998) Docs pushed
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-998 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg 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.3.15#6346-sha1:dbc023d)
Jira (FACT-997) Packages pushed
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-997 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg 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. Dependencies:
Jira (FACT-1000) Close all resolved tickets in Jira
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1000 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:51 PM Priority: Normal Reporter: Kylo Ginsberg Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20FACT%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%222.4.4%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (FACT-994) Smoke test packages
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-994 Smoke test packages Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg 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. 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. When all platforms picked have been smoke tested, move this ticket to done. IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to
Jira (FACT-996) Push tag
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-996 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg 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 This message was sent by Atlassian JIRA
Jira (FACT-999) Send out announcements
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-999 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/05/12 4:51 PM Priority: Normal Reporter: Kylo Ginsberg 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" Dependencies:
Jira (FACT-993) Tag the release and create packages
Title: Message Title
Kylo Ginsberg created an issue
Facter / FACT-993
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/05/12 4:50 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
Tag and create packages
Developer provides the SHA - Kylo Ginsberg - 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 (FACT-990) Merge master into stable
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-990 Merge master into stable Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg 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 stable
Jira (FACT-986) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-986 Is the code ready for release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:49 PM Priority: Normal Reporter: Kylo Ginsberg 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%20FACT%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.4.4%22
Jira (FACT-985) facter 2.4.4 2015-05-18 Release
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-985 facter 2.4.4 2015-05-18 Release Issue Type: Task Assignee: Release Engineering Created: 2015/05/12 4:49 PM Priority: Normal Reporter: Kylo Ginsberg facter 2.4.4 2015-05-18 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 (FACT-991) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-991 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg 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.Y', Save as "Introduced in X.Y.Y", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (FACT-992) Prepare long form release notes and short form release story
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-992 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment
Jira (FACT-989) Update version number in source
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-989 Update version number in source Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg Bump VERSION in lib/FACT/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? Is there a commit for every JIRA ticket targeted at the release?
Jira (FACT-987) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-987 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:49 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets referenced in the commit log have a bug targeted at the release git log .. look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release). There is also the release-inquisition, which also helps a lot with this task.
Jira (FACT-988) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-988 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:50 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets targeted at the release have a corresponding commit git log .. This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release) There is also the release-inquisition, which also helps a lot with this task. Add Comment
Jira (PUP-4599) Send out announcements
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4599 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg 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" Dependencies:
Jira (PUP-4600) Close all resolved tickets in Jira
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4600 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%224.1.0%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PUP-4593) Tag the release and create packages
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-4593
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/05/12 4:46 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
Tag and create packages
Developer provides the SHA - Kylo Ginsberg - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PUP-4594) Smoke test packages
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4594 Smoke test packages Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg 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. 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. When all platforms picked have been smoke tested, move this ticket to done. IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to
Jira (PUP-4588) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4588 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:45 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets targeted at the release have a corresponding commit git log .. This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release) There is also the release-inquisition, which also helps a lot with this task. Add Comment
Jira (PUP-4591) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4591 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg 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.Y', Save as "Introduced in X.Y.Y", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (PUP-4592) Prepare long form release notes and short form release story
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4592 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment
Jira (PUP-4585) puppet 4.1.0 2015-05-18 Release
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4585 puppet 4.1.0 2015-05-18 Release Issue Type: Task Assignee: Release Engineering Created: 2015/05/12 4:45 PM Priority: Normal Reporter: Kylo Ginsberg puppet 4.1.0 2015-05-18 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PUP-4597) Packages pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4597 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg 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. Dependencies:
Jira (PUP-4595) Go/no-go meeting (before 4pm)
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4595 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg 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 Add Comment
Jira (PUP-4586) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4586 Is the code ready for release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:45 PM Priority: Normal Reporter: Kylo Ginsberg If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%224.1.0%22
Jira (PUP-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Steve Barlow Sprint: Client Language 2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-958) Acceptance test covering facts based on platform
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-958 Acceptance test covering facts based on platform Change By: Michael Smith Status: Ready for CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4590) Merge master into stable
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4590 Merge master into stable Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:45 PM Priority: Normal Reporter: Kylo Ginsberg 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 stable
Jira (PUP-4596) Push tag
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4596 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg 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 This message was sent by Atlassian JIRA
Jira (PUP-4598) Docs pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4598 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/05/12 4:46 PM Priority: Normal Reporter: Kylo Ginsberg 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.3.15#6346-sha1:dbc023d)
Jira (PUP-4587) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4587 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:45 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets referenced in the commit log have a bug targeted at the release git log .. look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release). There is also the release-inquisition, which also helps a lot with this task.
Jira (PUP-4585) puppet 4.1.0 2015-05-18 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4585 puppet 4.1.0 2015-05-18 Release Change By: Kylo Ginsberg Sprint: Client 2015-05-27 Scrum Team: Client Platform Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4578) Smoke test packages
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4578 Smoke test packages Change By: Kylo Ginsberg Procedure may vary by project and point in the release cycle. Ask around.In general this should happen on Per a variety of platforms recent Platform SoS discussion , 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.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. * When all platforms picked have been smoke tested, move this ticket only needs to done.IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to be smoke test on, and the smoke test procedure.Example:Smoke test platforms: * pick some platforms such as * Windows 2003/2008/2012 (msi) * Solaris 10/11 (tarball or gem?) * OSX (dmg) * (Note if you are smoke testing Puppet and pick an rpm or deb based platform, concentrate on testing a gem or tarball, of gems since we run acceptance should have adequately smoke tested those against packages for everything else . )* RHEL/CentOS 5/6/7* Fedora 19/20* Debian 6/7* Ubuntu 10.04/12.04/14.04Smoke test procedure: * Start/stop/restart a master (if the platform supports that) * Start/stop/restart an agent * Help/man * Write and run some manifestsDependencies: * Tag and create packages * For Windows MSIs - Push tag Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4589) Update version number in source
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4589 Update version number in source Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/05/12 4:45 PM Priority: Normal Reporter: Kylo Ginsberg Bump VERSION in lib/PUP/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-4572) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4572 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:42 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets targeted at the release have a corresponding commit git log .. This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release) There is also the release-inquisition, which also helps a lot with this task. Add Comment
Jira (PUP-4578) Smoke test packages
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4578 Smoke test packages Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg 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. 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. When all platforms picked have been smoke tested, move this ticket to done. IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms
Jira (PUP-4574) Merge master into stable
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4574 Merge master into stable Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:42 PM Priority: Normal Reporter: Kylo Ginsberg 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 stable
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker ajroetker commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4576) Prepare long form release notes and short form release story
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4576 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment
Jira (PUP-4581) Packages pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4581 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg 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. Dependencies:
Jira (PUP-4577) Tag the release and create packages
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-4577
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/05/12 4:43 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
Tag and create packages
Developer provides the SHA - Henrik Lindberg - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PUP-4575) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4575 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:42 PM Priority: Normal Reporter: Kylo Ginsberg 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.Y', Save as "Introduced in X.Y.Y", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (PUP-4569) puppet 3.8.1 2015-05-21 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4569 puppet 3.8.1 2015-05-21 Release Change By: Kylo Ginsberg Sprint: Language 2015-05-27 Scrum Team: Language Story Points: 3 Note: date set for a couple days after 4.1.0. puppet 3.8.1 2015-05-21 ReleaseWhen working through this ticket, add it to the board and then keep it in the Ready for Engineering column.Move the subtasks to In Progress when you are working on them and Resolved when you have completed them.In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. * The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. * Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. * When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready. Add Comment This message was
Jira (PUP-4579) Go/no-go meeting (before 4pm)
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4579 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg 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 Add Comment
Jira (PUP-4571) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4571 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:42 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets referenced in the commit log have a bug targeted at the release git log .. look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release). There is also the release-inquisition, which also helps a lot with this task.
Jira (PUP-4584) Close all resolved tickets in Jira
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4584 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.8.1%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PUP-4583) Send out announcements
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4583 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg 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" Dependencies:
Jira (PUP-4582) Docs pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4582 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg 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.3.15#6346-sha1:dbc023d)
Jira (PUP-4573) Update version number in source
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4573 Update version number in source Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:42 PM Priority: Normal Reporter: Kylo Ginsberg Bump VERSION in lib/PUP/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-4580) Push tag
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4580 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/05/12 4:43 PM Priority: Normal Reporter: Kylo Ginsberg 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 This message was sent by Atlassian JIRA
Jira (PUP-4569) puppet 3.8.1 2015-05-21 Release
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4569 puppet 3.8.1 2015-05-21 Release Issue Type: Task Assignee: Release Engineering Created: 2015/05/12 4:42 PM Priority: Normal Reporter: Kylo Ginsberg puppet 3.8.1 2015-05-21 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PUP-4570) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4570 Is the code ready for release? Issue Type: Sub-task Assignee: Henrik Lindberg Created: 2015/05/12 4:42 PM Priority: Normal Reporter: Kylo Ginsberg If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.8.1%22
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1206/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4559) Extend spec testing to Puppet 3.7 and 4.0
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4559 Extend spec testing to Puppet 3.7 and 4.0 Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4567) Fix acceptance infrastructure
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-4567 Fix acceptance infrastructure Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4567) Fix acceptance infrastructure
Title: Message Title Michael Smith commented on PUP-4567 Re: Fix acceptance infrastructure Acceptance pipeline relies on packages, so this is blocked on releasing a Puppet 3.8 package. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4568) Puppet agent does not resend certificate request to master
Title: Message Title Nelson Araujo created an issue Puppet / PUP-4568 Puppet agent does not resend certificate request to master Issue Type: Bug Affects Versions: PUP 3.7.5 Assignee: Kylo Ginsberg Components: Client Created: 2015/05/12 4:26 PM Labels: puppet-agent Priority: Normal Reporter: Nelson Araujo I am refiling #4680 because the fix applied was unrelated to the original request [Actual] Once the agent sends the certificate request once to the master, it never does it again (even if the master does not have it anymore) [Expected] In the case the master does not have a copy of the certificate request, the agent should send it to the master, instead of assuming it still does.
Jira (PUP-1295) Yum provider "purge" target runs irrespective of package installation status
Title: Message Title Peter Huene updated an issue Puppet / PUP-1295 Yum provider "purge" target runs irrespective of package installation status Change By: Peter Huene Labels: customer redmine Community Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1295) Yum provider "purge" target runs irrespective of package installation status
Title: Message Title Peter Huene updated an issue Puppet / PUP-1295 Yum provider "purge" target runs irrespective of package installation status Change By: Peter Huene Sprint: Client 2015-05-27 Scrum Team: Client Platform Story Points: 1 Fix Version/s: PUP 4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Michael Smith commented on PUP-4477 Re: Create a base agent upgrade module for rpm-based distro Acceptance CI failed, filed PUP-4567. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-984) Fix facts/debian on Debian 8
Title: Message Title Michael Smith created an issue Facter / FACT-984 Fix facts/debian on Debian 8 Issue Type: Improvement Assignee: Unassigned Created: 2015/05/12 3:47 PM Priority: Normal Reporter: Michael Smith Update facts/debian acceptance test to support Debian 8. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-983) Fix facts/ubuntu on Ubuntu 15.04
Title: Message Title Michael Smith created an issue Facter / FACT-983 Fix facts/ubuntu on Ubuntu 15.04 Issue Type: Improvement Assignee: Unassigned Created: 2015/05/12 3:46 PM Priority: Normal Reporter: Michael Smith Update the facts/ubuntu acceptance test for Ubuntu 15.04. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4567) Fix acceptance infrastructure
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4567 Fix acceptance infrastructure Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Oliver Bertuch commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Is there any particular reason why this fix didn't make it into 3.7.x and/or 3.8.x? This is actually breaking my recent RedHat 7 installs while trying to install things and no Puppet 4 around. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1205/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4567) Fix acceptance infrastructure
Title: Message Title Michael Smith created an issue Puppet / PUP-4567 Fix acceptance infrastructure Issue Type: Sub-task Assignee: Unassigned Created: 2015/05/12 2:40 PM Priority: Normal Reporter: Michael Smith A CI pipeline is setup at https://jenkins-modules.delivery.puppetlabs.net/view/4.%20cross%20platform/view/agent_upgrade/view/master/, but the basic acceptance framework doesn't run successfully. Fix it. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4565) Reference/Access resource's variables along with Resources Collectors (<| |>)
Title: Message Title Henrik Lindberg assigned an issue to Roberto Gonzalez Azevedo Puppet / PUP-4565 Reference/Access resource's variables along with Resources Collectors (<| |>) Change By: Henrik Lindberg Assignee: Roberto Gonzalez Azevedo Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4565) Reference/Access resource's variables along with Resources Collectors (<| |>)
Title: Message Title
Henrik Lindberg commented on PUP-4565
Re: Reference/Access resource's variables along with Resources Collectors (<| |>)
Is this a regression from 3.x. without future parser? i.e. can the $title etc. be used if future parser is not used?
Secondly, this example:
Service <| |> { 'restart' => '/usr/bin/runcon -t initrc_t -u system_u -r system_r /sbin/service $title restart', }
would not work because a single quoted string is used and it does not support interpolation of variables. You would have to write it like this
Service <| |> { 'restart' => "/usr/bin/runcon -t initrc_t -u system_u -r system_r /sbin/service $title restart",
}
Was that just a typo in this ticket?
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4565) Reference/Access resource's variables along with Resources Collectors (<| |>)
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4565
Reference/Access resource's variables along with Resources Collectors (<| |>)
Change By:
Henrik Lindberg
Hello,I've been struggling with this issue a while and now I decided to ask you some help. I need to redefine the 'start/restart' behavior of all classes during the execution phase (post compile phase). (I want to 'start/restart' every service through 'runcon' (selinux) command)In the beginning I tried this: {code:puppet} Service <| |> { 'restart' => '/usr/bin/runcon -t initrc_t -u system_u -r system_r /sbin/service $title restart', } {code} It didn't work out. The variable $title, or $name, whatever, is always empty (all the time).Then, I made this using inline_template (it's awful, but it works). Please, check the attached file.It would be great if Resource Collectors provide those variables ($title, $name, anyway)...(Personally, I don't like the idea of use internals variables like 'scope.compiler.catalog.vertices'...)Is there any other solution?System used (parser=future):[root@centos6 ~]# rpm -q puppet ; uname -apuppet-3.7.5-1.el6.noarchLinux centos6 2.6.32-504.16.2.el6.x86_64 #1 SMP Wed Apr 22 06:48:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@goog
Jira (PUP-4193) Add pattern matching to the Puppet DSL
Title: Message Title Kylo Ginsberg commented on PUP-4193 Re: Add pattern matching to the Puppet DSL Eric Sorenson ping. I'd appreciate your review on this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4342) add acceptance to call all parser functions
Title: Message Title Kurt Wall commented on PUP-4342 Re: add acceptance to call all parser functions Merged to master at 6a3e2ed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4466) add acceptance: ensure functions can be written/execute in puppet language
Title: Message Title Kurt Wall commented on PUP-4466 Re: add acceptance: ensure functions can be written/execute in puppet language This should not gate PUP-2080l Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker ajroetker commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1204/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1487) Add producer_timestamp to store-report
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1487 Add producer_timestamp to store-report Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker ajroetker commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1487) Add producer_timestamp to store-report
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1487 Add producer_timestamp to store-report Change By: Russell Mull Sprint: PuppetDB 2015- 06 05 - 03 20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3967) Run puppet acceptance with cfacter
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3967 Run puppet acceptance with cfacter Change By: Kurt Wall QA Risk Assessment Reason: N/A for test-related tickets Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4113) Migrate and Preview 3.8 Language to 4.0
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4113 Migrate and Preview 3.8 Language to 4.0 Change By: Kurt Wall QA Risk Assessment Reason: N/A for an epic Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4113) Migrate and Preview 3.8 Language to 4.0
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4113 Migrate and Preview 3.8 Language to 4.0 Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3967) Run puppet acceptance with cfacter
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3967 Run puppet acceptance with cfacter Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1428) Failure to contact updates.puppetlabs.com is logged at INFO
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1428 Failure to contact updates.puppetlabs.com is logged at INFO Change By: Kurt Wall QA Risk Probability: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1428) Failure to contact updates.puppetlabs.com is logged at INFO
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1428 Failure to contact updates.puppetlabs.com is logged at INFO Change By: Kurt Wall QA Risk Assessment Reason: Just a log level change Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1417) Announce HyperSQL Deprecation in 3.0.0
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1417 Announce HyperSQL Deprecation in 3.0.0 Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1428) Failure to contact updates.puppetlabs.com is logged at INFO
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1428 Failure to contact updates.puppetlabs.com is logged at INFO Change By: Kurt Wall QA Risk Severity: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1428) Failure to contact updates.puppetlabs.com is logged at INFO
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1428 Failure to contact updates.puppetlabs.com is logged at INFO Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
