Jira (PDB-2755) (maint) Add acceptance testing to puppetdb-cli

[Andrew Roetker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2755 
 
 
 
  (maint) Add acceptance testing to puppetdb-cli  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Sprint:
 
 Hopper 
 
 
 

Scrum Team:
 
 PuppetDB 
 
 
 

Fix Version/s:
 
 PDB CLI 1.1.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 (PDB-2755) (maint) Add acceptance testing to puppetdb-cli

[gepetto-bot (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2755 
 
 
 
  (maint) Add acceptance testing to puppetdb-cli  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 10:30 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (PDB-2754) (maint) Make master C++ branch 1.0.1

[Andrew Roetker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2754 
 
 
 
  (maint) Make master C++ branch 1.0.1  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Sprint:
 
 Hopper 
 
 
 

Fix Version/s:
 
 PDB CLI 1.0.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 (PDB-2754) (maint) Make master C++ branch 1.0.1

[gepetto-bot (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2754 
 
 
 
  (maint) Make master C++ branch 1.0.1  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 10:20 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
This commit makes the master branch for the C++ code 1.0.1 as it will probably be the last release of the C++ code and contains some bugfixes. This is also the only C++ branch with a pipeline. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6363) The puppet master should accept reports submitted for an environment that doesn't exist

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The puppet master should accept reports submitted for an environment that doesn't exist  
 
 
 
 
 
 
 
 
 
 
Ryan Whitehurst great, thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1924) source function library *before* client sysconfig overrides

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1924 
 
 
 
  source function library *before* client sysconfig overrides  
 
 
 
 
 
 
 
 
 
 
Ping Kylo Ginsberg - reopened earlier fixed ticket, a regression is reported. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[Andrew Roetker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
Looks like the most recent pl-build-tools was fixed per the discussion above and in the PuppetDB channel. 
We now are fixed from a packaging/code perspective and just need to release a 1.0.1 of the client-tools. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6372) Puppet::Transaction#failed? is unused - remove it

[Kylo Ginsberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6372 
 
 
 
  Puppet::Transaction#failed? is unused - remove it  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 4:06 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
The one use of Puppet::Transaction#failed? was removed in https://github.com/puppetlabs/puppet/commit/84be695ddee004d7e358d9256f7929e1a2c400a3, so we can now remove the method itself. 
Note that the entire class is marked as api private. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6363) The puppet master should accept reports submitted for an environment that doesn't exist

[Ryan Whitehurst (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Whitehurst commented on  PUP-6363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The puppet master should accept reports submitted for an environment that doesn't exist  
 
 
 
 
 
 
 
 
 
 
Chris Price Here's the access logs for what I believe is a single full puppet "run" where a node tried to check into an environment that didn't exist: 
 
 
 
 
 
 
10.32.22.221 - - [27/May/2016:14:49:03 -0700] "GET /puppet/v3/node/i-75fd61af?environment=aggregate_rds_check_environment=aggregate_rds_check_uuid=5395921a-b614-4bd4-9255-20ffa54d242c_on_404=true HTTP/1.1" 400 48 "-" "Ruby" 15 
 
 
 
 
10.32.22.221 - - [27/May/2016:14:49:03 -0700] "GET /puppet/v3/file_metadatas/pluginfacts?environment=aggregate_rds_check=follow=true_permissions=use=.svn=CVS=.git_type=md5 HTTP/1.1" 400 48 "-" "Ruby" 15 
 
 
 
 
10.32.22.221 - - [27/May/2016:14:49:03 -0700] "GET /puppet/v3/file_metadata/pluginfacts?environment=aggregate_rds_check=follow_type=md5_permissions=use HTTP/1.1" 400 48 "-" "Ruby" 10 
 
 
 
 
10.32.22.221 - - [27/May/2016:14:49:04 -0700] "GET /puppet/v3/file_metadatas/plugins?environment=aggregate_rds_check=follow=true_permissions=ignore=.svn=CVS=.git_type=md5 HTTP/1.1" 400 48 "-" "Ruby" 10 
 
 
 
 
10.32.22.221 - - [27/May/2016:14:49:04 -0700] "GET /puppet/v3/file_metadata/plugins?environment=aggregate_rds_check=follow_type=md5_permissions=ignore HTTP/1.1" 400 48 "-" "Ruby" 10 
 
 
 
 
10.32.22.221 - - [27/May/2016:14:49:06 -0700] "POST /puppet/v3/catalog/i-75fd61af?environment=aggregate_rds_check HTTP/1.1" 400 48 "-" "Ruby" 38 
 
 
 
 
10.32.22.221 - - [27/May/2016:14:49:06 -0700] "PUT /puppet/v3/report/i-75fd61af?environment=aggregate_rds_check& HTTP/1.1" 400 48 "-" "Ruby" 10
 
 
 

Jira (PUP-6268) Display cert information when interacting with certs via `puppet cert` face

[Nathaniel Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nathaniel Smith commented on  PUP-6268 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Display cert information when interacting with certs via `puppet cert` face  
 
 
 
 
 
 
 
 
 
 
Ok, the outcome of Justin Stoller, Lori Landesman, and my meeting was that we'd prepare a prototype CLI for some internal user testing in the next 1.5 weeks with the following changes: 
 

Showing extension information in the column currently used for alt names
 

hiding hash algorithm and fingerprints behind a verbose flag (--verbose if that's not already in use)
 

Printing a cert's information (just like in cert list) when signing a cert and prompting the user on STDIN for confirmation to sign the cert
 

Recognizing a -I or --non-interactive flag that disables the signing prompt
 

Showing expiry when printing a cert's info
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5926) launchd service provider doesn't implement status override.

[William Hopper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 
 
Thanks Nerissa Lemon! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5926) launchd service provider doesn't implement status override.

[Nerissa Lemon (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nerissa Lemon commented on  PUP-5926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 
 
William Hopper Whoops, turns out I had included provider => systemd, which does not belong there.  
So:  Validated using puppet-agent at sha dc601a5c7 containing puppet at sha d68f622 on OSX10.11 and Redhat7. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6371) Could not find class x

[Michael Stahnke (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Stahnke moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6371 
 
 
 
  Could not find class x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Stahnke 
 
 
 

Workflow:
 
 Release Engineering Scrum Teams  Workflow 
 
 
 

Key:
 
 PA PUP - 366 6371 
 
 
 

Project:
 
 Puppet  Agent 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6370) systemd provider does not honor documented enabled states

[Emilien Macchi (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Emilien Macchi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6370 
 
 
 
  systemd provider does not honor documented enabled states  
 
 
 
 
 
 
 
 
 

Change By:
 
 Emilien Macchi 
 
 
 
 
 
 
 
 
 
 The systemd provider considers  to  too  many states as "disabled" and should probably just simply track the return value of "is-enabled" instead of capturing stdout and comparing it to a static list of knows states.  This has the added benefit of us not having to externally track new states added to systemd over time.This issue was found in puppet-nova's CI where we found that the virtlockd and virtlogd services attempt to be enabled on every run; their "is-enabled" state is "indirect".https://www.freedesktop.org/software/systemd/man/systemctl.htmlhttp://logs.openstack.org/30/308530/24/experimental/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/e209217/console.html#_2016-05-26_22_48_06_290 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6370) systemd provider does not honor documented enabled states

[Cody Herriges (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cody Herriges created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6370 
 
 
 
  systemd provider does not honor documented enabled states  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.5.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 1:32 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Cody Herriges 
 
 
 
 
 
 
 
 
 
 
The systemd provider considers to many states as "disabled" and should probably just simply track the return value of "is-enabled" instead of capturing stdout and comparing it to a static list of knows states. This has the added benefit of us not having to externally track new states added to systemd over time. 
This issue was found in puppet-nova's CI where we found that the virtlockd and virtlogd services attempt to be enabled on every run; their "is-enabled" state is "indirect". 
https://www.freedesktop.org/software/systemd/man/systemctl.html http://logs.openstack.org/30/308530/24/experimental/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial/e209217/console.html#_2016-05-26_22_48_06_290 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
  

Jira (PUP-5926) launchd service provider doesn't implement status override.

[Nerissa Lemon (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nerissa Lemon assigned an issue to Nerissa Lemon 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5926 
 
 
 
  launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nerissa Lemon 
 
 
 

Assignee:
 
 qa Nerissa Lemon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5926) launchd service provider doesn't implement status override.

[William Hopper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5926 
 
 
 
  launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Status:
 
 Needs Information Ready for Test 
 
 
 

Assignee:
 
 William Hopper qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6366) trusted facts with apache/nginx and puppetmaster unicorn

[Sebastian Reitenbach (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastian Reitenbach commented on  PUP-6366 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trusted facts with apache/nginx and puppetmaster unicorn  
 
 
 
 
 
 
 
 
 
 
Alright, did the PR against 3.x branch, see https://github.com/puppetlabs/puppet/pull/4997 
I you prefer against master or stable, let me know, and I'll create other PR. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5926) launchd service provider doesn't implement status override.

[William Hopper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 
 
Nerissa Lemon I'm not sure where the systemd provider is coming from on OSX10.11 - could you paste the test manifest you're using and the output of puppet apply with the --debug flag? 
For me, the following is successful on OSX 10.11: 
 
 
 
 
 
 
service { 'fake_service': 
 
 
 
 
ensure => running, 
 
 
 
 
start => '/bin/echo start command', 
 
 
 
 
status => '/usr/bin/true', 
 
 
 
 
hasstatus => false, 
 
 
 
 
}
 
 
 
 
 
 
 
Note that in OSX, /usr/bin/true is the location of true, not /bin/true like other linuxes.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

Jira (PUP-6366) trusted facts with apache/nginx and puppetmaster unicorn

[Sebastian Reitenbach (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastian Reitenbach commented on  PUP-6366 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trusted facts with apache/nginx and puppetmaster unicorn  
 
 
 
 
 
 
 
 
 
 
I'm aware that the 3.8 is kind of not "state of the art" anymore. But there is no puppet-server package for OpenBSD yet, so that's what I use  answering here for both tickets, it's the 3.x branch to where to do the PR against? 
BTW: just commited this fix, and the one to PUP-6365 to OpenBSD ports tree puppet port/package. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5926) launchd service provider doesn't implement status override.

[Nerissa Lemon (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nerissa Lemon commented on  PUP-5926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 
 
Failed using puppet-agent at sha dc601a5c7} containing {{puppet at sha d68f622 on OSX 10.11. 
On OSX 10.11, the test manifests triggers a default provider of systemd, which does not exist on this platform.  
 
 
 
 
 
 
Info: Applying configuration version '1464375377' 
 
 
 
 
Debug: Puppet::Type::Service::ProviderSystemd: file systemctl does not exist 
 
 
 
 
Debug: Puppet::Type::Service::ProviderSystemd: file systemctl does not exist 
 
 
 
 
Error: /Stage[main]/Main/Service[fake_service]: Provider systemd is not functional on this host
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-5926) launchd service provider doesn't implement status override.

[Nerissa Lemon (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nerissa Lemon assigned an issue to William Hopper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5926 
 
 
 
  launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nerissa Lemon 
 
 
 

Assignee:
 
 Nerissa Lemon William Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6354) Enum entries are not unique.

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6354 
 
 
 
  Enum entries are not unique.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Fix Version/s:
 
 PUP 4.5.2 
 
 
 

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-6354) Enum entries are not unique.

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin commented on  PUP-6354 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enum entries are not unique.  
 
 
 
 
 
 
 
 
 
 
Low risk, covered by unit test. Passed CI.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6354) Enum entries are not unique.

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6354 
 
 
 
  Enum entries are not unique.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6354) Enum entries are not unique.

[Sean Griffin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6354 
 
 
 
  Enum entries are not unique.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

QA Risk Assessment Reason:
 
 Covered by unit test 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5926) launchd service provider doesn't implement status override.

[Nerissa Lemon (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nerissa Lemon assigned an issue to Nerissa Lemon 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5926 
 
 
 
  launchd service provider doesn't implement status override.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nerissa Lemon 
 
 
 

Assignee:
 
 Nerissa Lemon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1408) Facter productname issue on Solaris

[Nerissa Lemon (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nerissa Lemon commented on  FACT-1408 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter productname issue on Solaris  
 
 
 
 
 
 
 
 
 
 
Validated using puppet-agent at sha ab8106c06 containing facter at sha 148948d on Solaris 11-sparc ldom. 
 
 
 
 
 
 
root@sol11:~# /opt/puppetlabs/bin/facter -p productname 
 
 
 
 
SPARC Enterprise T5120 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1408) Facter productname issue on Solaris

[Steve Barlow (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Barlow updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1408 
 
 
 
  Facter productname issue on Solaris  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steve Barlow 
 
 
 

Fix Version/s:
 
 FACT 3.1.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
That order still looks wrong. -fPIC -pthread -I/opt/puppetlabs/puppet/include -I/include is the bit that makes me question your toolchain file. 
If you updated, did you rebuild in the same environment? To use the new toolchain file, you'll have to wipe out your previous CMake configuration (CMakeCache.txt and CMakeFiles). If not, then take a look at the toolchain file and see if it's really changed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[Andrew Roetker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
Michael Smith 
 
 
 
 
 
 
make[3]: Nothing to be done for `CMakeFiles/translations.dir/build'. 
 
 
 
 
make[3]: Leaving directory `/var/tmp/tmp.gE4I3Ar7HS/leatherman/build' 
 
 
 
 
/opt/pl-build-tools/bin/cmake -E cmake_progress_report /var/tmp/tmp.gE4I3Ar7HS/leatherman/build/CMakeFiles 
 
 
 
 
[ 53%] Built target translations 
 
 
 
 
/opt/pl-build-tools/bin/cmake -E cmake_progress_report /var/tmp/tmp.gE4I3Ar7HS/leatherman/build/CMakeFiles 17 
 
 
 
 
[ 55%] Building CXX object ruby/CMakeFiles/leatherman_ruby.dir/src/posix/api.cc.o 
 
 
 
 
cd /var/tmp/tmp.gE4I3Ar7HS/leatherman/build/ruby && /opt/pl-build-tools/bin/g++   -DBOOST_LOG_WITHOUT_WCHAR_T -DBOOST_SYSTEM_NO_DEPRECATED -DLEATHERMAN_LOCALE_INSTALL=\"/opt/puppetlabs/client/tools/share/locale\" -DLEATHERMAN_LOGGING_LINE_NUMBERS -DLEATHERMAN_LOGGING_NAMESPACE=\"leatherman.ruby\" -DLEATHERMAN_USE_LOCALES -DPROJECT_DIR=\"/var/tmp/tmp.gE4I3Ar7HS/leatherman/build\" -DPROJECT_NAME=\"leatherman\" -fPIC -pthread -I/opt/puppetlabs/puppet/include -I/include -fPIC -pthread -I/opt/puppetlabs/puppet/include -I/include  -fPIC -pthread -I/opt/puppetlabs/puppet/include -I/include   -Wno-maybe-uninitialized -O3 -DNDEBUG -I/var/tmp/tmp.gE4I3Ar7HS/leatherman/file_util/inc -I/var/tmp/tmp.gE4I3Ar7HS/leatherman/execution/inc -I/var/tmp/tmp.gE4I3Ar7HS/leatherman/util/inc -I/var/tmp/tmp.gE4I3Ar7HS/leatherman/locale/inc -I/var/tmp/tmp.gE4I3Ar7HS/leatherman/nowide/../vendor/nowide/include -I/var/tmp/tmp.gE4I3Ar7HS/leatherman/nowide/inc -I/opt/pl-build-tools/include -I/var/tmp/tmp.gE4I3Ar7HS/leatherman/logging/inc 

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

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
Try make VERBOSE=1. It looks like you might still be picking up the wrong Leatherman headers, but not clear why. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[Andrew Roetker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
This could have been a different update Rob Braden we haven't touched the C++ code/packaging since the 1.0.0 release of client-tools 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

[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

[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

[Andrew Roetker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker commented on  PDB-2748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet-client-tools 1.0.0 and puppet-agent >=1.5 are broken  
 
 
 
 
 
 
 
 
 
 
Looks like leatherman (0.4.2) is failing to build with the pl-build-tools update 
 
 
 
 
 
 
bundle exec build puppet-client-tools el-7-x86_64
 
 
 
 
 
 
 
 
 
 
 
 
 
make[3]: Entering directory `/var/tmp/tmp.rQ55kQ4s7P/leatherman/build' 
 
 
 
 
[ 55%] Building CXX object ruby/CMakeFiles/leatherman_ruby.dir/src/api.cc.o 
 
 
 
 
/var/tmp/tmp.rQ55kQ4s7P/leatherman/execution/src/posix/execution.cc: In function 'leatherman::execution::result leatherman::execution::execute(const string&, const std::vector*, const string*, const std::map*, const std::function&, const std::function&, const std::function&, const leatherman::util::option_set&, uint32_t)': 
 
 
 
 
/var/tmp/tmp.rQ55kQ4s7P/leatherman/execution/src/posix/execution.cc:417:39: error: could not convert '{false, "", "", 127}' from '' to 'leatherman::execution::result' 
 
 
 
 
 return {false, "", "", 127}; 
 
 
 
 
   ^ 
 
 

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

[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 (PDB-2753) Use noop_status field from puppet agent report

[Karel Brezina (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karel Brezina created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2753 
 
 
 
  Use noop_status field from puppet agent report  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 9:27 AM 
 
 
 

Labels:
 

 SystemInsights-Dep 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Karel Brezina 
 
 
 
 
 
 
 
 
 
 
The field reflects result of noop puppet run. 
Possible values: 
 

"changed" (noop run + out-of-sync),
 

"unchanged" (noop run + in-sync),
 

"failed" (noop run + failure),
 

nil (enforcement puppet run).
 
 
This field needs to be queryable from both reports and nodes entity. 
 
 
 
 
 
 
 
 
 
 
   

Jira (PDB-2495) Use real 'noop' status from puppet agent report, when it has the feature to do this

[Karel Brezina (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karel Brezina updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2495 
 
 
 
  Use real 'noop' status from puppet agent report, when it has the feature to do this  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karel Brezina 
 
 
 

Labels:
 
 SystemInsights-Dep 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5216) Add Password Expiration for Windows User management

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes assigned an issue to Daniel Lu 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5216 
 
 
 
  Add Password Expiration for Windows User management   
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Assignee:
 
 Daniel Lu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3768) scheduled_task keeps reapplying

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes assigned an issue to Daniel Lu 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3768 
 
 
 
  scheduled_task keeps reapplying  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Assignee:
 
 Daniel Lu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3768) scheduled_task keeps reapplying

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3768 
 
 
 
  scheduled_task keeps reapplying  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Labels:
 
 scheduled_task windows  wintern 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2788) Puppet package source check fails with DFS share

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2788 
 
 
 
  Puppet package source check fails with DFS share  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Labels:
 
 windows  wintern 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5823) Puppet agent with splay on windows begets random interval between runs

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes assigned an issue to Daniel Lu 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5823 
 
 
 
  Puppet agent with splay on windows begets random interval between runs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Assignee:
 
 Daniel Lu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5216) Add Password Expiration for Windows User management

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5216 
 
 
 
  Add Password Expiration for Windows User management   
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Labels:
 
 wintern 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5823) Puppet agent with splay on windows begets random interval between runs

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5823 
 
 
 
  Puppet agent with splay on windows begets random interval between runs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Labels:
 
 windows  wintern 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6369) Add new noop_status field to puppet report

[Karel Brezina (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karel Brezina commented on  PUP-6369 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add new noop_status field to puppet report  
 
 
 
 
 
 
 
 
 
 
ping Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6363) The puppet master should accept reports submitted for an environment that doesn't exist

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6363 
 
 
 
  The puppet master should accept reports submitted for an environment that doesn't exist  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Scrum Team:
 
 Puppet Server 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6369) Add new noop_status field to puppet report

[Karel Brezina (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karel Brezina created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6369 
 
 
 
  Add new noop_status field to puppet report  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 8:51 AM 
 
 
 

Labels:
 

 SystemInsights-Dep noop 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Karel Brezina 
 
 
 
 
 
 
 
 
 
 
The field will reflect result of noop puppet run. 
Possible values: 
 

"changed" (noop run + out-of-sync),
 

"unchanged" (noop run + in-sync),
 

"failed" (noop run + failure),
 

nil (enforcement puppet run).
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 

Jira (PUP-6369) Add new noop_status field to puppet report

[Karel Brezina (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karel Brezina assigned an issue to Karel Brezina 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6369 
 
 
 
  Add new noop_status field to puppet report  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karel Brezina 
 
 
 

Assignee:
 
 Karel Brezina 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6294) Add a proper 'noop' status to the report output

[Steve Quin (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Quin commented on  PUP-6294 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a proper 'noop' status to the report output  
 
 
 
 
 
 
 
 
 
 
Hey Karel Is the proposed solution for the PUP ticket been signed of by the stakeholders? 
Steve 
On Fri, May 27, 2016 at 4:46 PM Karel Brezina (JIRA) < 
–  
Regards Steve 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2752) puppet-client-tools package for Xenial is missing

[Andrew Roetker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2752 
 
 
 
  puppet-client-tools package for Xenial is missing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Roetker 
 
 
 

Affects Version/s:
 
 PDB CLI 1.0.0 
 
 
 

Sprint:
 
 Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6368) Semantic::VersionRange creates incorrect range for <= version

[Thomas Hallgren (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6368 
 
 
 
  Semantic::VersionRange creates incorrect range for <= version  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 8:40 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
Creating a SemanticPuppet::VersionRange from the string '<=1.2.3' results in the range: 
 
 
 
 
 
 
0.0.0...1.2.4- # first pre-release of 1.2.4. There is no proper string format for it
 
 
 
 
 
 
 
This is incorrect even if 3 dots means exclude end, since that range, when converted to a String, becomes "<1.2.4". The correct range should be: 
 
 
 
 
 
 
0.0.0..1.2.3
 
 
 
 
 
 
 
  

Jira (FACT-1426) Triage acceptance failures on zlinux (s390x) sles-11

[Kenn Hussey (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1426 
 
 
 
  Triage acceptance failures on zlinux (s390x) sles-11  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

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-6358) Set strict_variables = true, if strict = error is set

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6358 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Set strict_variables = true, if strict = error is set  
 
 
 
 
 
 
 
 
 
 
The proposal is not backwards compatible. We are going to leave it as it is in the current implementation even if the combination of the two strictness options is not ideal. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6294) Add a proper 'noop' status to the report output

[Karel Brezina (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karel Brezina assigned an issue to Karel Brezina 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6294 
 
 
 
  Add a proper 'noop' status to the report output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karel Brezina 
 
 
 

Assignee:
 
 Karel Brezina 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6366) trusted facts with apache/nginx and puppetmaster unicorn

[Kylo Ginsberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-6366 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trusted facts with apache/nginx and puppetmaster unicorn  
 
 
 
 
 
 
 
 
 
 
Sebastian Reitenbach similar to my comment on PUP-6365: if you'd like to work through getting your patch rolled into core, please submit a pull request at https://github.com/puppetlabs/puppet. 
That said, please note that the deprecated server functionality - https://docs.puppet.com/puppet/4.1/reference/deprecated_servers.html - won't be available as of the next puppet major release (though that release is not scheduled as I write), which may affect this use. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6365) trusted facts not available when running "puppet master" webrick server

[Kylo Ginsberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-6365 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trusted facts not available when running "puppet master" webrick server  
 
 
 
 
 
 
 
 
 
 
Sebastian Reitenbach if you'd like to work through getting your patch rolled into core, please submit a pull request at https://github.com/puppetlabs/puppet. 
That said, please note that webrick is deprecated: https://docs.puppet.com/puppet/4.1/reference/deprecated_servers.html, and so won't be available as of the next puppet major release (though that release is not scheduled as I write). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6363) The puppet master should accept reports submitted for an environment that doesn't exist

[Kylo Ginsberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-6363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The puppet master should accept reports submitted for an environment that doesn't exist  
 
 
 
 
 
 
 
 
 
 
Chris Price +1 on putting this into server team's triage list.  
As a side note, this might tie into the ideas being kicked around for a report-endpoint-specific jruby and/or for adding the concept of a report-processor-specific module. That said, I know those ideas are likely a bit further out so if there's a shorter path than that to adding this feature, I'd still be for it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6365) trusted facts not available when running "puppet master" webrick server

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6365 
 
 
 
  trusted facts not available when running "puppet master" webrick server  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2752) puppet-client-tools package for Xenial is missing

[Gareth Rushgrove (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gareth Rushgrove created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2752 
 
 
 
  puppet-client-tools package for Xenial is missing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 7:22 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Gareth Rushgrove 
 
 
 
 
 
 
 
 
 
 
As per conversation with Ryan Senior 
While following the documentation https://docs.puppet.com/puppetdb/latest/pdb_client_tools.html to install the puppet-client-tools, in order to use the new puppet query feature I hit a snag: 
 
 
 
 
 
 
Unable to locate package puppet-client-tools
 
 
 
 
 
 
 
I'm running on Ubuntu Xenial, which we've just started shipping agent support for. Xenial is supported in the next PE release I believe. 
It looks like puppet-client-tools packages haven't made it to the xenial package repos yet. 
 
 
 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-6366) trusted facts with apache/nginx and puppetmaster unicorn

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6366 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trusted facts with apache/nginx and puppetmaster unicorn  
 
 
 
 
 
 
 
 
 
 
Ping @kylo and Chris Price 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6365) trusted facts not available when running "puppet master" webrick server

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6365 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trusted facts not available when running "puppet master" webrick server  
 
 
 
 
 
 
 
 
 
 
Ping Kylo Ginsberg and Chris Price 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6367) Semantic::VersionRange creates incorrect range for exact version

[Thomas Hallgren (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6367 
 
 
 
  Semantic::VersionRange creates incorrect range for exact version  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/27 6:27 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
Creating a SemanticPuppet::VersionRange from the string '1.2.3' results in the range: 
 
 
 
 
 
 
1.2.3...1.2.4
 
 
 
 
 
 
 
This is incorrect even if 3 dots means exclude end, since that range includes all prebuild releases between 1.2.4-nnn to the final release 1.2.4. The correct exact range should be: 
 
 
 
 
 
 
1.2.3..1.2.3
 
 
 
 
 
 
 

Jira (PUP-6363) The puppet master should accept reports submitted for an environment that doesn't exist

[Chris Price (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6363 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The puppet master should accept reports submitted for an environment that doesn't exist  
 
 
 
 
 
 
 
 
 
 
I think I agree with the spirit of this ticket. 
My guess is that the only tricky part about implementing this will be that the environment validation is in the indirector and it is generalized across all request types, so it might be tricky to figure out how to special-case the report requests. Worth looking into, though. 
Kylo Ginsberg I don't mind putting this onto the server team's triage list if you think it's appropriate. 
Ryan Whitehurst Do you have log output from a case where this happened? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1924) source function library *before* client sysconfig overrides

[Robin Bowes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1924 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: source function library *before* client sysconfig overrides  
 
 
 
 
 
 
 
 
 
 
pe-puppet 3.8.7 delivers an init file with the following content: 
 
 
 
 
 
 
#!/bin/bash 
 
 
 
 
# puppetInit script for running the puppet client daemon 
 
 
 
 
# 
 
 
 
 
# Author:   Duane Griffin  
 
 
 
 
#   David Lutterkort  
 
 
 
 
# 
 
 
 
 
# chkconfig: 2345 98 02 
 
 
 
 
# 
 
 
 
 
# description: Enables periodic system configuration checks through puppet. 
 
 
 
 
# processname: puppet 
 
 
 
 
  

Jira (PUP-1924) source function library *before* client sysconfig overrides

[Robin Bowes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-1924 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: source function library *before* client sysconfig overrides  
 
 
 
 
 
 
 
 
 
 
This appears to have regressed, at least in PE 3.8.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1428) FreeBSD facts are missing from Facter 3.X onwards

[Peter Souter (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1428 
 
 
 
  FreeBSD facts are missing from Facter 3.X onwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 
 
 
 
 
 
 
 Some are kinda expected, some are pretty worrying (no FQDN? :[ )architectureaugeasversionaugeasversionbios_release_datebios_vendorbios_versionboardmanufacturerboardproductnameboardserialnumberdomainfqdngidgidhardwareisahardwaremodelhostnameidinterfacesipaddressipaddress_em0ipaddress_lo0ipaddress_re0is_virtualmacaddressmacaddress_em0macaddress_re0macaddress_xl0manufacturermemoryfreememoryfree_mbmemorysizememorysize_mbmtu_em0mtu_lo0mtu_re0mtu_xl0netmasknetmask_em0netmask_lo0netmask_re0network_em0network_lo0network_re0processorprocessorcountprocessorsproductnamepspuppetversionrubyplatformrubysitedirrubyversionserialnumbersshdsakeysshecdsakeysshed25519keysshfp_dsasshfp_ecdsasshfp_ed25519sshfp_rsasshrsakeyswapfreeswapsizetype uptimeuptime_daysuptime_hoursuptime_seconds uuidvirtualzfs_versionzpool_version 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1428) FreeBSD facts are missing from Facter 3.X onwards

[Peter Souter (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1428 
 
 
 
  FreeBSD facts are missing from Facter 3.X onwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 
 
 
 
 
 
 
 Some are kinda expected, some are pretty worrying (no FQDN? :[ )architectureaugeasversionaugeasversionbios_release_datebios_vendorbios_versionboardmanufacturerboardproductnameboardserialnumberdomainfqdngidgidhardwareisahardwaremodelhostnameidinterfacesipaddressipaddress_em0ipaddress_lo0ipaddress_re0is_virtualmacaddressmacaddress_em0macaddress_re0macaddress_xl0manufacturermemoryfreememoryfree_mbmemorysizememorysize_mbmtu_em0mtu_lo0mtu_re0mtu_xl0netmasknetmask_em0netmask_lo0netmask_re0network_em0network_lo0network_re0 osfamily processorprocessorcountprocessorsproductnamepspuppetversionrubyplatformrubysitedirrubyversionserialnumbersshdsakeysshecdsakeysshed25519keysshfp_dsasshfp_ecdsasshfp_ed25519sshfp_rsasshrsakeyswapfreeswapsizetypeuptimeuptime_daysuptime_hoursuptime_secondsuuidvirtualzfs_versionzpool_version 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1428) FreeBSD facts are missing from Facter 3.X onwards

[Peter Souter (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter commented on  FACT-1428 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: FreeBSD facts are missing from Facter 3.X onwards  
 
 
 
 
 
 
 
 
 
 
Ok, so since FreeBSD uses kenv to get a lot of system settings, it would be ideal to use that for FreeBSD stuff. 
But we'll need to import #include  for FreeBSD, not sure how to add that to the build steps... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6366) trusted facts with apache/nginx and puppetmaster unicorn

[Sebastian Reitenbach (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastian Reitenbach created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6366 
 
 
 
  trusted facts with apache/nginx and puppetmaster unicorn  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 

Attachments:
 

 puppet_unicorn.diff 
 
 
 

Components:
 

 Networking Services 
 
 
 

Created:
 

 2016/05/27 3:29 AM 
 
 
 

Environment:
 
 
node and master OpenBSD 6.0-beta, puppet 3.8.7, ruby 2.2.4, nginx-1.10.0, gunicorn 5.0.1 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sebastian Reitenbach 
 
 
 
 
 
 
 
 
 
 
I have gunicorn running behind nginx, but want to make use of trusted facts, but that doesn't seem to work out of the box. 
Some debugging, I found the lib/puppet/network/http/rack/rest.rb, esp. the +ExportCertData comment in it. This is only 

Jira (PUP-6365) trusted facts not available when running "puppet master" webrick server

[Sebastian Reitenbach (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastian Reitenbach created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6365 
 
 
 
  trusted facts not available when running "puppet master" webrick server  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 

Attachments:
 

 puppet_webrick.diff 
 
 
 

Components:
 

 Networking Services 
 
 
 

Created:
 

 2016/05/27 2:56 AM 
 
 
 

Environment:
 
 
nodes and master are on: 
 

OpenBSD 6.0-beta, Puppet 3.8.7, ruby 2.2.4
 
 
 
 
 

Labels:
 

 trusted facts 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sebastian Reitenbach 
 
 

Jira (PUP-6354) Enum entries are not unique.

[Thomas Hallgren (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6354 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enum entries are not unique.  
 
 
 
 
 
 
 
 
 
 
Merged to stable at 529bdb4 and onward to master at eb4627a. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.