Jira (PUP-3262) By default, the cadir should be separated from the ssldir

2019-07-24 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-3262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: By default, the cadir should be separated from the ssldir   
 

  
 
 
 
 

 
 This continues to be a problem and is easy to trigger accidentally: https://tickets.puppetlabs.com/browse/ENTERPRISE-1274  
 

  
 
 
 
 

 
 
 

 
 
 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.51395.141089306.30372.1564019340744%40Atlassian.JIRA.


Jira (BOLT-1455) out::message messages don't print when format=json

2019-07-24 Thread Chris Cowell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Cowell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1455  
 
 
  out::message messages don't print when format=json   
 

  
 
 
 
 

 
Change By: 
 Chris Cowell  
 
 
Labels: 
 docs_reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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.315274.1562178132000.30316.1564013220100%40Atlassian.JIRA.


Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha commented on  PUP-9920  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
 I think we should be able to handle this one, I'll work with Jean  
 

  
 
 
 
 

 
 
 

 
 
 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.318037.156401119.30288.1564011900099%40Atlassian.JIRA.


Jira (PUP-9920) Prepare release announcement (Puppet Platform 6.7.1)

2019-07-24 Thread Jed Gresham (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jed Gresham updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9920  
 
 
  Prepare release announcement (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
 Will you take care of this please? On Wed, Jul 24, 2019 at 6:34 PM Nirupama Mantha (JIRA) < –  Jed Gresham Director of Product, Puppet 407.408.5577  
 

  
 
 
 
 

 
Change By: 
 Jed Gresham  
 
 
Attachment: 
 noname  
 

  
 
 
 
 

 
 
 

 
 
 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.318037.156401119.30279.1564011540112%40Atlassian.JIRA.


Jira (PUP-9925) Communicate scope and timeline of next release (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9925  
 
 
  Communicate scope and timeline of next release (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/07/24 4:34 PM  
 
 
Due Date: 
2019/07/27 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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-9924) Update Confluence and JIRA based on release (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9924  
 
 
  Update Confluence and JIRA based on release (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/07/24 4:34 PM  
 
 
Due Date: 
2019/07/27 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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-9923) Send release announcement (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9923  
 
 
  Send release announcement (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Sara Meisburger  
 
 
Created: 
 2019/07/24 4:34 PM  
 
 
Due Date: 
2019/07/26 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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.7.1 is now available". 
  
 

  
 
 
 
 

 
 
 


Jira (PUP-9922) Publish documentation and updates and release notes (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9922  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/07/24 4:33 PM  
 
 
Due Date: 
2019/07/26 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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-9920) Prepare release announcement (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9920  
 
 
  Prepare release announcement (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jed Gresham  
 
 
Created: 
 2019/07/24 4:33 PM  
 
 
Due Date: 
2019/07/25 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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-9921) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9921  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/07/24 4:33 PM  
 
 
Due Date: 
2019/07/25 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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 (PUP-9919) Prepare documentation updates and release notes (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9919  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/07/24 4:33 PM  
 
 
Due Date: 
2019/07/26 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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-9917) Prepare JIRA and Confluence for release (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9917  
 
 
  Prepare JIRA and Confluence for release (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/07/24 4:32 PM  
 
 
Due Date: 
2019/07/24 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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.7.1 and puppet-agent 6.7.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y 

Jira (PUP-9918) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.1)

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9918  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/07/24 4:32 PM  
 
 
Due Date: 
2019/07/24 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-26) 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 HipChat) 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-9916) Puppet Platform 6.7.1 Release - 2019-07-26

2019-07-24 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9916  
 
 
  Puppet Platform 6.7.1 Release - 2019-07-26
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/07/24 4:32 PM  
 
 
Due Date: 
2019/07/26 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 Puppet Platform 6.7.1 Release - 2019-07-26  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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


Jira (BOLT-1456) bolt debug output shows task input as a ruby hash, not json

2019-07-24 Thread Chris Cowell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Cowell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1456  
 
 
  bolt debug output shows task input as a ruby hash, not json   
 

  
 
 
 
 

 
Change By: 
 Chris Cowell  
 
 
Labels: 
 docs_reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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.315307.1562198295000.30136.1564009200175%40Atlassian.JIRA.


Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index

2019-07-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8949  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Package pip provide won't work with ensure latest and custom index   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/puppet/pull/7633  
 

  
 
 
 
 

 
 
 

 
 
 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.261544.1529423125000.29727.1563999420149%40Atlassian.JIRA.


Jira (PDB-4371) Add initial support for catalog input related queries

2019-07-24 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning assigned an issue to Rob Browning  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4371  
 
 
  Add initial support for catalog input related queries   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Assignee: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

 
 
 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.308642.155786921.29704.1563998280227%40Atlassian.JIRA.


Jira (BOLT-1323) Support WinRM with Kerberos (from Windows node)

2019-07-24 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1323  
 
 
  Support WinRM with Kerberos (from Windows node)   
 

  
 
 
 
 

 
Change By: 
 Ethan Brown  
 

  
 
 
 
 

 
 BOLT-126 was originally intended to be for supporting Kerberos authentication over WinRM.After working on that effort, it was uncovered that the {{winrm}} gem only supports the MIT {{GSSAPI}}. While this is fine on Linux, where installation of the relevant packages is straightforward, it is a non-standard approach on Windows (even given the Windows installer for GSSAPI). No Windows admin wants to install an additional 3rd party library to access Kerberos functionality that is already built into the OS.Supporting Windows to Windows authentication using Kerberos and WinRM should use built-in Windows API calls, and should default to using the credentials from the active domain login (as a starting point).This will require adding support to the WinRM gem to provide encryption / decryption using Windows APIs.There are some useful details in  [  https://docs.microsoft.com/en-us/windows/desktop/secauthn/sspi-kerberos-interoperability-with-gssapi ]  about translating gssapi calls to equivalent Windows APIs:  * gss_get_mic -> MakeSignature* gss_verify_mic -> VerifySignature* gss_init_sec_context -> [InitializeSecurityContext (Kerberos)|https://msdn.microsoft.com/en-us/library/windows/desktop/aa375507%28v=vs.85%29.aspx?f=255=-2147217396]* GSS_Wrap -> [EncryptMessage (Kerberos)|https://msdn.microsoft.com/en-us/library/Aa375385(v=VS.85).aspx]* GSS_Unwrap -> [DecryptMessage (Kerberos)|https://msdn.microsoft.com/en-us/library/Aa375215(v=VS.85).aspx]{{_iov}} functions may already be supported with the above APIs, but may require the {{*Ex}} versions.  Code changes to winrm gem will need to be made to replicate the behavior of the {{HttpGSSAPI}} class at  [  https://github.com/WinRb/WinRM/blob/master/lib/winrm/http/transport.rb#L287-L461 ]  in a new class, {{HttpSSPI}}Ruby already has some limited helper code available around the Win32 SSPI layer, namely support for the {{AcquireCredentialsHandle}} and {{InitializeSecurityContext}} APIs - see  [  https://github.com/ruby/ruby/blob/d48783bb0236db505fe1205d1d9822309de53a36/ext/win32/lib/win32/sspi.rb ] The code from gssapi simple that will need to be ported to a Windows API equivalent is at  [  https://github.com/zenchild/gssapi/blob/master/lib/gssapi/simple.rb ] Some other ideas tossed around for consuming the MIT dep:- compile / build / redistribute Windows binaries in MSI from https://github.com/krb5/krb5    - build once / stash as a "static" dep in Artifactory    - build via some kind of build step in puppet-runtime    - not great solution for testing "source" - drag in older prebuilt binaries from upstream somehow - provide docs on how to install deps in Windows  
 

  
 
 
 
   

Jira (PDB-4456) Add support for import/export for "replace catalog inputs"

2019-07-24 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4456  
 
 
  Add support for import/export for "replace catalog inputs"   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Summary: 
 Add support for import/export for " repalce replace  catalog inputs"  
 

  
 
 
 
 

 
 
 

 
 
 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.317966.1563991828000.29557.1563992220316%40Atlassian.JIRA.


Jira (PDB-4456) Add support for import/export for "repalce catalog inputs"

2019-07-24 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4456  
 
 
  Add support for import/export for "repalce catalog inputs"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/07/24 11:10 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 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 (PDB-4455) Add support for syncing catalog inputs

2019-07-24 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4455  
 
 
  Add support for syncing catalog inputs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/07/24 11:09 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 Add a new sync-entity to pe-puppetdb-extensions to enable syncing the catalog inputs via "replace catalog inputs" command. Add tests to verify convergence, proper data handling, and proper handling of producer timestamp.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
 

Jira (BOLT-1481) Kick off release pipeline (Bolt 1.27.0)

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1481  
 
 
  Kick off release pipeline (Bolt 1.27.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Tom Beech  
 
 
Created: 
 2019/07/24 10:04 AM  
 
 
Due Date: 
2019/07/24 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-24) With our automated builds pipeline 
 
Ensure the sha at the tip of the master branch of bolt has been promoted to bolt-vanagon 
Based on that sha ensure both the component pipeline and bolt-vanagon packaging pipeline have completed successfully 
bolt packages are staged on puppet-bolt based on sha from bolt vanagon 
Go to the release pipeline 
Click "Build with Parameters" 
Check the PUBLIC checkbox 
Enter the version in the NEW_TAG box (x.y.z format) 
Click build! 
 And make sure the pipeline is green!  
 

  
 
 
 
 

 
 
 


Jira (BOLT-1482) Publish release artifacts (Bolt 1.27.0)

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1482  
 
 
  Publish release artifacts (Bolt 1.27.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Tom Beech  
 
 
Created: 
 2019/07/24 10:04 AM  
 
 
Due Date: 
2019/07/24 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-24) Run the Bolt shipping pipeline. Set REF to 1.27.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

Jira (BOLT-1486) Send release announcements (Bolt 1.27.0)

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1486  
 
 
  Send release announcements (Bolt 1.27.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Chris Cowell  
 
 
Created: 
 2019/07/24 10:04 AM  
 
 
Due Date: 
2019/07/24 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-24) When docs have finished building (check that all links resolve appropriately) - 
 
Create an e-mail announcement with the subject "Bolt  now available". 
 
In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). 
In the Bcc: field, enter the following addresses: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com 
In the body, include a summary of the release and links to the release notes and installation instructions. 
  
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
 (Optional) Set up a canned response in Gmail so that you don't have to recreate this email every time: Subject: Bolt X.Y.Z now available Body: Greetings! We're happy to announce the release of Bolt X.Y.Z. Highlights in this release include: 
 
Gerund phrase 
Gerund phrase For more information, check out the 

Jira (BOLT-1485) Docs for bolt release (Bolt 1.27.0)

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1485  
 
 
  Docs for bolt release (Bolt 1.27.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Chris Cowell  
 
 
Created: 
 2019/07/24 10:04 AM  
 
 
Due Date: 
2019/07/24 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-24) Release notes and docs changes for bolt 1.27.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (BOLT-1483) Update the release spreadsheet (Bolt 1.27.0)

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1483  
 
 
  Update the release spreadsheet (Bolt 1.27.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Tom Beech  
 
 
Created: 
 2019/07/24 10:04 AM  
 
 
Due Date: 
2019/07/24 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-24) Update the release google spreadsheet for Bolt 1.27.0.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (BOLT-1484) Update homebrew-puppet (Bolt 1.27.0)

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1484  
 
 
  Update homebrew-puppet (Bolt 1.27.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Tom Beech  
 
 
Created: 
 2019/07/24 10:04 AM  
 
 
Due Date: 
2019/07/24 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-24) Until we automate this, you'll also need to update the version and SHA hashes of homebrew-puppet. To do this please 
 
Create a fork of the homebrew-puppet repo 
Create a new branch on that fork 
Run "rake 'brew:cask[puppet-bolt]'" 
Verify Casks/puppet-bolt.rb was updated to the correct version 
Put up a PR to homebrew-puppet and request review 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

 

Jira (BOLT-1479) Bolt 1.27.0 2019-07-24 Release

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1479  
 
 
  Bolt 1.27.0 2019-07-24 Release   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Tom Beech  
 
 
Created: 
 2019/07/24 10:03 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 Bolt 1.27.0 2019-07-24 Release  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  

Jira (BOLT-1480) Reconcile git commits, JIRA tickets, and versions (Bolt 1.27.0)

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1480  
 
 
  Reconcile git commits, JIRA tickets, and versions (Bolt 1.27.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Tom Beech  
 
 
Created: 
 2019/07/24 10:03 AM  
 
 
Due Date: 
2019/07/24 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Beech  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-07-24) 
 
Ensure all tickets referenced in the commit log have been targeted at the release. 
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=Bolt and fixVersion="Bolt x.y.z"' in JIRA. 
Ensure all tickets have release notes. 
Ensure all tickets have been resolved. 
In JIRA releases, change 'BOLT Next' to 'BOLT x.y.z' with the release date. Create a new 'BOLT Next'. 
  
 

  
 
 
 
 

 
 
 

 
 
   

Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix

2019-07-24 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9914  
 
 
  v6.7.0 Breaks camptocamp-postfix   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.7.1  
 

  
 
 
 
 

 
 
 

 
 
 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.317861.1563928891000.29186.1563987180378%40Atlassian.JIRA.


Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix

2019-07-24 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9914  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: v6.7.0 Breaks camptocamp-postfix   
 

  
 
 
 
 

 
 FYI, we've merged a fix for this issue (https://github.com/puppetlabs/puppet/commit/ce76a749ccadc5fbddd58122bb9a55be36e17d9c) and we should have a 6.7.1 release out soon.  
 

  
 
 
 
 

 
 
 

 
 
 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.317861.1563928891000.29169.1563987120718%40Atlassian.JIRA.


Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix

2019-07-24 Thread Ketan Patel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ketan Patel commented on  PUP-9914  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: v6.7.0 Breaks camptocamp-postfix   
 

  
 
 
 
 

 
 same issue here.  
 

  
 
 
 
 

 
 
 

 
 
 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.317861.1563928891000.29127.1563985920296%40Atlassian.JIRA.


Jira (BOLT-1315) Collect analytics about Boltdir usage

2019-07-24 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1315  
 
 
  Collect analytics about Boltdir usage   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Release Notes Summary: 
 Bolt will  now send  report how the boltdir was determined to  analytics  information about which type of project directory . IE  is  being used  the user default, from a dir with bolt . yaml, from a dir called Boltdir, or explicitly specified  
 

  
 
 
 
 

 
 
 

 
 
 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.309059.1558038203000.29115.1563985800376%40Atlassian.JIRA.


Jira (BOLT-1315) Collect analytics about Boltdir usage

2019-07-24 Thread Tom Beech (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Beech updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1315  
 
 
  Collect analytics about Boltdir usage   
 

  
 
 
 
 

 
Change By: 
 Tom Beech  
 
 
Release Notes Summary: 
 Bolt will now send analytics information about which type of project directory is being used.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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.309059.1558038203000.29112.1563985740552%40Atlassian.JIRA.


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

2019-07-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6382  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 We could implement this with something like ...   lib/puppet/type/service.rb  
 
 
 
 
  newproperty(:enable, :required_features => :enableable) do  
 
 
   ...  
 
 
  newvalue(:delayed, :event => :service_delayed_start) do  
 
 
provider.delayed_start  
 
 
  end
  
 
 
 
  lib/puppet/provider/service/windows.rb  
 
 
 
 
   def delayed_start  
 
 
 enable  
 
 
 Puppet::Util::Windows::Service.set_startup_mode_delayed( @resource[:name] )  
 
 
   rescue => detail  
 
 
 raise Puppet::Error.new(_("Cannot enable %{resource_name} for delayed start, error was: %{detail}") % { resource_name: @resource[:name], detail: detail }, detail )  
 
 
   end
  
 
 

Jira (PUP-9915) Debian: avoid updating systemd defaults for every release

2019-07-24 Thread Christian Hofstaedtler (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Hofstaedtler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9915  
 
 
  Debian: avoid updating systemd defaults for every release   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2019/07/24 2:30 AM  
 
 
Environment: 
 OS: Debian 10, any future version  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Christian Hofstaedtler  
 

  
 
 
 
 

 
 Puppet Version: (all released agent versions) Puppet Server Version: OS Name/Version: Debian 10   The systemd provider has a hard-coded list of Debian releases that use systemd. For the foreseeable future this should include all new releases. Right now the hard-coded list means the file needs updating for every release. Desired Behavior: systemd should be default-available on future releases.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1936  
 
 
  facter -p segfaults with facts that call open-uri.open   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.316163.1562873035000.28705.1563960600386%40Atlassian.JIRA.


Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1936  
 
 
  facter -p segfaults with facts that call open-uri.open   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 5  
 

  
 
 
 
 

 
 
 

 
 
 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.316163.1562873035000.28701.1563960600338%40Atlassian.JIRA.


Jira (FACT-1935) Facter ipaddress6 on Windows returns link-local address with interface identifier

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1935  
 
 
  Facter ipaddress6 on Windows returns link-local address with interface identifier   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.316045.1562828787000.28697.1563960120223%40Atlassian.JIRA.


Jira (FACT-1935) Facter ipaddress6 on Windows returns link-local address with interface identifier

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1935  
 
 
  Facter ipaddress6 on Windows returns link-local address with interface identifier   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.316045.1562828787000.28695.1563960120214%40Atlassian.JIRA.


Jira (PUP-9752) Systemd should be default service provider for Debian buster

2019-07-24 Thread Daniel Krämer
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Krämer commented on  PUP-9752  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Systemd should be default service provider for Debian buster   
 

  
 
 
 
 

 
 Change was merged  
 

  
 
 
 
 

 
 
 

 
 
 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.312293.1560388027000.28661.1563958560320%40Atlassian.JIRA.


Jira (PUP-9041) AIX nim provider can't be used on a NIM master

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9041  
 
 
  AIX nim provider can't be used on a NIM master   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.267945.153332494.28659.1563958320750%40Atlassian.JIRA.


Jira (PUP-9041) AIX nim provider can't be used on a NIM master

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9041  
 
 
  AIX nim provider can't be used on a NIM master   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.267945.153332494.28653.1563958320700%40Atlassian.JIRA.


Jira (FACT-1964) Facter retrive the first mountpoint when multiple mountpoints are mounted to the same directory

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1964  
 
 
  Facter retrive the first mountpoint when multiple mountpoints are mounted to the same directory   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.317592.1563890051000.28613.1563957240331%40Atlassian.JIRA.


Jira (FACT-1964) Facter retrive the first mountpoint when multiple mountpoints are mounted to the same directory

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1964  
 
 
  Facter retrive the first mountpoint when multiple mountpoints are mounted to the same directory   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.317592.1563890051000.28609.1563957240310%40Atlassian.JIRA.


Jira (PUP-9605) Type package (provider yum) fails when handling kernel packages

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9605  
 
 
  Type package (provider yum) fails when handling kernel packages   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.303636.1554712703000.28545.1563957064801%40Atlassian.JIRA.


Jira (PUP-7312) Confine systemd provider to init system matching systemd

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7312  
 
 
  Confine systemd provider to init system matching systemd   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-07-10, PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.178941.1488893881000.28505.1563957064570%40Atlassian.JIRA.


Jira (PUP-9908) When setting ensure=running on a osx service, Puppet is reporting the service as absent

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9908  
 
 
  When setting ensure=running on a osx service, Puppet is reporting the service as absent   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.317053.1563430406000.28606.1563957065070%40Atlassian.JIRA.


Jira (PUP-9722) Regression: File mode changed on every puppet run

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9722  
 
 
  Regression: File mode changed on every puppet run   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12, PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.310253.1558976203000.28529.1563957064728%40Atlassian.JIRA.


Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1919  
 
 
  blank/negative facter cache due to timed out EC2 metadata   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.307267.1556898834000.28572.1563957064929%40Atlassian.JIRA.


Jira (FACT-1884) Add NIM master detection

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1884  
 
 
  Add NIM master detection   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.276290.1537303892000.28551.1563957064826%40Atlassian.JIRA.


Jira (PUP-9754) Log resident configuration upon daemon launch

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9754  
 
 
  Log resident configuration upon daemon launch   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.312512.1560543853000.28576.1563957064943%40Atlassian.JIRA.


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8736  
 
 
  /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12, PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.251027.1526491177000.28517.1563957064642%40Atlassian.JIRA.


Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9719  
 
 
  Cannot run Puppet Agent as Administrator if first PA run is done as System   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.310162.1558726819000.28542.1563957064790%40Atlassian.JIRA.


Jira (PUP-9814) pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM

2019-07-24 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9814  
 
 
  pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-07-23 , NW - 2019-08-07  
 

  
 
 
 
 

 
 
 

 
 
 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.315397.1562338786000.28602.1563957065053%40Atlassian.JIRA.


Jira (FACT-1884) Add NIM master detection

2019-07-24 Thread Sebastian Miclea (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Miclea commented on  FACT-1884  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add NIM master detection   
 

  
 
 
 
 

 
 Passing pipeline: https://jenkins-platform.delivery.puppetlabs.net/view/Adhoc/job/platform_puppet-agent-extra_puppet-agent-suite-init_adhoc-ad_hoc/654/  
 

  
 
 
 
 

 
 
 

 
 
 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.276290.1537303892000.28491.1563956520121%40Atlassian.JIRA.


Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix

2019-07-24 Thread Benedikt Sterzinger (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Benedikt Sterzinger commented on  PUP-9914  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: v6.7.0 Breaks camptocamp-postfix   
 

  
 
 
 
 

 
 Same issue here.   
 

  
 
 
 
 

 
 
 

 
 
 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.317861.1563928891000.28484.1563955860166%40Atlassian.JIRA.


Jira (PUP-9914) v6.7.0 Breaks camptocamp-postfix

2019-07-24 Thread Alexander Heimann (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Heimann commented on  PUP-9914  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: v6.7.0 Breaks camptocamp-postfix   
 

  
 
 
 
 

 
 We have the same problem with CentOS 7.6  
 

  
 
 
 
 

 
 
 

 
 
 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.317861.1563928891000.28480.1563955680225%40Atlassian.JIRA.