Jira (PDB-4495) Merge-up, branch, and create pipelines (PuppetDB 6.6.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4495  
 
 
  Merge-up, branch, and create pipelines (PuppetDB 6.6.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Zachary Kent  
 
 
Created: 
 2019/09/05 4:57 PM  
 
 
Due Date: 
2019/09/10 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS). 
 
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master 
 
 
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/ 
 
 
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/ 
 
 
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/ 
 
 
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches 
 Do merge-ups: 
  

Jira (PDB-4499) Update winston (PuppetDB 6.6.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4499  
 
 
  Update winston (PuppetDB 6.6.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Zachary Kent  
 
 
Created: 
 2019/09/05 4:58 PM  
 
 
Due Date: 
2019/09/18 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) Update winston to make these tickets more accurate for next time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
  

Jira (PDB-4496) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.6.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4496  
 
 
  Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.6.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Zachary Kent  
 
 
Created: 
 2019/09/05 4:57 PM  
 
 
Due Date: 
2019/09/10 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) 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. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
  

Jira (PDB-4497) Bump versions, push directly, and tag (PuppetDB 6.6.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4497  
 
 
  Bump versions, push directly, and tag (PuppetDB 6.6.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Zachary Kent  
 
 
Created: 
 2019/09/05 4:57 PM  
 
 
Due Date: 
2019/09/13 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) (if you're making the first release off a new branch you may already have done some of this) 
 
Check that there aren't any essential updates to ezbake needed in this release before pushing a non-snapshot version and tagging. 
 Disable automatic promotions: 
 
Go to the CI pipeline for the version being released and select the Conditional Promotion Trigger job. Click the disable button (the job's circle indicator should be gray now). 
 Set the real version for release: 
 
Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. 
 
 
Go into the '#release-new-new' Slack channel to make yourself a tag 
  ! tag puppetdb  at  with  
 
Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch you're releasing. 
   

Jira (PDB-4498) Check builds, promote to PE (PuppetDB 6.6.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4498  
 
 
  Check builds, promote to PE (PuppetDB 6.6.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Zachary Kent  
 
 
Created: 
 2019/09/05 4:57 PM  
 
 
Due Date: 
2019/09/13 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) 
 
Check that all the builds are green. 
 
 
Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. 
 
 
Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. 
 
 
Remember to revert pe-puppetdb-extensions to reading the version from the file 
  
 

  
 
 
 
 

 
 
 
 

Jira (PUP-10008) Send release announcement (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10008  
 
 
  Send release announcement (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Morgan Rhodes  
 
 
Created: 
 2019/09/05 4:55 PM  
 
 
Due Date: 
2019/09/17 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - 
 
Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. 
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.9.0 is now available". 
  
 

  
 
 
 
 

 
 
 

 

Jira (PUP-10009) Update Confluence and JIRA based on release (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10009  
 
 
  Update Confluence and JIRA based on release (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/09/05 4:55 PM  
 
 
Due Date: 
2019/09/18 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the 

Jira (PUP-10010) Communicate scope and timeline of next release (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10010  
 
 
  Communicate scope and timeline of next release (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/09/05 4:55 PM  
 
 
Due Date: 
2019/09/18 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.  
 

  
   

Jira (PUP-10001) Puppet Platform 6.9.0 Release - 2019-09-17

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10001  
 
 
  Puppet Platform 6.9.0 Release - 2019-09-17
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/09/05 4:54 PM  
 
 
Due Date: 
2019/09/17 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 Puppet Platform 6.9.0 Release - 2019-09-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

Jira (PUP-10002) Prepare JIRA and Confluence for release (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10002  
 
 
  Prepare JIRA and Confluence for release (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/09/05 4:54 PM  
 
 
Due Date: 
2019/09/11 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.9.0 and puppet-agent 6.9.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y 

Jira (PUP-10007) Publish documentation and updates and release notes (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10007  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/09/05 4:54 PM  
 
 
Due Date: 
2019/09/17 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
   

Jira (PUP-10005) Prepare release announcement (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10005  
 
 
  Prepare release announcement (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Bill Tang  
 
 
Created: 
 2019/09/05 4:54 PM  
 
 
Due Date: 
2019/09/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

Jira (PUP-10004) Prepare documentation updates and release notes (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10004  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/09/05 4:54 PM  
 
 
Due Date: 
2019/09/13 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

   

Jira (PUP-10003) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10003  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/09/05 4:54 PM  
 
 
Due Date: 
2019/09/11 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

Jira (PUP-10006) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.9.0)

2019-09-05 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10006  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.9.0)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/09/05 4:54 PM  
 
 
Due Date: 
2019/09/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-09-17) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

Jira (PDB-4494) PuppetDB 5.2.8 and 5.2.9 Docker images missing

2019-09-05 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt commented on  PDB-4494  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetDB 5.2.8 and 5.2.9 Docker images missing   
 

  
 
 
 
 

 
 Hi Ira Snyder docker images before the maintained branch 6.3.z were experimental container releases. We have stopped shipping images for 5.2.z and 6.0.z, so you should take a look at a version 6.3.0+. If you see any versions >=6.3.0 that don't have Docker images or you find issues with those Docker images please let us know, thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323743.1567724072000.87988.1567725540474%40Atlassian.JIRA.


Jira (PDB-4494) PuppetDB 5.2.8 and 5.2.9 Docker images missing

2019-09-05 Thread Ira Snyder (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ira Snyder created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4494  
 
 
  PuppetDB 5.2.8 and 5.2.9 Docker images missing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PDB 5.2.9, PDB 5.2.8  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 PuppetDB  
 
 
Created: 
 2019/09/05 3:54 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Ira Snyder  
 

  
 
 
 
 

 
 The official Docker Hub does not contain puppet/puppetdb images for version 5.2.8 and 5.2.9. See the tags page here: https://hub.docker.com/r/puppet/puppetdb/tags?page=1=5.2 The PuppetDB release notes list these versions as available: https://puppet.com/docs/puppetdb/5.2/release_notes.html#section The PuppetDB Github repository has tags for version 5.2.8 and 5.2.9: https://github.com/puppetlabs/puppetdb/tags   The Puppet CI bot has apparently forgotten about the PuppetDB 5.2.x series.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

Jira (PDB-4493) Query function count() broken for JSON fields

2019-09-05 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4493  
 
 
  Query function count() broken for JSON fields   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 

  
 
 
 
 

 
 For a query like{code}  facts[name, count(value)] {  certname ~ "^pe.*"  group by name}{code}The query engine currently constructs an SQL SELECT that looks like{code}  SELECTfs.key AS name,  count((value#>>'{}')::numeric)count{code}  Which causes the error{code}  javax.servlet.ServletException: org.postgresql.util.PSQLException: ERROR: invalid input syntax for type numeric: "root"{code} But the The  argument to count is invalid and it should be closer to{code}  SELECTfs.key AS name,  count(value)count{code}  *_NOTE_: The error will only happen if the table has data.*   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails 

Jira (PDB-4493) Query function count() broken for JSON fields

2019-09-05 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4493  
 
 
  Query function count() broken for JSON fields   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PDB 6.5.0, PDB 6.3.4, PDB 5.2.9  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/09/05 2:43 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 For a query like  
 
 
 
 
 facts[name, count(value)] {  
 
 
   certname ~ "^pe.*"  
 
 
   group by name  
 
 
 }
  
 
 
 
  The query engine currently constructs an SQL SELECT that looks like  
 
 
 
 
 SELECT

Jira (PUP-9998) Puppet agent --disable is ignored with cron puppet agent (splay).

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9998  
 
 
  Puppet agent --disable is ignored with cron puppet agent (splay).   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323623.1567679385000.87579.1567714380481%40Atlassian.JIRA.


Jira (PDB-4354) Support FIPS certification

2019-09-05 Thread Alexander Johnson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Johnson commented on  PDB-4354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support FIPS certification   
 

  
 
 
 
 

 
 Eric Thompson Are we able to resolve this epic?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306362.155621099.87453.1567711680296%40Atlassian.JIRA.


Jira (PUP-9991) `puppet module uninstall` does not work on FIPS

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9991  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `puppet module uninstall` does not work on FIPS   
 

  
 
 
 
 

 
 Passed CI in 4563f413d6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323058.1567203304000.87334.1567709880144%40Atlassian.JIRA.


Jira (PUP-10000) {brief summary of issue}

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1  
 
 
  {brief summary of issue}   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 [puppen open source|https://  ! puppet .com/sites/default/files/2019 - 07/puppet- os.png ] |thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323670.1567700828000.87035.1567702800210%40Atlassian.JIRA.


Jira (PUP-10000) Puppet 10k

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1  
 
 
  Puppet 10k   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Summary: 
 {brief summary of issue} Puppet 10k  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323670.1567700828000.87036.1567702800228%40Atlassian.JIRA.


Jira (PUP-10000) {brief summary of issue}

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1  
 
 
  {brief summary of issue}   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Attachment: 
 puppet-os.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323670.1567700828000.87034.1567702740247%40Atlassian.JIRA.


Jira (PUP-10000) {brief summary of issue}

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1  
 
 
  {brief summary of issue}   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 *Puppet Version [puppen open source|https : **Puppet Server Version:**OS Name / Version:*Describe your issue in as much detail as possible…Describe steps to reproduce…*Desired Behavior:**Actual Behavior:*Please take a moment and attach any relevant log output and / or manifests. This will help us immensely when troubleshooting the issue.Examples:Run  puppet  agent with --test --trace --debugRelevant sections of {{ .com / var sites / log default / puppetlabs files / puppetserver 2019-07 / puppetserver.log}} or any applicable logs from the same directory.For more detailed information turn up the server logs by upping the log level in the server's logback.xmlRelevant sections of configurations files ( puppet -os . conf, hiera.conf, Server's conf.d, defaults/sysconfig)For memory issues with server heap dumps are also helpful. png]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   
 

Jira (PUP-9998) Puppet agent --disable is ignored with cron puppet agent (splay).

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9998  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet agent --disable is ignored with cron puppet agent (splay).   
 

  
 
 
 
 

 
 This is due to the way the daemon code interacts with puppet's scheduler. It should attempt to acquire the lock in the job that runs the agent (after splay has been applied).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323623.1567679385000.87023.1567702500156%40Atlassian.JIRA.


Jira (PUP-9998) Puppet agent --disable is ignored with cron puppet agent (splay).

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9998  
 
 
  Puppet agent --disable is ignored with cron puppet agent (splay).   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Henrik Lindberg  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323623.1567679385000.87020.1567702440432%40Atlassian.JIRA.


Jira (PUP-10000) {brief summary of issue}

2019-09-05 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1  
 
 
  {brief summary of issue}   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/09/05 9:27 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Change By: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: CentOS Linux release 7.6.1810*I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not.I'm using this fact:{noformat}  require 'puppet'  def to_boolean(value)  %w[absent yes true 1].include?(value.downcase) endFacter endFacter .add('enabled_repos') do  setcode dorepos = []Puppet::Type.type('yumrepo').instances.find_all do |repo|  repo_value = repo.retrieve  repos << repo.name if to_boolean(repo_value[repo.property(:enabled)].to_s.strip)endrepos.sort  endend{noformat}I have a repo defined with enbled=0, ex: myrepoI run this loop to reproduce: {noformat}( date; while :; do facter -p enabled_repos | grep -i myrepo && date && break; sleep 1; done ; yum repolist ) >enabled-repo.tmp 2>&1 &{noformat}After few days I get:{noformat}Mon Sep  2 03:48:12 UTC 2019  "myrepo",Thu Sep  5 16:09:28 UTC 2019Loaded plugins: enabled_repos_upload, fastestmirror, langpacks, package_upload, product-id, search-  : disabled-repos, subscription-manager, tracer_upload, versionlockLoading mirror speeds from cached hostfilerepo id repo name status!Centos_Centos_7_Base Centos_7 Base 10,019!Centos_Centos_7_Extras Centos 7 Extras 435!Centos_Centos_7_Opstools Centos 7 Opstools 896!Centos_Centos_7_Updates Centos 7 Updates 4,067!Centos_Centos_7_kvm-common Centos 7 kvm-common 79!Centos_Centos_7_ovirt Centos 7 ovirt 744!Centos_Centos_sclo Centos sclo 786!Centos_Centos_sclo-rh Centos sclo-rh 8,444repolist: 25,470Uploading Enabled Repositories ReportLoaded plugins: fastestmirror, langpacks, product-id, subscription-manager,  : versionlock{noformat}myrepo is included in the fact enabled_repos but it is not enabled on the system.*Desired Behavior:*myrepo is not included in the fact enabled_repos. Only repos with enable=1 should be included.*Actual Behavior:*myrepo is included in the fact enabled_repos but it is not enabled on the system.I'm using foreman with katello plugin and yum subscriptions.  
 

  
 
 
 
 

 
 
 

Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Change By: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: CentOS Linux release 7.6.1810*I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not.I'm using this fact :    {noformat}require 'puppet'def to_boolean(value)  %w[absent yes true 1].include?(value.downcase)endFacter.add('enabled_repos') do  setcode dorepos = []Puppet::Type.type('yumrepo').instances.find_all do |repo|  repo_value = repo.retrieve  repos << repo.name if to_boolean(repo_value[repo.property(:enabled)].to_s.strip)endrepos.sort  endend  {noformat}I have a repo defined with enbled=0, ex: myrepo   I run this loop to reproduce:   {noformat}( date; while :; do facter -p enabled_repos | grep -i myrepo && date && break; sleep 1; done ; yum repolist ) >enabled-repo.tmp 2>&1 &{noformat}After few days I get:    {noformat}Mon Sep  2 03:48:12 UTC 2019  "myrepo",Thu Sep  5 16:09:28 UTC 2019Loaded plugins: enabled_repos_upload, fastestmirror, langpacks, package_upload, product-id, search-  : disabled-repos, subscription-manager, tracer_upload, versionlockLoading mirror speeds from cached hostfilerepo id repo name status!Centos_Centos_7_Base Centos_7 Base 10,019!Centos_Centos_7_Extras Centos 7 Extras 435!Centos_Centos_7_Opstools Centos 7 Opstools 896!Centos_Centos_7_Updates Centos 7 Updates 4,067!Centos_Centos_7_kvm-common Centos 7 kvm-common 79!Centos_Centos_7_ovirt Centos 7 ovirt 744!Centos_Centos_sclo Centos sclo 786!Centos_Centos_sclo-rh Centos sclo-rh 8,444repolist: 25,470Uploading Enabled Repositories ReportLoaded plugins: fastestmirror, langpacks, product-id, subscription-manager,  : versionlock{noformat}myrepo is included in the fact enabled_repos but it is not enabled on the system.   *Desired Behavior:*myrepo is not included in the fact enabled_repos. Only repos with enable=1 should be included.*Actual Behavior:*myrepo is included in the fact enabled_repos but it is not enabled on the system.I'm using foreman with katello plugin and yum subscriptions.    
 

  
 
 
 
 

 
 

Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Change By: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 *Puppet Version: 4.10.12* *Puppet Server Version: 2.8.1* *OS Name/Version: CentOS Linux release 7.6.1810*I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not. I'm using this fact {noformat}  require 'puppet'def to_boolean(value)  %w[absent yes true 1].include?(value.downcase)endFacter.add('enabled_repos') do  setcode dorepos = []Puppet::Type.type('yumrepo').instances.find_all do |repo|  repo_value = repo.retrieve  repos << repo.name if to_boolean(repo_value[repo.property(:enabled)].to_s.strip)endrepos.sort  endend{noformat}I have a repo defined with enbled=0, ex: myrepo I run this loop to reproduce: {noformat}  ( date; while :; do facter -p enabled_repos | grep -i myrepo && date && break; sleep 1; done ; yum repolist ) >enabled-repo.tmp 2>&1 &{noformat}After few days I get:  {noformat}  Mon Sep  2 03:48:12 UTC 2019  "myrepo",Thu Sep  5 16:09:28 UTC 2019Loaded plugins: enabled_repos_upload, fastestmirror, langpacks, package_upload, product-id, search-  : disabled-repos, subscription-manager, tracer_upload, versionlockLoading mirror speeds from cached hostfilerepo id repo name status!Centos_Centos_7_Base Centos_7 Base 10,019!Centos_Centos_7_Extras Centos 7 Extras 435!Centos_Centos_7_Opstools Centos 7 Opstools 896!Centos_Centos_7_Updates Centos 7 Updates 4,067!Centos_Centos_7_kvm-common Centos 7 kvm-common 79!Centos_Centos_7_ovirt Centos 7 ovirt 744!Centos_Centos_sclo Centos sclo 786!Centos_Centos_sclo-rh Centos sclo-rh 8,444repolist: 25,470Uploading Enabled Repositories ReportLoaded plugins: fastestmirror, langpacks, product-id, subscription-manager,  : versionlock{noformat}myrepo is included in the fact enabled_repos but it is not enabled on the system. *Desired Behavior:*myrepo is not included in the fact enabled_repos. Only repos with enable=1 should be included.*Actual Behavior:*myrepo is included in the fact enabled_repos but it is not enabled on the system. I'm using foreman with katello plugin and yum subscriptions.    
 

  
 
 
 
 

 
 
   

Jira (PUP-9999) Puppet::Type.type('yumrepo') wrongly reports enabled repo

2019-09-05 Thread Anthony Chevalet (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anthony Chevalet created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-  
 
 
  Puppet::Type.type('yumrepo') wrongly reports enabled repo   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 4.10.12  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2019/09/05 7:58 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Anthony Chevalet  
 

  
 
 
 
 

 
 Puppet Version: 4.10.12 Puppet Server Version: 2.8.1 OS Name/Version: CentOS Linux release 7.6.1810 I have weird behavior which occurs randomly where Puppet::Type.type('yumrepo') reports that a yum repo is enabled despite it is not.  I'm using this fact    
 
 
 
 
 require 'puppet'def to_boolean(value)  
 
 
   %w[absent yes true 1].include?(value.downcase)  
 
 
 endFacter.add('enabled_repos') do  
 
 
   setcode do  
 
 

Jira (PUP-9465) group resource type misunderstands/misuses libuser

2019-09-05 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  PUP-9465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
 In addition to that, the forcelocal parameter is also being used by the useradd provider. We'd also have to implement a libuser provider for the user type.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.86734.1567695180351%40Atlassian.JIRA.


Jira (PUP-9465) group resource type misunderstands/misuses libuser

2019-09-05 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  PUP-9465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
 I've put up a PR here: https://github.com/puppetlabs/puppet/pull/7695 The only changes to the groupadd provider are the deprecation warnings, directing Puppet users to the separate libuser provider. Next steps would be to actually remove the libuser feature and the forcelocal parameter for Puppet 7.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.86654.1567691760330%40Atlassian.JIRA.


Jira (FACT-2012) Facter should not display fact if its value is nil

2019-09-05 Thread Oana Tanasoiu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oana Tanasoiu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2012  
 
 
  Facter should not display fact if its value is nil   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oana Tanasoiu  
 
 
Created: 
 2019/09/05 4:56 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Oana Tanasoiu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit 

Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows

2019-09-05 Thread Dirk Heinrichs (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dirk Heinrichs commented on  PUP-6382  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add "Automatic (delayed start)" as option for Service Resource on Windows   
 

  
 
 
 
 

 
 Will it be available in P6 only or also backported to P5?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.135151.1464896598000.86496.1567683180365%40Atlassian.JIRA.


Jira (PUP-9998) Puppet agent --disable is ignored with cron puppet agent (splay).

2019-09-05 Thread Daniel Steininger (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Steininger commented on  PUP-9998  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet agent --disable is ignored with cron puppet agent (splay).   
 

  
 
 
 
 

 
 A better behaviour would be if puppet agent would check the lock file again after the sleep.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323623.1567679385000.86467.1567679640126%40Atlassian.JIRA.


Jira (PUP-9998) Puppet agent --disable is ignored with cron puppet agent (splay).

2019-09-05 Thread Daniel Steininger (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Steininger created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9998  
 
 
  Puppet agent --disable is ignored with cron puppet agent (splay).   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 4.10.12  
 
 
Assignee: 
 Henrik Lindberg  
 
 
Components: 
 Functions  
 
 
Created: 
 2019/09/05 3:29 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Daniel Steininger  
 

  
 
 
 
 

 
 Puppet Version: v4.10.12 OS Name/Version: Debian GNU/Linux 8 (jessie) Desired Behavior: All puppet runs should not start until the lock file is available.  Actual Behavior: It seems that the puppet agent command checks if the lock file exists in the early state. If not, the splay sleep starts. Then the puppet run itself starts. When I call "puppet agent - disabled" after Cron based puppet is started. The lock file has no effect on the puppet run, which starts after the sleep phase.  Test scenario  2019-09-05 07:48:46 /opt/puppetlabs/bin/puppet agent --config /etc/puppetlabs/puppet/puppet.conf --onetime --no-daemonize --logdest /var/log/puppetlabs/puppet/puppet.log  starts and is in sleep mode ... 2019-09-05 07:49:25 puppet agent --disable (other shell) ... ... 20 minutes later:  ... sleep over -> Puppet is on going:  ... Puppet is done 2019-09-05 08:18:33 echo $? 0 Lock file is still present: The second run stops correctly.  
 
 
 
 
 root@server:/etc/puppetlabs/puppet# /opt/puppetlabs/bin/puppet agent --config /etc/puppetlabs/puppet/puppet.conf --onetime --no-daemonize --logdest /var/log/puppetlabs/puppet/puppet.log  
 

Jira (FACT-2009) Replacement of : with => should not be done inside fact values

2019-09-05 Thread Sebastian Miclea (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Miclea assigned an issue to Alexandru Popa  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2009  
 
 
  Replacement of : with => should not be done inside fact values   
 

  
 
 
 
 

 
Change By: 
 Sebastian Miclea  
 
 
Assignee: 
 Alexandru Popa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323197.1567507573000.86423.1567674720331%40Atlassian.JIRA.


Jira (FACT-2009) Replacement of : with => should not be done inside fact values

2019-09-05 Thread Sebastian Miclea (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Miclea assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2009  
 
 
  Replacement of : with => should not be done inside fact values   
 

  
 
 
 
 

 
Change By: 
 Sebastian Miclea  
 
 
Assignee: 
 Alexandru Popa  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323197.1567507573000.86426.1567674720343%40Atlassian.JIRA.


Jira (PUP-9465) group resource type misunderstands/misuses libuser

2019-09-05 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  PUP-9465  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
 James Ralston, makes sense. The thing is, groupadd is currently not being defaulted to any platform, in fact it's the only suitable provider for Linux, so that's why it gets picked. When we introduce the new libuser provider, we have to explicitly default groupadd to avoid having libuser getting picked up by mistake.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.293306.1548368109000.86399.1567669680881%40Atlassian.JIRA.


Jira (PUP-9993) lookup's knockout_prefix cannot be undef, contrary to the documentation

2019-09-05 Thread Fabien Wernli (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fabien Wernli commented on  PUP-9993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: lookup's knockout_prefix cannot be undef, contrary to the documentation   
 

  
 
 
 
 

 
 My initial use-case was to parameterize a class with `$knockout_prefix` and `undef` would disable it. Of course I can use a switch to enable/disable it, but this is still either a bug or a docbug.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323217.1567511185000.86391.1567666560385%40Atlassian.JIRA.