Jira (PUP-3338) Systemd should be the default service provider for SLES 12

2014-09-24 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden created an issue


















 Puppet /  PUP-3338



  Systemd should be the default service provider for SLES 12 










Issue Type:

  Improvement




Affects Versions:


 3.7.1




Assignee:


 Unassigned




Created:


 24/Sep/14 11:40 AM




Priority:

  Normal




Reporter:

 Rob Braden










As of SLES 12, systemd should be the default service provider.
Using the SLES 12 RC, puppet is unable to properly determine if a service is enabled.












   

 Add Comment






















 This message was sent by Atlassian JIRA 

Jira (PUP-3338) Systemd should be the default service provider for OpenSUSE = 12 and SLES 12

2014-09-24 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden updated an issue


















 Puppet /  PUP-3338



  Systemd should be the default service provider for OpenSUSE = 12 and SLES 12 










Change By:

 Rob Braden




Summary:

 Systemdshouldbethedefaultserviceproviderfor OpenSUSE=12and SLES12












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3338) Systemd should be the default service provider for OpenSuSE = 12 and SLES 12

2014-09-24 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden updated an issue


















 Puppet /  PUP-3338



  Systemd should be the default service provider for OpenSuSE = 12 and SLES 12 










Change By:

 Rob Braden




Summary:

 Systemdshouldbethedefaultserviceproviderfor OpenSUSE OpenSuSE =12andSLES12












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1491) Remove Fedora 18 from default mocks

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden created an issue


















 Puppet /  PUP-1491



  Remove Fedora 18 from default mocks 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Created:


 22/Jan/14 9:18 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You 

Jira (PUP-1491) Remove Fedora 18 from default mocks

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden assigned an issue to Rob Braden


















 Puppet /  PUP-1491



  Remove Fedora 18 from default mocks 










Change By:

 Rob Braden




Assignee:

 EricSorenson RobBraden












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (FACT-242) (packaging) Remove Fedora 18 from default build targets

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden created an issue


















 Facter /  FACT-242



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:41 AM




Priority:

  Normal




Reporter:

 Rob Braden












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (MCO-166) (packaging) Remove Fedora 18 from default build targets

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden created an issue


















 MCollective /  MCO-166



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:44 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 










Jira (HI-149) (packaging) Remove Fedora 18 from default build targets

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden created an issue


















 Hiera /  HI-149



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:46 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 















Jira (PUP-1491) (packaging)Remove Fedora 18 from default mocks

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden updated an issue


















 Puppet /  PUP-1491



  (packaging)Remove Fedora 18 from default mocks 










Change By:

 Rob Braden




Summary:

 (packaging) RemoveFedora18fromdefaultmocks












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (FACT-242) (packaging) Remove Fedora 18 from default build targets

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden updated an issue


















 Facter /  FACT-242



  (packaging) Remove Fedora 18 from default build targets 










Change By:

 Rob Braden









 Fedora18reachedend-of-lifeonJanuary14,2014.RemoveFedora18fromthelistofdefaultpackagebuildmocks.TheF18yumreposwillberemovedfromyum.puppetlabs.comonMarch18.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PDB-343) (packaging) Remove Fedora 18 from default build targets

2014-01-22 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden created an issue


















 PuppetDB /  PDB-343



  (packaging) Remove Fedora 18 from default build targets 










Issue Type:

  Task




Assignee:

 Rob Braden




Created:


 22/Jan/14 9:47 AM




Priority:

  Normal




Reporter:

 Rob Braden










Fedora 18 reached end-of-life on January 14, 2014. Remove Fedora 18 from the list of default package build mocks. The F18 yum repos will be removed from yum.puppetlabs.com on March 18.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 













Jira (PDB-468) Update scripts to leverage JAVA_BIN

2014-02-19 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden assigned an issue to Rob Braden


















 PuppetDB /  PDB-468



  Update scripts to leverage JAVA_BIN 










Change By:

 Rob Braden




Assignee:

 RobBraden












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PDB-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)

2014-02-19 Thread Rob Braden (JIRA)
Title: Message Title










 

 Rob Braden assigned an issue to Rob Braden


















 PuppetDB /  PDB-142



  puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) 










Change By:

 Rob Braden




