date:20160523

Jira (PUP-6345) Configuration reference reports wacky default for hiera_config setting

2016-05-23 Thread Nicholas Fagerlund (JIRA)

Title: Message Title

Nicholas Fagerlund created an issue

Puppet / PUP-6345

Configuration reference reports wacky default for hiera_config setting

Issue Type:

Bug

Assignee:

Unassigned

Created:

2016/05/23 5:42 PM

Priority:

Normal

Reporter:

Nicholas Fagerlund

Docs team relies on puppet doc -r configuration to build the configuration reference. If you run that command with Puppet 4.5, it reports the default location of hiera_config as something like /Users/nick/.puppetlabs/etc/code/hiera.yaml.
a. It should be reporting the default in terms of variables like $confdir, not printing a user-specific path. b. Even $confdir/hiera.yaml isn't the whole story, because of the try-codedir-first behavior to preserve backward compatibility. That kind of dynamic behavior is really hard to introspect, and we rely on being able to introspect.
I think I know how to fix this, but I'm filing it as a real ticket to raise awareness:

When we add dynamic behaviors for auto-documented objects, we also need to make sure we don't break the docs.

Plain old introspection is brittle, and it would be really nice to have a way, in the settings themselves, to provide a descriptive default value. We probably won't get this for oldskool puppet settings, but it'd be nice to take into account for whatever's next. We've been burned by this sort of thing before, in several places.

Jira (PUP-6344) metrics.time.total does not correlate to time reported in log

2016-05-23 Thread Henrik Lindberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6344 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: metrics.time.total does not correlate to time reported in log  
 
 
 
 
 
 
 
 
 
 
This looks familiar to other reported discrepancies in reported profiling data. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)

2016-05-23 Thread Brian Conner (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian Conner commented on  PUP-6334 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)  
 
 
 
 
 
 
 
 
 
 
Thanks all, it now works for CentOS 6 using 
 
 
 
 
 
 
 provider => 'redhat'  
 
 
 
 
 
. Unfortunately, now we're having issues with CentOS 7: 
This error was actually for CloudPassage, I was advised to use iptables originally as that would be something everyone would have. Init had been used because 
 
 
 
 
 
 
 provider => systemd  
 
 
 
 
 
 was acting up when the code was written(Puppet 3.8).  
 
 
 
 
 
 
class cloudpassage::service { 
 
 
 
 
service { "${cloudpassage::params::servicename}" : 
 
 
 
 
ensure => running, 
 
 
 
 
enable => true, 
 
 
 
 
provider   => 'redhat',

Jira (PUP-3852) Switch from PSON to JSON

2016-05-23 Thread Chris Price (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-3852 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Switch from PSON to JSON  
 
 
 
 
 
 
 
 
 
 
Nathaniel Smith it largely is a duplicate of 

PUP-3450
, just created to make sure that we have a separate ticket to track on our agile board vs. the client/language boards. Happy to discuss (maybe IRL) if you feel like it needs more verbiage, but I'm not sure what to change the title to at the moment. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6344) metrics.time.total does not correlate to time reported in log

2016-05-23 Thread Adam Bottchen (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adam Bottchen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6344 
 
 
 
  metrics.time.total does not correlate to time reported in log  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/05/23 4:16 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adam Bottchen 
 
 
 
 
 
 
 
 
 
 
The time reported by a `puppet agent -t` run for "Applied catalog in" does not appear to correlate to the times reported in the Puppet::Util::Metric "time" array. The applied catalog time should be the time used to apply the resources in the catalog, and the times returned to the report processor in the Puppet::Util::Metric "time" array should be the amount of time spent applying each resource, yet the two do not add up. Sometimes the applied catalog line is larger and sometimes the total time is larger. 
 
 
 
 
 
 
# cat lib/puppet/reports/myreport.rb 
 
 
 
 
require 'puppet' 
 
 
 
 
Puppet::Reports.register_report(:myreport) do

1 2 >

1 - 100 of 106 matches

Mail list logo