Jira (PUP-3884) Craft migration/upgrade script for use in the AIO puppet agent

[Branan Purvine-Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Purvine-Riley assigned an issue to Branan Purvine-Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3884 
 
 
 
  Craft migration/upgrade script for use in the AIO puppet agent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Purvine-Riley 
 
 
 

Assignee:
 
 Branan Purvine-Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3884) Craft migration/upgrade script for use in the AIO puppet agent

[Branan Purvine-Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Purvine-Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3884 
 
 
 
  Craft migration/upgrade script for use in the AIO puppet agent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Purvine-Riley 
 
 
 

Issue Type:
 
 Bug Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3982) Ensure puppet service supports conditional restart

[Branan Purvine-Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Purvine-Riley commented on  PUP-3982 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ensure puppet service supports conditional restart  
 
 
 
 
 
 
 
 
 
 
I based this on nate wolfe's branch, but he doesn't want to merge it in (trying to keep his branch focused on just making things work). 
Once his code is merged I'll rebase this and open a PR against puppetlabs master 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3982) Ensure puppet service supports conditional restart

[Branan Purvine-Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Purvine-Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3982 
 
 
 
  Ensure puppet service supports conditional restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Purvine-Riley 
 
 
 

Summary:
 
 Ensure  agent components support  puppet service supports  conditional restart 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3983) Ensure agent components support conditional restart

[Branan Purvine-Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3983 
 
 
 
  Ensure agent components support conditional restart  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 
 Branan Purvine-Riley 
 
 
 

Created:
 

 2015/02/09 11:08 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Matthaus Owens 
 
 
 
 
 
 
 
 
 
 
To ensure clean upgrades, calling conditional restart/try-restart/condrestart in the post will be a better experience. Currently, only puppet and mcollective have services that will need to updated. Debian and redhat support this behavior, I don't know about OSX, solaris, or AIX for this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-3982) Ensure agent components support conditional restart

[Branan Purvine-Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Purvine-Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3982 
 
 
 
  Ensure agent components support conditional restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Purvine-Riley 
 
 
 

Sprint:
 
 Client 2015-02-18 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 










Failures today:


tests/concurrency/ticket_2659_concurrent_catalog_requests.rb Still some sort of classifier failure. Need to investigate further.








> GET /production/catalog/dz1zznczs2t8rz3.delivery.puppetlabs.net HTTP/1.1\13




> User-Agent: curl/7.26.0\13




> Host: k9wmzzbetnq13lx.delivery.puppetlabs.net:8140\13




> Accept: text/pson\13




> \13




* additional stuff not fine transfer.c:1037: 0 0




* HTTP 1.1 or later with persistent connection, pipelining supported




< HTTP/1.1 400 Bad Request\13




< Date: Wed, 29 Oct 2014 10:52:08 GMT\13



  

Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 










tests/reports/submission.rb appears to be failing because it does not wait for puppetdb to finish processing reports before querying it. This can cause an old report to be read if for some reason puppetdb can't quite keep up.












   

 Add Comment











 













 Puppet /  PUP-3277



  Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 







 A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 















 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley updated an issue











 






 Puppet /  PUP-3277



  Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 










Change By:

 Branan Purvine-Riley




Component/s:

 PE












   

 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 










It doesn't look like NC-263 has made it into PE yet. I'll try to get that shepherded through so we can get some cleaner results tonight.












   

 Add Comment











 













 Puppet /  PUP-3277



  Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. 







 A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 















 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 (FACT-649) Backport acceptance setup update for RedHat / Fedora into Facter / master

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Backport acceptance setup update for RedHat / Fedora into Facter / master 










I'm am 97% sure this should be cherry-picked over












   

 Add Comment











 













 Facter /  FACT-649



  Backport acceptance setup update for RedHat / Fedora into Facter / master 







 This commit was lost in the facter-2 / master merge.















 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-894) Too easy to hit "CRL not yet valid for " (and not very informative)

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Too easy to hit "CRL not yet valid for " (and not very informative) 










This hit acceptance testing again last night: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-stable/label=acc-coord,platform=squeeze/514/












   

 Add Comment











 













 Puppet /  PUP-894



  Too easy to hit "CRL not yet valid for " (and not very informative) 







 Currently we set the CRL time range to start at 1 second in the past:   https://github.com/puppetlabs/puppet/blob/a8311df5438601a3394d38e37f671626969d50db/lib/puppet/ssl/certificate_revocation_list.rb#L85   However, this creates a window where an agent with a small amount of clock skew can hit the `CRL not yet valid for ` message. This affects bo...















 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, visi

Jira (PUP-3016) tests/modules/install/with_version.rb assumes `puppet` is on the path

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley created an issue











 






 Puppet /  PUP-3016



  tests/modules/install/with_version.rb assumes `puppet` is on the path 










Issue Type:

  Bug




Assignee:

 Kurt Wall




Created:


 05/Aug/14 2:24 PM




Priority:

  Normal




Reporter:

 Branan Purvine-Riley










tests/modules/install/with_version.rb assumes that the puppet command is on the default PATH. It is not when we are deploying puppet-enterprise (and would not be when we deploy Windows tests using MSIs)
This should use the beaker puppet helper, even though we probably need to fight with it a little to make it work right in this case












   

 Add Comment











 










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




 
 

Jira (PUP-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Version of win32-security expected by puppet master branch is not in puppet-win32-ruby 










Josh Cooper The symptom of this was reported as a potential QE issue in the flakiness ticket. The affect is visible in https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-Per-Commit-master/403/
Inspecting the code deployed to the system in that test run shows version 0.1.4 of the gem, but a version of puppet that rescues a "SystemError" instead of a "Win32::Security::SID::Error".












   

 Add Comment











 













 Puppet /  PUP-2830



  Version of win32-security expected by puppet master branch is not in puppet-win32-ruby 







 Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our {{puppet-win32-security}} repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions.   Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo...















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




 














-- 
You received this message because you are 

Jira (PUP-2830) Version of win32-security expected by puppet master branch is not in puppet-win32-ruby

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley created an issue











 






 Puppet /  PUP-2830



  Version of win32-security expected by puppet master branch is not in puppet-win32-ruby 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 24/Jun/14 12:05 PM




Priority:

  Normal




Reporter:

 Branan Purvine-Riley










Puppet master branch has been updated to expect version 0.2.5 of the win32-security gem. However, the version of the gem included in our puppet-win32-security repo is still 0.1.4. This is causing test failures, since there are some incompatibilities between those versions.
Either puppet needs to be made to expect 0.1.4 again, or the win32-ruby repo needs to be updated to 0.2.5.












   

 Add Comment











 










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


   

Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley updated an issue











 






 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 










Change By:

 Branan Purvine-Riley




Labels:

 impacting-pe-ci pe-ci- puppet_acce puppet_acceptance












   

 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley updated an issue











 






 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 










Change By:

 Branan Purvine-Riley




Labels:

 impacting-pe-ci  pe-ci-puppet_acce












   

 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 (FACT-464) Mandrake osfamily is missing in stable/facter-2

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley updated an issue











 






 Facter /  FACT-464



  Mandrake osfamily is missing in stable/facter-2 










Change By:

 Branan Purvine-Riley




Fix Version/s:

 2.0.2




Fix Version/s:

 2.1












   

 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 (FACT-464) Mandrake osfamily is missing in stable/facter-2

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Mandrake osfamily is missing in stable/facter-2 










Pull request is open against facter-2












   

 Add Comment











 













 Facter /  FACT-464



  Mandrake osfamily is missing in stable/facter-2 







 In master, the osfamily fact returns "Mandrake" for the following operating systems:   - Mandrake  - Mandriva  - Mageia   This is missing for both facter stable (2.0.1) and facter-2 (2.1.0).















 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 (FACT-464) Mandrake osfamily is missing in stable/facter-2

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Mandrake osfamily is missing in stable/facter-2 










The results I am seeing, from a facter checkout:
stable: Mandriva / Linux facter-2: Mandriva / Linux master: RedHat / RedHat (WTF, right?)
This is not the simple backport I thought it would be, but should still be pretty easy to implement... Working on it now 












   

 Add Comment











 













 Facter /  FACT-464



  Mandrake osfamily is missing in stable/facter-2 







 In master, the osfamily fact returns "Mandrake" for the following operating systems:   - Mandrake  - Mandriva  - Mageia   This is missing for both facter stable (2.0.1) and facter-2 (2.1.0).















 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 h

Jira (FACT-197) processorcount counting CPU cores on Solaris

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: processorcount counting CPU cores on Solaris 










I'm just gonna go ahead and open a PR for the backport












   

 Add Comment











 













 Facter /  FACT-197



  processorcount counting CPU cores on Solaris 







 The processorcount fact on Solaris is counting CPU cores   {noformat}  physicalprocessorcount => 1  processor0 => SPARC-T4  processor1 => SPARC-T4  processor2 => SPARC-T4  processor3 => SPARC-T4  processorcount => 1  {noformat}   and on linux it counts CPU threads. This was reported as  http://projects.puppetlabs.com/issues/18215   and a working fix is...















 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 (FACT-197) processorcount counting CPU cores on Solaris

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley assigned an issue to Branan Purvine-Riley











 






 Facter /  FACT-197



  processorcount counting CPU cores on Solaris 










Change By:

 Branan Purvine-Riley




Assignee:

 Eric Sorenson Branan Purvine-Riley












   

 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 (FACT-464) Mandrake osfamily is missing in stable/facter-2

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley assigned an issue to Branan Purvine-Riley











 






 Facter /  FACT-464



  Mandrake osfamily is missing in stable/facter-2 










Change By:

 Branan Purvine-Riley




Assignee:

 Eric Sorenson Branan Purvine-Riley












   

 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 (FACT-464) Mandrake osfamily is missing in stable/facter-2

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Mandrake osfamily is missing in stable/facter-2 










On second thought, this is small enough I can backport this afternoon. If it ends up sitting in a PR for a while so be it.












   

 Add Comment











 













 Facter /  FACT-464



  Mandrake osfamily is missing in stable/facter-2 







 In master, the osfamily fact returns "Mandrake" for the following operating systems:   - Mandrake  - Mandriva  - Mageia   This is missing for both facter stable (2.0.1) and facter-2 (2.1.0).















 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 (FACT-464) Mandrake osfamily is missing in stable/facter-2

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Mandrake osfamily is missing in stable/facter-2 










Eric Sorenson If this indeed works for master, we should consider it for backport to 2.1












   

 Add Comment











 













 Facter /  FACT-464



  Mandrake osfamily is missing in stable/facter-2 







 In master, the osfamily fact returns "Mandrake" for the following operating systems:   - Mandrake  - Mandriva  - Mageia   This is missing for both facter stable (2.0.1) and facter-2 (2.1.0).















 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 (FACT-377) Does not detect LXC virtualization

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Does not detect LXC virtualization 










PR 630 was merged into facter-2 and master. 












   

 Add Comment











 













 Facter /  FACT-377



  Does not detect LXC virtualization 







 Facter does not detect when run in an LXC virtual environment. It reports is_virtual = false and virtual = physical. 















 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 (FACT-377) Does not detect LXC virtualization

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley updated an issue











 






 Facter /  FACT-377



  Does not detect LXC virtualization 










Change By:

 Branan Purvine-Riley




Fix Version/s:

 2.1












   

 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 (FACT-197) processorcount counting CPU cores on Solaris

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: processorcount counting CPU cores on Solaris 










Eric Sorenson, I think this should be considered for backport from master to facter-2. 












   

 Add Comment











 













 Facter /  FACT-197



  processorcount counting CPU cores on Solaris 







 The processorcount fact on Solaris is counting CPU cores   {noformat}  physicalprocessorcount => 1  processor0 => SPARC-T4  processor1 => SPARC-T4  processor2 => SPARC-T4  processor3 => SPARC-T4  processorcount => 1  {noformat}   and on linux it counts CPU threads. This was reported as  http://projects.puppetlabs.com/issues/18215   and a working fix is...















 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Merge puppet 3.6 into pe-puppet 3.3.x 










Kylo Ginsberg I have not seen anything like that when restarting pe-httpd in any other test suites. And it is particularly odd that it is sles-only.












   

 Add Comment











 













 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 







 pe-puppet/3.3.x is based on puppet 3.6.x















 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Merge puppet 3.6 into pe-puppet 3.3.x 










The PMT ones are likely just OPS-3284 still causing us problems.
The SLES service ones look like they could be a socket hold from the kernel preventing the new process from grabbing the socket... but I'd expect apache to use SO_REUSEADDR? Maybe I have too much faith.
I have no idea WTF is up with the autoload ones. Possibly the tests changing config settings in the `with_puppet_running_on` block that breaks basic PE configuration? Those ones deserve more investigation.












   

 Add Comment











 













 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 







 pe-puppet/3.3.x is based on puppet 3.6.x















 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/g

Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Merge puppet 3.6 into pe-puppet 3.3.x 










Awesome, sounds good 












   

 Add Comment











 













 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 







 pe-puppet/3.3.x is based on puppet 3.6.x















 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Merge puppet 3.6 into pe-puppet 3.3.x 










I'm going to guess that the `pe_mcollective` issue is because the master configuration in that test somehow tosses the  {/opt/puppet/share/modules} part of the modulepath.  As for the latter... I don't like that we throw that deprecation warning in PE, since it's for part of our default configuration (the aforementioned {/opt/puppet/share/modules}
 being added to the modulepath). I'm not sure what the decision is on that warning, though.












   

 Add Comment











 













 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 







 pe-puppet/3.3.x is based on puppet 3.6.x















 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Merge puppet 3.6 into pe-puppet 3.3.x 










Kylo Ginsberg Puppet is looking sane in the basic PE integration tests, but the current version of MCO in PE appears to be incompatible. I'm holding off on running more expensive suites until we have that resolved.












   

 Add Comment











 













 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 







 pe-puppet/3.3.x is based on puppet 3.6.x















 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 (PDB-13) Add acceptance tests for platforms with a default ruby of 1.9

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley updated an issue











 






 PuppetDB /  PDB-13



  Add acceptance tests for platforms with a default ruby of 1.9 










Change By:

 Branan Purvine-Riley




Assignee:

 Branan Purvine-Riley












   

 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 (PDB-13) Add acceptance tests for platforms with a default ruby of 1.9

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Add acceptance tests for platforms with a default ruby of 1.9 










I am almost certainly the wrong person for this work. The PDB team largely manages their own CI, and if not them then Roger Ignazio is the QE of choice for FOSS stuff these days. Unassigning from myself, at least for now












   

 Add Comment











 













 PuppetDB /  PDB-13



  Add acceptance tests for platforms with a default ruby of 1.9 







 Currently puppetdb acceptance runs against el5, el6, precise, lucid and squeeze. All of these platforms default to ruby 1.8, which is end of life. precise lucid and squeeze have 1.9 available, but not the default.   If fedora 18, or wheezy, quantal or raring were added to the mix we would have some ruby 1.9 coverage at least.















 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/p

Jira (PUP-1842) Backport Gemfile and whatever other spec fixes are needed to the stdlib 3.2.x branch

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley updated an issue











 






 Puppet /  PUP-1842



  Backport Gemfile and whatever other spec fixes are needed to the stdlib 3.2.x branch 










Change By:

 Branan Purvine-Riley




Summary:

 Backport Gemfile and whatever other spec fixes are needed to the  stdlib  3.2.x branch












   

 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-1842) Backport Gemfile and whatever other spec fixes are needed to the 3.2.x branch

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley created an issue











 






 Puppet /  PUP-1842



  Backport Gemfile and whatever other spec fixes are needed to the 3.2.x branch 










Issue Type:

  Bug




Assignee:

 Branan Purvine-Riley




Created:


 03/Mar/14 5:29 PM




Priority:

  Normal




Reporter:

 Branan Purvine-Riley










Running the spec tests against the 3.2.x branch is currently "hard", since that branch lacks a Gemfile and possibly other fixes (unknown at this time)
Unfortunately, this is the branch of stdlib that is shipped in PE, so we really should be testing it.
In order to make sure that happens, the Gemfile should be backported to the 3.2.x branch.












   

 Add Comment











 










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



 

Jira (PDB-93) duplicate resource collections during catalog compilation

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: duplicate resource collections during catalog compilation 










I've been able to reproduce and somewhat control this with the following manifest:


define sum_series($counter = 0) {
 
  $newcounter = $counter + $title
  if $title == 1 {
notify { "${newcounter}": }
  }
  else {
$dec = $title - 1
$hash = {
  "${dec}"=> {
"counter" => $newcounter,
  },
}
 
create_resources('sum_series', $hash)
  }
}
 
sum_series { '50': }

@@host { "${::hostname}.branan.ec2":
  ip => $::ipaddress
}

Host<<||>>



When this manifest is applied with `puppet agent -t`, 51 (yes, fifty-one. Not a typo) queries to puppetdb are made to collect the Host resources.
If I comment out the "sum_series  { '50': }
" line, a mere 5 queries are made... which is still 5 times as many as I would expect.
In my environment of about 850 nodes, each of these queries takes about 0.1 seconds to complete, which means a good 5s are spent only hitting puppetdb, without counting the decoding and processing of the resources that the master does once it gets them (the extent of which I don't actually know)












   

 Add Comment











 













 PuppetDB /  PDB-93



  duplicate resource collections during catalog compilation 







 While attempting to troubleshoot performance issues with puppetdb, I noticed that during a single catalog compilation, the same resources are trying to be collected multiple times. In my case, what is normally 4 collections turns into 28. This is potentially the source of my performance issue when multiple nodes check in and hammer puppetdb with all these

Jira (PUP-1677) Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley assigned an issue to Branan Purvine-Riley











 






 Puppet /  PUP-1677



  Placeholder for pe-puppet acceptance test changes Brannan has made which we need to pull into stable and pe-puppet 










Change By:

 Branan Purvine-Riley




Assignee:

 Branan Purvine-Riley












   

 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Kenneth Barber So a bit of context: The spec machines were pegged at the vmware level, and I'm not sure the in-VM reporting is necessarily accurate in those cases. 8-core VMs require 8 simultaneously free physical cores in order to be scheduled, which basically slows down the entire ESX scheduler.
They just got moved (or are about to be moved, I'll need to double-check the status) onto additional hardware that has a lower virtual-to-physical ratio, so I'm more comfortable adding the new load of this change.
Re: storage, I am not entirely sure of the details. Something something tuning for our actual workloads. I'm not a storage guy, sorry.












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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




 
   

Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Kenneth Barber Alright, let's go for it. What needs to change on the spec boxes for this to be workable? Are the necessary packages already installed?












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















 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.

Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










At the moment, I'm not sure this is a great idea. I found out recently that our spec machines are already pegged, and are configured in a way that they are impacting the overall health of the cluster (vor does not have this global impact presently). I'm just not super comfortable adding more workload to them until our spec testing deployment is cleaned up.
I absolutely agree that having better control for test scenarios would be awesome, and as soon as I feel we have a solid plan for spec testing machines we can move forward on this.
Scott and Ops have also put a lot of effort into the storage lately, so hopefully in the meantime vor will be healthier as well. If that proves not to be the case we can revisit the prioritization of things to make sure this happens












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















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

   

Jira (PUP-1485) test agent/fallback_to_cached_catalog.rb assumes no master is running by default

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley assigned an issue to Branan Purvine-Riley











 






 Puppet /  PUP-1485



  test agent/fallback_to_cached_catalog.rb assumes no master is running by default 










Change By:

 Branan Purvine-Riley




Assignee:

 Branan Purvine-Riley












   

 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-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










we actually can't decommission vor, we use it for unit testing the dashboard on the PE side of things. Though if this pattern works out we could switch that over as well.
What sorts of faults are you seeing in vor, though? Ideally we want to spend time stabilizing our infra, not working around it.












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















 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 i

Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: PR (802): Convert unit testing to use dynamic postgres instance - kbarber 










Kenneth Barber So Michelle assigned this to QA, but I'm not sure you need me here? What's the status of things? Do you just need a code review? Infra changes to make sure postgres is on your test servers?












   

 Add Comment











 













 PuppetDB /  PDB-312



  PR (802): Convert unit testing to use dynamic postgres instance - kbarber 







 h2. Convert unit testing to use dynamic postgres instance   * Author: Ken Barber   * Company: Puppetlabs Inc.  * Github ID: [kbarber|https://github.com/kbarber]  * [Pull Request 802 Discussion|https://github.com/puppetlabs/puppetdb/pull/802]  * [Pull Request 802 File Diff|https://github.com/puppetlabs/puppetdb/pull/802/files]  h2. Pull Request...















 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 thi

Jira (PUP-1485) test agent/fallback_to_cached_catalog.rb assumes no master is running by default

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: test agent/fallback_to_cached_catalog.rb assumes no master is running by default 










Joshua Cooper That sounds like an even simpler and easier solution. I am all for it












   

 Add Comment











 













 Puppet /  PUP-1485



  test agent/fallback_to_cached_catalog.rb assumes no master is running by default 







 When running the puppet tests against pe, the master is running even outside of a with_puppet_running_on block.   Do we need a "without_puppet_running_on" block in beaker?















 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-1485) test agent/fallback_to_cached_catalog.rb assumes no master is running by default

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley created an issue











 






 Puppet /  PUP-1485



  test agent/fallback_to_cached_catalog.rb assumes no master is running by default 










Issue Type:

  Bug




Assignee:

 Aaron Armstrong




Components:


 PE




Created:


 21/Jan/14 11:52 AM




Priority:

  Normal




Reporter:

 Branan Purvine-Riley










When running the puppet tests against pe, the master is running even outside of a with_puppet_running_on block.
Do we need a "without_puppet_running_on" block in beaker?












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4

Jira (PUP-522) Port final test changes from tmpfosstestsforpe back into puppet.

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Port final test changes from tmpfosstestsforpe back into puppet. 










Joshua Partlow Awesome. Yeah, lets close this out and if I find any newly-introduce compatibility issues in the current FOSS suite run against PE I will ticket those separately (or more likely just fix them)












   

 Add Comment











 













 Puppet /  PUP-522



  Port final test changes from tmpfosstestsforpe back into puppet. 







 There are a few tests that have been added to https://github.com/puppetlabs/tmpfosstestsforpe since we began the testing from packages saga and started the port of pe-puppet acceptance changes back into puppet.   Once we have the current integration/acceptance work merged in, and things are running on the https://jenkins.puppetlabs.com/job/PE-Puppet-Acce...















 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://g

Jira (PUP-522) Port final test changes from tmpfosstestsforpe back into puppet.

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: Port final test changes from tmpfosstestsforpe back into puppet. 










Is there any chance this could get prioritized in the next week or two? PE 3.2 is coming up soon and at this point my options are to run with a suite in tmpfosstestsforpe that is missing the latest updated tests, or run with the suite in pe-puppet that does not have all the tweaks necessary to run properly against PE. Neither of these is super awesome.
If your team can't resolve this soon, a quick write-up of what's needed would at least be great so I can do the heavy lifting.












   

 Add Comment











 













 Puppet /  PUP-522



  Port final test changes from tmpfosstestsforpe back into puppet. 







 There are a few tests that have been added to https://github.com/puppetlabs/tmpfosstestsforpe since we began the testing from packages saga and started the port of pe-puppet acceptance changes back into puppet.   Once we have the current integration/acceptance work merged in, and things are running on the https://jenkins.puppetlabs.com/job/PE-Puppet-Acce...















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




 














-

Jira (MCO-2) mcollective daemon can crash at startup on Windows

[Branan Purvine-Riley (JIRA)]

Title: Message Title










 

 Branan Purvine-Riley commented on an issue











 






  Re: mcollective daemon can crash at startup on Windows 










I've seen no further MCO crashes since PE-1840 was fixed.












   

 Add Comment











 













 MCollective /  MCO-2



  mcollective daemon can crash at startup on Windows 







 This does NOT affect all windows machines, but does seem to hit our test machines with decent regularity.   http://projects.puppetlabs.com/issues/22369 indicated that this could be related to http://projects.puppetlabs.com/issues/20467, but I am not convinced yet.   Tailing the mcollective logs on windows shows that the service does not even initialize ...















 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.