Assignee:

 RobBraden












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PUP-3777) Readonly mountpoint mounted after read-write mountpoint causes unexpected altering of permissions

2014-12-18 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-3777 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Readonly mountpoint mounted after read-write mountpoint causes unexpected altering of permissions  
 
 
 
 
 
 
 
 
 
 
I don't think we should implement 'nosharecache' as a default option, I'd be more inclined to document this specific edge case and let the user decide how to remediate, including using 'nosharecache' as a mount option if they choose to. I'm open to opposing viewpoints, but it feels weird to try to hide the designed behavior. The caching issue above is one example.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1032) Ezbake: Get pe-puppetdb building with ezbake

2015-01-27 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-1032 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Ezbake: Get pe-puppetdb building with ezbake  
 
 
 
 
 
 
 
 
 
 
This work is largely complete, though not really well tested. My inclination would be to close this and we can work through any issues that come up as bugs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3801) HP-UX User Provider not resetting password expiration after changing password hash.

2015-01-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Matthaus Owens 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3801 
 
 
 
  HP-UX User Provider not resetting password expiration after changing password hash.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 MatthausOwens 
 
 
 

Sprint:
 
 RE2015-01-21 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4390) Regression: Windows service provider fails to retrieve current state on 2003

2015-04-17 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-4390 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Regression: Windows service provider fails to retrieve current state on 2003  
 
 
 
 
 
 
 
 
 
 
Ryan - sorry, I moved this to resolved right as I was about to tag an RC build and hand it off, then got sidetracked by an issue that came up. 
3.8.0-rc0-745-gde6c188 should have it 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1891) Tag the release and create packages

2015-08-25 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-1891 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Tag the release and create packages  
 
 
 
 
 
 
 
 
 
 
Tagged 05df6b89faea628d03e714dfb55f14a662492c66 as 3.1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1891) Tag the release and create packages

2015-08-25 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Rob Braden 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1891 
 
 
 
  Tag the release and create packages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 MelissaStone RobBraden 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5324) Is the Jira tidy-up done for this release and prepared for the next one?

2015-10-19 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Steve Barlow 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5324 
 
 
 
  Is the Jira tidy-up done for this release and prepared for the next one?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 Rob Braden Steve Barlow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5326) Tag the release and create packages

2015-10-08 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-5326 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Tag the release and create packages  
 
 
 
 
 
 
 
 
 
 
http://builds.puppetlabs.lan/puppet-agent/1.2.6/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5332) Send out announcements

2015-10-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Rob Braden 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5332 
 
 
 
  Send out announcements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 Eric Sorenson Rob Braden 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5328) Go/no-go meeting (before 4pm)

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5328 
 
 
 
  Go/no-go meeting (before 4pm)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. 
Get a yes/no for the release from dev, docs, product, qa, releng. 
This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. 
Dependencies: 
 

Smoke testing
 
 
Participants: 
 

Rob Braden
 

Isaac Eldridge
 

Josh Cooper
 

Christopher Thorn
 

Rob Braden
 
 
 

Jira (PUP-5322) Update version number in source

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5322 
 
 
 
  Update version number in source  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Bump VERSION in lib/PUP/version.rb or project.clj to correct version. 
 

Commit the updated version file.
 

e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3".
 

If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask).
 

Once this is done, hand the SHA to be built to RelEng to be tagged.
 
 
Dependencies: 
 

Is the code ready for release?
 

Reconcile git commits and JIRA tickets
 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-5321) Reconcile git commits and JIRA tickets

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5321 
 
 
 
  Reconcile git commits and JIRA tickets  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. 
 

cd ~/work
 

git clone https://github.com/puppetlabs/ticketmatch
 

cd ~/work/puppet # or whatever the repo is you're releasing from
 

ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0
 
 
The output may contain the following headers: 
COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) 
Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier release (stable), but the ticket's fixVersion is not updated. 

Jira (PUP-5323) Merge master into stable

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5323 
 
 
 
  Merge master into stable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
For some releases, the code base will need to be merged down to stable. 
NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. 
Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: 
 
 
 
 
 
 
git fetch upstream 
 
 
 
 
git rebase upstream/master 
 
 
 
 
  
 
 
 
 
git checkout stable 
 
   

Jira (PUP-5329) Push tag

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5329 
 
 
 
  Push tag  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. 
Dependencies: 
 

Go / No Go meeting (except where it's required to push the tag to build packages - MSIs)
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

Jira (PUP-5332) Send out announcements

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5332 
 
 
 
  Send out announcements  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Created:
 

 2015/10/06 11:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
 

Rob Braden: update the release google spreadsheet.
 

Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014)
 

Send the drafted release notes email.
 

If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev).
 

If this release has security implications, also send the release announcement to puppet-security-announce
 

Make a PSA on IRC letting those kiddos know about the new release.
 

Something along the lines of "PSA: facter 1.7.3 now available"
 
 
Dependencies: 
 

Jira (PUP-5330) Packages pushed

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5330 
 
 
 
  Packages pushed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Push packages 
 

run `rake pl:jenkins:uber_ship`
 

You will need the keys to the castle (aka the passphrase) for this to work.
 

Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms.
 

Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay.
 

If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file.
 

If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
 
 
Dependencies: 
 
 

Jira (PUP-5333) Close all resolved tickets in Jira

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5333 
 
 
 
  Close all resolved tickets in Jira  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Close any tickets that have been resolved for the release. 
https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%22puppet-agent 1.2.6%22%20AND%20status%20%3D%20Resolved 
There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: 
 

Select Bulk Change - All # issues
 

Step 1 - choose all relevant issues (likely all of them)
 

Step 2 - Select "Transition Issues"
 

Step 3 - Select "Closed"
 

Step 4 - Select "Fixed" in Change Resolution.
 

View what is about to change and confirm it. Then commit the change.
 
 
Dependencies: 
 


Jira (PUP-5320) Is the code ready for release?

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5320 
 
 
 
  Is the code ready for release?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. 
All tests (spec, acceptance) should be passing on all platforms for both stable & master. 
 

If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc.
 

If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests
 

Move all items that should be moved from Ready for CI to Ready for Review
 
 
Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. 
https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%22puppet-agent 1.2.6%22 
 
 
 
 
 
 
   

Jira (PUP-5324) Is the Jira tidy-up done for this release and prepared for the next one?

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5324 
 
 
 
  Is the Jira tidy-up done for this release and prepared for the next one?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
This happens on Jira - we need to clean up the current release and prepare for the next release. 
 

Mark the version that's going out as "Released" in the Project Admin -> Versions panel.
 

Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future)
 

Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket):
 
 
 

'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone
 

'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
  

Jira (PUP-5331) Docs pushed

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5331 
 
 
 
  Docs pushed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Isaac Eldridge 
 
 
 

Created:
 

 2015/10/06 11:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Push the documentation updates to docs.puppetlabs.com. 
Dependencies: 
 

Go / No Go meeting (Status - Ship it!)
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 

Jira (PUP-5327) Smoke test packages

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5327 
 
 
 
  Smoke test packages  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Procedure may vary by project and point in the release cycle. Ask around. 
In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). 
For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. 
Lighter testing of Z releases is acceptable. 
 

Add a link to the Packages repository that you receive from the "Tag and create packages" subtask
 

Ping folks on your team for help with different platforms.
 

When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
 

When all 

Jira (PUP-5319) puppet-agent puppet-agent 1.2.6 2015-10-08 Release

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5319 
 
 
 
  puppet-agent puppet-agent 1.2.6 2015-10-08 Release  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
puppet-agent puppet-agent 1.2.6 2015-10-08 Release 
When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. 
 

The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them.
 

Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward.
 

When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
 
 
 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-5326) Tag the release and create packages

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5326 
 
 
 
  Tag the release and create packages  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Tag and create packages 
 

Developer provides the SHA - Rob Braden - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
 

checkout the sha
 

Make sure you are about to tag the correct thing
 

Create the tag e.g.) git tag -s -u {GPG key} 
 -m "1.7.3" 1.7.3
 

You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
 

DO NOT push the tag to the repo, keep it local only
 

`git describe` will show you the tag. Make sure you're building what you think you're building.
 


Jira (PUP-5325) Prepare long form release notes and short form release story

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5325 
 
 
 
  Prepare long form release notes and short form release story  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Isaac Eldridge 
 
 
 

Created:
 

 2015/10/06 11:35 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
Collaborating with product for release story 
Dependencies: 
 

Reconcile git commits and JIRA tickets
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 

Jira (PUP-5328) Go/no-go meeting (before 4pm)

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5328 
 
 
 
  Go/no-go meeting (before 4pm)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time.Get a yes/no for the release from dev, docs, product, qa, releng.This meeting is informal, over chat, and usually happens right before packages are pushed.Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release.Dependencies:  * Smoke testingParticipants:  * [~bradejr]  * [~ isaac nick . eldridge fagerlund ]  * [~josh]  * [~christopher.thorn]  * [~bradejr] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5325) Prepare long form release notes and short form release story

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-5325 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prepare long form release notes and short form release story  
 
 
 
 
 
 
 
 
 
 
The fix for PE-12273 is the only substantive change, and the reason for the release 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5325) Prepare long form release notes and short form release story

2015-10-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5325 
 
 
 
  Prepare long form release notes and short form release story  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 Isaac Eldridge Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5331) Docs pushed

2015-10-09 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5331 
 
 
 
  Docs pushed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 Isaac Eldridge Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5096) Windows Puppet build includes an OpenSSL with crazy defaults baked in

2015-09-01 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-5096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows Puppet build includes an OpenSSL with crazy defaults baked in  
 
 
 
 
 
 
 
 
 
 
Hi Jeff Bachtel, 
This issue is the same as https://github.com/oneclick/rubyinstaller/issues/153 (also discussed in https://github.com/oneclick/rubyinstaller/pull/47 ) 
In short, it's a limitation of openssl. You should be able to set the SSL_CERT_FILE environment variable in the app environment to point to the CA cert file. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5096) Windows Puppet build includes an OpenSSL with crazy defaults baked in

2015-09-01 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Rob Braden 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5096 
 
 
 
  Windows Puppet build includes an OpenSSL with crazy defaults baked in  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 

Story Points:
 
 2 
 
 
 

Sprint:
 
 RE 2015-09-09 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5096) Windows Puppet build includes an OpenSSL with crazy defaults baked in

2015-09-04 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-5096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows Puppet build includes an OpenSSL with crazy defaults baked in  
 
 
 
 
 
 
 
 
 
 
Jeff Bachtel In future builds we're going to set that value to something more sane by default, but you can use the openssl environment variables (SSL_CERT_FILE, SSL_CERT_DIR, etc) to set it to what you need for your usage. 
I'll resolve this ticket for now, but please feel free to comment/reopen if this doesn't satisfy your requirements. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2657) Untangle the use of facter from the 2.3.x build tasks

2016-06-08 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2657 
 
 
 
  Untangle the use of facter from the 2.3.x build tasks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Sprint:
 
 RE Services 2016-06-15 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6356) puppet-agent suite tests fail: Invalid resource type test_custom_type

2016-05-25 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6356 
 
 
 
  puppet-agent suite tests fail: Invalid resource type test_custom_type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Issue Type:
 
 Bug CI Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6356) puppet-agent suite tests fail: Invalid resource type test_custom_type

2016-05-25 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6356 
 
 
 
  puppet-agent suite tests fail: Invalid resource type test_custom_type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 PUP 4.5.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6356) puppet-agent suite tests fail: Invalid resource type test_custom_type

2016-05-25 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6356 
 
 
 
  puppet-agent suite tests fail: Invalid resource type test_custom_type  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/25 3:13 PM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
https://jenkins.puppetlabs.com/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-stable/135/SLAVE_LABEL=beaker,TEST_TARGET=arista4-32a/console 
a number of errors like the following: 
 
 
 
 
 
 
14:44:53 Test Case tests/security/cve-2013-4761_resource_type.rb reported: # 
 
 
 
 
14:44:53puppet agent -t --server qnrq12cz19ftx7e.delivery.puppetlabs.net 
 
 
 
 
14:44:53   Last 10 lines of output were: 
 
 
 
 

Jira (PDB-2748) puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken

2016-05-27 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
That's strange, all that was changed were some linker flags (to drop the puppet-agent libdir from the front of the rpath) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2748) puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken

2016-05-27 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
ping Branan Riley or Michael Smith does that look familiar? ^^^ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2748) puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken

2016-05-27 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
It looks like this is fixed, with the fix to RE-7163. A rebuild now should pick up the updated toolchain. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6356) puppet-agent suite tests fail: Invalid resource type test_custom_type

2016-05-26 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-6356 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-agent suite tests fail: Invalid resource type test_custom_type  
 
 
 
 
 
 
 
 
 
 
Yep, just passed and is in the process of promoting to PE, so this can be resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2748) puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken

2016-06-21 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
Works for me.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2748) puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken

2016-06-21 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
Andrew Roetker When do you want it? Early next week work ok? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1371) Build failure on cisco-wrlinux5 - leatherman locale

2016-03-15 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1371 
 
 
 
  Build failure on cisco-wrlinux5 - leatherman locale  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/03/15 4:33 PM 
 
 
 

Environment:
 
 
cisco-wrlinux5 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
https://jenkins.puppetlabs.com/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_pkg-van-ship_daily-master/100/BUILD_TARGET=cisco-wrlinux-5-x86_64,SLAVE_LABEL=beaker/consoleFull 
 
15:54:50 test 1 15:54:50 Start 1: libfacter tests 15:54:50  15:54:50 1: Test command: /tmp/tmp.ocP7qb28Gu/facter/bin/libfacter_test 15:54:50 1: Test timeout computed to be: 9.99988e+06 15:54:50 1: terminate called after throwing an instance of 'facter::logging::locale_error' 15:54:50 1: what(): leatherman::locale::get_locale is not supported on this platform 15:54:50 1/2 Test #1: libfacter tests ..***Exception: Other 0.01 sec 15:54:50 test 2 15:54:50 Start 2: facter smoke 15:54:50  15:54:50 2: Test command: /tmp/tmp.ocP7qb28Gu/facter/bin/facter 15:54:50 2: Test timeout computed to be: 9.99988e+06 15:54:50 2: failed to initialize logging system due to a locale error: leatherman::locale::get_locale is not supported on this platform 15:54:50 2:  15:54:50 2/2 Test #2: facter smoke .***Failed 0.01 sec
 
 
 
 
 
 
 
 
 
 

Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8

2016-03-14 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2354 
 
 
 
  PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Labels:
 
 burnside-ss 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8

2016-03-14 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2354 
 
 
 
  PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Assignee:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8

2016-03-14 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-2354 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8  
 
 
 
 
 
 
 
 
 
 
Per Andrew Roetker and Ryan Senior, only FOSS-side work remains - touching the upgrade test pipeline matrix. Removing the Burnside-ss label. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8

2016-03-09 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-2354 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8  
 
 
 
 
 
 
 
 
 
 
We're working on the issue, unsure what the testing implications are. Is that accomplished by the existing PE upgrade test matrices? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5233) puppet inspect is using wrong path for catalog data

2016-03-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-5233 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet inspect is using wrong path for catalog data  
 
 
 
 
 
 
 
 
 
 
Are there release notes for this issue? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6090) Output of iterator type results in unhandled exception

2016-03-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6090 
 
 
 
  Output of iterator type results in unhandled exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 PUP 4.4.1 
 
 
 

Fix Version/s:
 
 PUP 4.4.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6089) type function: Unit type being returned for empty array and hash

2016-03-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6089 
 
 
 
  type function: Unit type being returned for empty array and hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 PUP 4.4.1 
 
 
 

Fix Version/s:
 
 PUP 4.4.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5877) acceptance: puppet class inheritance

2016-03-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5877 
 
 
 
  acceptance: puppet class inheritance  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 PUP 4.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6067) Pip3 provider does not include features from Pip

2016-03-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6067 
 
 
 
  Pip3 provider does not include features from Pip  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Release Notes Summary:
 
 Package provider features were not inherited from the parent provider. This adds features provided by Pip as also provided by Pip3.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-5967) File type links documentation incorrectly references :ignore value

2016-03-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5967 
 
 
 
  File type links documentation incorrectly references :ignore value  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 PUP 4.4.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0

2016-05-23 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6321 
 
 
 
  undef in custom type autorequire value causes error in Puppet 4.5.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Flagged:
 
 Impediment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1409) Facter should continue without locales instead of aborting if they are unavailable

2016-05-23 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1409 
 
 
 
  Facter should continue without locales instead of aborting if they are unavailable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Flagged:
 
 Impediment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6339) Hiera Data in Module give bad results when environment_timeout is unlimited

2016-05-23 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6339 
 
 
 
  Hiera Data in Module give bad results when environment_timeout is unlimited  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Flagged:
 
 Impediment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6238) Serivce SMF should set has_feature :refreshable

2016-05-23 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6238 
 
 
 
  Serivce SMF should set has_feature :refreshable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 PUP 4.5.1 
 
 
 

Fix Version/s:
 
 PUP 4.5.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1415) Replace Facter 3.x Windows Operating System kernel query with Windows Kernel API call RtlGetVersion

2016-05-23 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1415 
 
 
 
  Replace Facter 3.x Windows Operating System kernel query with Windows Kernel API call RtlGetVersion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 FACT 3.1.8 
 
 
 

Fix Version/s:
 
 FACT 3.1.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6336) Quoted string "undef" treated as value undef

2016-05-23 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6336 
 
 
 
  Quoted string "undef" treated as value undef  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Flagged:
 
 Impediment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1381) Facter module not available in at_exit

2016-05-23 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1381 
 
 
 
  Facter module not available in at_exit  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 FACT 3.1.8 
 
 
 

Fix Version/s:
 
 FACT 3.1.9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-05-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-6096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 
 
Solaris 10: 
 
 
 
 
 
 
21:14:00   Begin tests/modules/install/long_path_name.rb 
 
 
 
 
21:14:00
 
 
 
 
21:14:00   puppet module install (long file path) 
 
 
 
 
21:14:00  
 
 
 
 
21:14:00 lkabdtl383cgzo5.delivery.puppetlabs.net (redhat7-64-1) 21:14:00$ puppet module list --render-as pson 
 
 
 
 
21:14:01   {"environment":"production","modules_by_path":{"/etc/puppetlabs/code/environments/production/modules":[],"/etc/puppetlabs/code/modules":[],"/opt/puppetlabs/puppet/modules":[]}} 
 
 
 
 
21:14:01  
 
 
 
 
21:14:01 lkabdtl383cgzo5.delivery.puppetlabs.net (redhat7-64-1) executed in 0.98 seconds 
 
 
 
 
21:14:01  
 
 
 
 
21:14:01 yeyer4h3mgwv9g0.delivery.puppetlabs.net 

Jira (PUP-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-05-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-6096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 
 
cisco-nx-64 on master is also failing with an out of space error: 
 
 
 
 
 
 
20:32:01   Begin tests/modules/install/long_path_name.rb 
 
 
 
 
20:32:01
 
 
 
 
20:32:01   puppet module install (long file path) 
 
 
 
 
20:32:01  
 
 
 
 
20:32:01 h7cfchw5ic1hoxg.delivery.puppetlabs.net (redhat7-64-1) 20:32:01$ puppet module list --render-as pson 
 
 
 
 
20:32:02   {"environment":"production","modules_by_path":{"/etc/puppetlabs/code/environments/production/modules":[],"/etc/puppetlabs/code/modules":[],"/opt/puppetlabs/puppet/modules":[]}} 
 
 
 
 
20:32:02  
 
 
 
 
20:32:02 h7cfchw5ic1hoxg.delivery.puppetlabs.net (redhat7-64-1) executed in 0.86 seconds 
 
 
 
 
20:32:02  
 
 
 
 
20:32:02 

Jira (PUP-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-05-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-6096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 
 
Both cases appear to be bad options to the find on those platforms 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-05-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-6096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 
 
I think this may be failing on a Solaris 10 and Windows 2008: 
https://jenkins.puppetlabs.com/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-stable/120/ 
 
 
 
 
 
 
21:20:56 Begin tests/modules/install/long_path_name.rb 
 
 
 
 
21:20:56  
 
 
 
 
21:20:56 puppet module install (long file path) 
 
 
 
 
21:20:56
 
 
 
 
21:20:56   vhggnmg21mqo9pp.delivery.puppetlabs.net (redhat7-64-1) 21:20:56$ puppet module list --render-as pson 
 
 
 
 
21:20:57 {"environment":"production","modules_by_path":{"/etc/puppetlabs/code/environments/production/modules":[],"/etc/puppetlabs/code/modules":[],"/opt/puppetlabs/puppet/modules":[]}} 
 
 
 
 
21:20:57
 
 
 
 
21:20:57   vhggnmg21mqo9pp.delivery.puppetlabs.net (redhat7-64-1) executed in 0.95 seconds 
 
 
 
 
21:20:57
 
   

Jira (PUP-6298) Puppet component specs failing for linux

2016-05-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6298 
 
 
 
  Puppet component specs failing for linux  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/12 4:38 PM 
 
 
 

Fix Versions:
 

 PUP 4.5.0 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
https://jenkins.puppetlabs.com/job/platform_puppet_unit-ruby_stable/174/ 
 
 
 
 
 
 
16:16:45 Failures: 
 
 
 
 
16:16:45  
 
 
 
 
16:16:45   1) Package provider puppet_gem should be able to get a list of existing packages 
 
 
 
 
   

Jira (PUP-6270) tests/environment/environment_scenario-bad.rb fails on all master platforms

2016-05-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6270 
 
 
 
  tests/environment/environment_scenario-bad.rb fails on all master platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Fix Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6270) tests/environment/environment_scenario-bad.rb fails on all master platforms

2016-05-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6270 
 
 
 
  tests/environment/environment_scenario-bad.rb fails on all master platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Affects Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6270) tests/environment/environment_scenario-bad.rb fails on all master platforms

2016-05-06 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6270 
 
 
 
  tests/environment/environment_scenario-bad.rb fails on all master platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Priority:
 
 Normal Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6478) "Unable to set ownership" error with logdest on agents

2016-07-20 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-6478 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Unable to set ownership" error with logdest on agents  
 
 
 
 
 
 
 
 
 
 
What about the 'non-root' use case? Should Puppet[:user] and Puppet[:group] be able to resolve to the user/group that the process is currently running as if there's not a config defined? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6471) Add toggle to disable symlinks in the file server

2016-07-04 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6471 
 
 
 
  Add toggle to disable symlinks in the file server  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/04 10:26 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
The fileserver functionality of puppet (https://docs.puppet.com/puppet/latest/reference/config_file_fileserver.html) follows symlinks. While this is not an issue in simple deployments, if the fileserver is used to serve files from mixed trust sources; its possible that a symlink was placed under the fileserver's root that references say /. It would then be possible to read arbitrary files as the puppet service, such as private keys and eyaml keys. 
What would be great is a fileserver.conf option to not follow symlinks. This way if the fileserver directory has a mixed trust level, an upstream compromise or other attack won't allow a compromise of puppet itself. For example, puppet's fileserver might be a NFS share mounted from a remote host. With symlinks enabled, puppet now has to fully trust the remote share and the network as NFS is vuln to MITM. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 

Jira (FACT-1450) Test failure on the Ubuntus

2016-07-01 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1450 
 
 
 
  Test failure on the Ubuntus  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  CI Blocker 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/01 11:12 AM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Rob Braden 
 
 
 
 
 
 
 
 
 
 
https://jenkins.puppetlabs.com/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-master/140/ 
After some of the Ubuntu templates were updated, facter tests are failing: 12.04: 
 
 
 
 
 
 
08:26:30   Test Case tests/facts/ubuntu.rb reported: #
 
 
 
 
 
 
 
14.04: 
 
 
 
 
 
 
08:28:29   Test Case tests/facts/ubuntu.rb reported: #
 
 
 
 
 
 
 
  

Jira (PUP-6812) Force --disable flag comment

2016-10-12 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6812 
 
 
 
  Force --disable flag comment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Workflow:
 
 Release Engineering Scrum Teams  Workflow 
 
 
 

Key:
 
 PA PUP - 623 6812 
 
 
 

Project:
 
 Puppet  Agent 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3401) PuppetDB 4.4.0 2017-04-04 Release

2017-04-04 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-3401 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB 4.4.0 2017-04-04 Release  
 
 
 
 
 
 
 
 
 
 
As far as getting on the release calendar, I was going to suggest that your PM/release manager should handle that, but if there's not one... 
I assume it populates from Project Central? https://tickets.puppetlabs.com/browse/PC?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel 
Kenn Hussey or one of the PMs probably has a better idea of how that works. That calendar is what we point to in our weekly status, although we try to call out pending releases (within the next week or two) individually. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3401) PuppetDB 4.4.0 2017-04-04 Release

2017-04-04 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-3401 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PuppetDB 4.4.0 2017-04-04 Release  
 
 
 
 
 
 
 
 
 
 
I'm sure I sound like a broken record, because we bring this up for most PDB releases, but honestly getting less than a day's notice for this really screws up our planning. We ask for a week, typically. Even better, they should be on the release calendar. https://tickets.puppetlabs.com/secure/Dashboard.jspa?selectPageId=11907 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1630) Prepare a gem-only Facter 2.5.0 release

2017-07-17 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  FACT-1630 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prepare a gem-only Facter 2.5.0 release  
 
 
 
 
 
 
 
 
 
 
This is just for the gem, right? Then apt shouldn't be in play at all unless I'm misunderstanding something... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1630) Prepare a gem-only Facter 2.5.0 release

2017-07-17 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  FACT-1630 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prepare a gem-only Facter 2.5.0 release  
 
 
 
 
 
 
 
 
 
 
But yes, those repos have recently moved into the Cloudfront CDN, which doesn't appear to like the double-forward-slash after the host in http://apt.puppetlabs.com//puppetlabs-release-.deb, removing that works properly. Is that in the job? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7976) Puppet agent fights with RPM package over owner/group of certain directories

2017-09-21 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7976 
 
 
 
  Puppet agent fights with RPM package over owner/group of certain directories  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Component/s:
 
 Packaging 
 
 
 

Component/s:
 
 AIO 
 
 
 

Key:
 
 CPR PUP - 222 7976 
 
 
 

Project:
 
 Community Package Repository Puppet 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7989) 404 failure when trying to fetch the latest puppetserver

2017-09-26 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PUP-7989 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 404 failure when trying to fetch the latest puppetserver  
 
 
 
 
 
 
 
 
 
 
I wonder if this corresponds to a nightly ship - do you have a link to the job? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8908) Resource status of "failed_to_restart" is not included in reports for individual resources

2018-06-07 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8908  
 
 
  Resource status of "failed_to_restart" is not included in reports for individual resources   
 

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Priority: 
 Normal Major  
 

  
 
 
 
 

 
 
 

 
 
 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7426) Puppet 5.y Deprecations

2018-06-25 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7426  
 
 
  Puppet 5.y Deprecations   
 

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Sub-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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7426) Puppet 5.y Deprecations

2018-06-25 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7426  
 
 
  Puppet 5.y Deprecations   
 

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Team/s: 
 Coremunity Platform Core  
 

  
 
 
 
 

 
 
 

 
 
 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3638) Work with docs to add new foss platform

2018-01-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3638 
 
 
 
  Work with docs to add new foss platform  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Braden 
 
 
 

Team:
 
 Release Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3638) Work with docs to add new foss platform

2018-01-24 Thread Rob Braden (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Braden commented on  PDB-3638 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Work with docs to add new foss platform  
 
 
 
 
 
 
 
 
 
 
ping Jeff Yarnell - The docs have not yet been updated to list SLES support, but we have been shipping it in Platform 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3832) puppetdb module config.ini mgmt should be in sync with rpm

2018-02-07 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3832  
 
 
  puppetdb module config.ini mgmt should be in sync with rpm   
 

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Team: 
 Release Engineering  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3832) puppetdb module config.ini mgmt should be in sync with rpm

2018-02-07 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden commented on  PDB-3832  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppetdb module config.ini mgmt should be in sync with rpm   
 

  
 
 
 
 

 
 Yep, we can take a look at updating the packages to match  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates

2018-08-01 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8969  
 
 
  Sensitive parameters are not redacted from reports / agent output when used in templates   
 

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Team: 
 Platform Core 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9009) The zypper and rpm providers have duplicate instance lists

2018-08-01 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9009  
 
 
  The zypper and rpm providers have duplicate instance lists   
 

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Sprint: 
 Platform Core Grooming  
 

  
 
 
 
 

 
 
 

 
 
 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9009) The zypper and rpm providers have duplicate instance lists

2018-08-01 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9009  
 
 
  The zypper and rpm providers have duplicate instance lists   
 

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Team: 
 Platform  Core  OS  
 

  
 
 
 
 

 
 
 

 
 
 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


  1   2   3   4   >