Jira (FACT-620) windows facter $::osfamily and $::kernel output inconsistent output

[Geoff Williams (JIRA)]

Title: Message Title










 

 Geoff Williams created an issue











 






 Facter /  FACT-620



  windows facter $::osfamily and $::kernel output inconsistent output 










Issue Type:

  Bug




Affects Versions:


 1.7.5




Assignee:

 Eric Sorenson




Created:


 08/Jul/14 9:09 PM




Environment:


windows




Priority:

  Normal




Reporter:

 Geoff Williams










Output from facter for $::osfamily and $::kernel is inconsistent vs output on other platforms.
I get 'windows' instead of 'Windows' as the output.
Other platforms give outputs such as 'Solaris' or 'RedHat' because programmers and customers picking up this fact will naturally expect its output to be consistent with other platforms.
Today this has led to bug MODULES-1203 (PR merged) which broke the concat module for our windows users - I'm concerned that we will see this problem come up time after time and also that it will impact our customers - eg if they use regexps. Would be great if this could be addressed to improve consistency
Cheers,

Jira (FACT-620) windows facter $::osfamily and $::kernel output inconsistent vs other platforms

[Geoff Williams (JIRA)]

Title: Message Title










 

 Geoff Williams updated an issue











 






 Facter /  FACT-620



  windows facter $::osfamily and $::kernel output inconsistent vs other platforms 










Change By:

 Geoff Williams




Summary:

 windows facter $::osfamily and $::kernel output inconsistent  output  vs other platforms












   

 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-2939) puppet (enterprise) doesn't restart web server after doing a "ca revoke"

[Geoff Williams (JIRA)]

Title: Message Title










 

 Geoff Williams created an issue











 






 Puppet /  PUP-2939



  puppet (enterprise) doesn't restart web server after doing a "ca revoke" 










Issue Type:

  Bug




Affects Versions:


 3.2.3




Assignee:

 Geoff Williams




Created:


 15/Jul/14 9:41 PM




Environment:


linux/puppet-enterprise




Priority:

  Normal




Reporter:

 Geoff Williams










Very very occasionally someone will have an emergency and need to revoke a certificate with "puppet ca revoke".
On this day, I guarantee that they will forget to also restart apache, leaving this person open to attack.
In today's last ever puppet advanced course we taught students to restart apache after doing a revoke – lets make their lives easier by doing something like:
PE: After revoking certificate we will restart pe-httpd (graceful or reload to prevent killing active connections)
OSS After revoking certificate, print a message along the lines of "don't forget to restart your web server"











 

Jira (PUP-2939) puppet (enterprise) doesn't restart web server after doing a "ca revoke"

[Geoff Williams (JIRA)]

Title: Message Title










 

 Geoff Williams commented on an issue











 






  Re: puppet (enterprise) doesn't restart web server after doing a "ca revoke" 










Initial research identifies this code should go in the file:
/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/ssl/certificate_revocation_list.rb
in the revoke() method ~line 62
Will get to work on a PR during my no travel week












   

 Add Comment











 













 Puppet /  PUP-2939



  puppet (enterprise) doesn't restart web server after doing a "ca revoke" 







 Very very occasionally someone will have an emergency and need to revoke a certificate with "puppet ca revoke".   On this day, I guarantee that they will forget to also restart apache, leaving this person open to attack.   In today's last ever puppet advanced course we taught students to restart apache after doing a revoke -- lets make their lives easie...















 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

Jira (PUP-2939) puppet (enterprise) doesn't restart web server after doing a "ca revoke"

[Geoff Williams (JIRA)]

Title: Message Title










 

 Geoff Williams commented on an issue











 






  Re: puppet (enterprise) doesn't restart web server after doing a "ca revoke" 










spec tests ~line 90 ./spec/unit/indirector/ssl_file_spec.rb












   

 Add Comment











 













 Puppet /  PUP-2939



  puppet (enterprise) doesn't restart web server after doing a "ca revoke" 







 Very very occasionally someone will have an emergency and need to revoke a certificate with "puppet ca revoke".   On this day, I guarantee that they will forget to also restart apache, leaving this person open to attack.   In today's last ever puppet advanced course we taught students to restart apache after doing a revoke -- lets make their lives easie...















 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-8395) Exec Parity for Windows

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-8395 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exec Parity for Windows  
 
 
 
 
 
 
 
 
 
 
Correct me if I'm wrong but in my quick look at this the ruby linked code doesn't look like it actually does anything to control the ID running the installer: 
 
 
 
 
 
 
if FEATURE_RESERVED_SWITCHES.include? k 
 
 
 
 
  warn("Reserved switch [#{k}] found for `install_switches`, please know the provided value may be overridden by some command line arguments") 
 
 
 
 
end
 
 
 
 
 
 
 
see: https://github.com/puppetlabs/puppetlabs-sqlserver/blob/master/lib/puppet/provider/sqlserver_features/mssql.rb#L96 
This would just print a warning that some options may be ignored (or they may not...) - because it depends on the ID who owns the Puppet process. The above options then get written to a configuration file which is fed to the SQL installer and it is that, not puppet, which performs the ID change. 
Writing a custom ruby provider while fun, is not a means that can be leveraged to change users if puppet is not being run as a user who is able to switch IDs according to Windows. 
I did build some PowerShell to allow an ID switch as a proof-of-concept: https://gist.github.com/GeoffWilliams/e8f64a8d01f3c8611e5ef06d5989f4d5 but this will only work if executed as a suitable user. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 

Jira (PUP-8395) Exec Parity for Windows

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8395 
 
 
 
  Exec Parity for Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 In Linux, Puppet typically runs as root (full privileges) and can leverage the exec resource's user parameter to run a command as a local user. In Windows, this parity is lacking and it's increasingly causing problems for Puppet users. It would be nice to run things as a local user.This issue is further compounded by common Microsoft System Administration use cases, where various pieces of software are installed and run as domain service accounts. For instance, the SQL Server module does it with [some gnarly Ruby in a provider to set domain credentials in 3 places | https://github.com/puppetlabs/puppetlabs-sqlserver/blob/master/lib/puppet/provider/sqlserver_features/mssql.rb#L7-L8] by passing parameters to the installer. I suggest writing a custom installation provider for software requiring a service account is not a reasonable ask for a typical user who is an experienced Windows admin and nascent Puppet practitioner.There is a large and growing amount of Microsoft enterprise software (SQL Server, SCOM, SCCM, SCVMM) that recommends or requires the use of a domain service account, and there's not currently a good way to address it. Feature parity (and perhaps going a little further to support Domain Accounts) would be a good start, especially if this exec allows users to get the automation done while we determine if other features are needed. (For instance, passing a Microsoft Domain user credential to the package resource).Finally, field experience indicates this is complicated further by Mandatory Access Controls.  These  may limit  deny  the ability of any service running as  Local System  LocalSystem  to interact with the wider world using domain credentials .  and there are no workarounds to disable them that don't break the integrity of the operating system 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-8956) puppet agent doesn't run properly when avast anti-virus running

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8956  
 
 
  puppet agent doesn't run properly when avast anti-virus running   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 pupp-bug-3.png, puppet_bug-2.png, pup_win_bug_1.png  
 
 
Components: 
 Windows  
 
 
Created: 
 2018/06/24 2:46 AM  
 
 
Environment: 
 Windows 10 x64 Avast anti virus active  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Geoff Williams  
 

  
 
 
 
 

 
 Overview Unable to run puppet agent on windows 10 when Avast anti-virus is active   Expected result Expect puppet agent to work without error   Actual result Tons of errors all over the place where the AV agent blocks puppet C:\WINDOWS\system32>puppet agent -t Info: Caching certificate for bpm-r1.lan.asio Info: Caching certificate_revocation_list for ca Info: Caching certificate for bpm-r1.lan.asio Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Notice: /File[C:/ProgramData/PuppetLabs/puppet/cache/lib/facter]/ensure: created Notice: /File[C:/ProgramData/PuppetLabs/puppet/cache/lib/facter/aio_agent_build.rb]/ensure: defined content as '{md5}cdcc1ff07bc245c66cc1d46be56b3af5' Notice: /File[C:/ProgramData/PuppetLabs/puppet/cache/lib/facter/aio_agent_version.rb]/ensure: defined content as '{md5}d05c8cbf788f47d33efd46a935dda61e' Error: ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/lib/facter/archive_windir.rb

Jira (PUP-8956) puppet agent doesn't run properly when avast anti-virus running

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8956  
 
 
  puppet agent doesn't run properly when avast anti-virus running   
 

  
 
 
 
 

 
Change By: 
 Geoff Williams  
 
 
Attachment: 
 puppet_bug-2.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PDOC-260) Ruby error when @return used to document puppet function

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-260  
 
 
  Ruby error when @return used to document puppet function   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.0.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 CLI, UX  
 
 
Created: 
 2018/06/24 11:31 PM  
 
 
Environment: 
 Latest Puppet Strings loaded in Gemfile via: gem 'puppet-strings', :git => 'https://github.com/puppetlabs/puppet-strings'    
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Geoff Williams  
 

  
 
 
 
 

 
 Overview If the @return tag is used to document a function written in puppet code, puppet-strings prints a stack trace, although it does seem to be able to continue past this   Expected result No stack trace. Print a human-readable error if input was not in the correct format   Actual result Stacktrace printed while generating documentation:   }}{{[error]: Unhandled exception in PuppetStrings::Yard::Handlers::Puppet::FunctionHandler: {{ in `functions/find_match.pp`:12:}}12: function logrotate::find_match($setting) >> String {[error]: NoMethodError: undefined method `first' for nil:NilClass [error]: Stack trace: {{ /home/geoff/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/bundler/gems/puppet-strings-ab62430c6862/lib/puppet-strings/yard/handlers/puppet/function_handler.rb:40:in `add_return_tag'}} {{ /home/geoff/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/bundler/gems/puppet-strings-ab62430c6862/lib/puppet-strings/yard/handlers/puppet/function_handler.rb:24:in `block in '}} {{ /home/geoff/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/yard-0.9.14/lib/yard/handlers/processor.rb:114:in `block (2 levels) in process'}} {{ /home/geoff/.rbenv/versions/2.5.1/lib

Jira (PDOC-260) Ruby error when @return used to document puppet function

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-260  
 
 
  Ruby error when @return used to document puppet function   
 

  
 
 
 
 

 
Change By: 
 Geoff Williams  
 
 
Attachment: 
 find_match.pp  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-8956) puppet agent doesn't run properly when avast anti-virus running

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams commented on  PUP-8956  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet agent doesn't run properly when avast anti-virus running   
 

  
 
 
 
 

 
 Customer for this ticket is just me - I have a lab of Windows machines and figured the info might be useful to someone  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-8956) puppet agent doesn't run properly when avast anti-virus running

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams commented on  PUP-8956  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet agent doesn't run properly when avast anti-virus running   
 

  
 
 
 
 

 
 Ethan Brown I ended up uninstalling avast to let puppet run. I'm out of time to spend looking at this issue myself unfortunately  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-8980) `loglevel` parameter for `notify` resource not documented

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8980  
 
 
  `loglevel` parameter for `notify` resource not documented   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 loglevels.png  
 
 
Components: 
 DOCS  
 
 
Created: 
 2018/07/04 12:10 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Geoff Williams  
 

  
 
 
 
 

 
 Overview The notify resource provides a loglevel parameter with colourized output, however, this is not documented at: https://puppet.com/docs/puppet/5.5/types/notify.html Desired outcome Please document the loglevel parameter Example test.pp  
 
 
 
 
 [debug, info, notice, warning, err, alert, emerg, crit, verbose].each |$level| {  
 
 
   notify { "message at level ${level}":  
 
 
 loglevel => $level,  
 
 
   }  
 
 
  

Jira (PDOC-260) Ruby error when @return used to document puppet function

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams commented on  PDOC-260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ruby error when @return used to document puppet function   
 

  
 
 
 
 

 
 Workaround: Make sure there are square brackets around the datatype, eg:    
 
 
 
 
 # @return [String] representing the regex to match the main config file for
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PDOC-263) Puppet strings output on ruby functions seems incorrect

[Geoff Williams (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Williams created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-263  
 
 
  Puppet strings output on ruby functions seems incorrect   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 includable2.rb, includable.rb, REFERENCE.md, Screenshot_2018-08-29_13-10-41.png, Screenshot_2018-08-29_15-16-36.png  
 
 
Created: 
 2018/08/28 10:33 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Geoff Williams  
 

  
 
 
 
 

 
 Puppet Strings version: puppet-strings (2.1.0) GIT Overview Running puppet strings against a ruby function seems to produce some strange outputs: Doubled-up text Descriptive text placed at the top of the file will be duplicated. Source: includable.rb   Missing examples In all cases, rich examples are lost. Lost text Re-positioning to look more like the example at https://puppet.com/docs/puppet/5.5/puppet_strings_style.html#ruby-function-examples results in the text not appearing in the output any more: Source: includable2.rb   @summary fixes TOC formatting @summary seems to work nicely even though the docs say not to use it Desired outcome Would like to be able to include rich examples in function definitions along with descriptive text  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

Jira (FACT-866) pe-facter missing dependency on package providing lsb_release command

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-866 
 
 
 
  pe-facter missing dependency on package providing lsb_release command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Environment:
 
 *Debian*{noformat}geoff@jenkins:~$ lsb_release  -aNo LSB modules are available.Distributor ID: DebianDescription: Debian GNU/Linux 8.0 (jessie)Release: 8.0Codename: jessiegeoff@jenkins:~$ puppet --version3.7.4 (Puppet Enterprise 3.7.2){noformat}*CentOS* {noformat} [root@master tmp]# lsb_release -aLSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarchDistributor ID: CentOSDescription: CentOS release 6.5 (Final)Release: 6.5Codename: Final[root@master tmp]# /opt/puppet/bin/puppet --version3.7.4 (Puppet Enterprise 3.8.0-rc0-281-gd05d353) {noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-866) pe-facter missing dependency on package providing lsb_release command

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-866 
 
 
 
  pe-facter missing dependency on package providing lsb_release command  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.3.0 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Created:
 

 2015/03/24 4:44 PM 
 
 
 

Environment:
 
 
Debian 
 
 
 
 
 
 
geoff@jenkins:~$ lsb_release  -a 
 
 
 
 
No LSB modules are available. 
 
 
 
 
Distributor ID:	Debian 
 
 
 
 
Description:	Debian GNU/Linux 8.0 (jessie) 
 
 
 
 
Release:	8.0 
 
 
 
 
Codename:	jessie 
  

Jira (FACT-866) pe-facter missing dependency on package providing lsb_release command

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  FACT-866 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: pe-facter missing dependency on package providing lsb_release command  
 
 
 
 
 
 
 
 
 
 
Lindsey Smith this is helpful, for public release please 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-866) pe-facter missing dependency on package providing lsb_release command

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-866 
 
 
 
  pe-facter missing dependency on package providing lsb_release command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 h2.  OverviewFactor fact {{lsbdistcodename}} does not work out of the box on minimal OS installs due to the {{pe-facter}} package not specifying a dependency on the package providing the {{lsb_release}} command.Affected platforms:* Debian (tested 8.0/Jessie -- after a forced install of PE agent)* Centos (tested 6.5 -  trainingvm  seteam )* _Probably more_h2.  Expected result{noformat}/opt/puppet/bin/facter lsbdistcodename{noformat}Should always print the LSB release code nameh2.  Actual resultCommand output is dependent on supplementary packages being installed.  On a minimal OS installation a blank line is printed:{noformat}[root@master tmp]# /opt/puppet/bin/facter lsbdistcodename{noformat}h2.  Packaging info*CentOS*{noformat}[root@master tmp]# rpm -q --requires pe-facter/opt/puppet/bin/ruby  dmidecode  pciutils  pe-ruby  pe-virt-what  rpmlib(CompressedFileNames) <= 3.0.4-1rpmlib(FileDigests) <= 4.6.0-1rpmlib(PayloadFilesHavePrefix) <= 4.0-1rpmlib(VersionedDependencies) <= 3.0.3-1which  rpmlib(PayloadIsXz) <= 5.2-1{noformat}*Debian*{noformat}geoff@jenkins:~$ dpkg -s pe-facterPackage: pe-facterStatus: install ok installedPriority: optionalSection: rubyInstalled-Size: 388Maintainer: Puppet Labs Architecture: amd64Version: 2.3.0.2-1puppet1Depends: pe-ruby, dmidecode, pe-virt-what, pciutilsDescription: Ruby module for collecting simple facts about a host operating system Some of the facts are preconfigured, such as the hostname and the operating system. Additional facts can be added through simple Ruby scripts.Homepage: http://www.puppetlabs.com{noformat}h2.  Problems this causesModules that expect to have the {{$::lsbdistcodename}} fact available fail in production in mysterious ways and {{facter}} itself gives no information or warning on how to resolve things.  I was only able to figure out what was broken by looking at the source code.I personally witnessed {{puppetlabs/java}} failing on Debian with a message that the operating system is not supported.  This was resolved by installing the required package.h2.  Condition diagnosisTo confirm you are affected by this issue, run the command:{noformat}/opt/puppet/bin/facter lsbdistcodename{noformat}If you do not see any output, you are missing the {{lsb_release}} programh2.  Workaround*Debian*{noformat}apt-get install lsb_release{noformat}*CentOS/RHEL*{noformat}yum install redhat-lsb-core{noformat}After installing these packages, the fact will work although on CentOS 6.5 it just displays the word {{Final}} which is all that is available via the {{lsb_release}} command. 
 
 
 
 
 
 
 
 
 
 
 
 

 
  

Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Zypper provider doesn't work correctly on SLES 10.4 with install_options set  
 
 
 
 
 
 
 
 
 
 
Melissa Stone this looks like a good fix and thanks for following up. Are customers able to use this file as a drop-in replacement if an immediate fix is needed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Zypper provider doesn't work correctly on SLES 10.4 with install_options set  
 
 
 
 
 
 
 
 
 
 
Melissa Stone Yes that's what I was asking - basically can this file be dropped into an existing Puppet Enterprise 3.7/3.8 installation without breaking anything. I don't see why this wouldn't work - thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-3692) Resource defaults leak between classes at the same level of scope hierarchy

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3692 
 
 
 
  Resource defaults leak between classes at the same level of scope hierarchy  
 
 
 
 
 
 
 
 
 
 
Just because they were a semi-private conversation between the two of us. These updates are great BTW. There's some really nice language features that will soon be usable 
On Wed, Apr 8, 2015 at 8:09 PM, Henrik Lindberg (JIRA) < 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-3692) Resource defaults leak between classes at the same level of scope hierarchy

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3692 
 
 
 
  Resource defaults leak between classes at the same level of scope hierarchy  
 
 
 
 
 
 
 
 
 
 
Just because they were a semi-private conversation between the two of us. These updates are great BTW. There's some really nice language features that will soon be usable 
On Wed, Apr 8, 2015 at 8:09 PM, Henrik Lindberg (JIRA) < 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3692) Resource defaults leak between classes at the same level of scope hierarchy

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3692 
 
 
 
  Resource defaults leak between classes at the same level of scope hierarchy  
 
 
 
 
 
 
 
 
 
 
Just because they were a semi-private conversation between the two of us. These updates are great BTW. There's some really nice language features that will soon be usable 
On Wed, Apr 8, 2015 at 8:09 PM, Henrik Lindberg (JIRA) < 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4414) Puppet forge doesn't work on Windows out-of-the-box

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4414 
 
 
 
  Puppet forge doesn't work on Windows out-of-the-box  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 Modules, UX, Windows 
 
 
 

Created:
 

 2015/04/14 11:11 PM 
 
 
 

Environment:
 
 
Windows server 2012 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
puppet module install doesn't work out-of-the-box on windows. To resolve this, users must follow almost a full page of manual steps from the Puppet Labs Windows troubleshooting guide: https://docs.puppetlabs.com/windows/troubleshooting.html#error-messages 
Expected behaviour 
After installing Puppet, the puppet module face should work as intended without any further configuration required 
Actual behaviour 
Users receive the message:  
 
  

Jira (PUP-4414) Puppet forge doesn't work on Windows out-of-the-box

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4414 
 
 
 
  Puppet forge doesn't work on Windows out-of-the-box  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 h2. Overview{{puppet module install}} doesn't work out-of-the-box on windows.  To resolve this, users must follow  almost a full page of  manual steps from the Puppet Labs Windows troubleshooting guide:  https://docs.puppetlabs.com/windows/troubleshooting.html#error-messagesh2. Expected behaviourAfter installing Puppet, the {{puppet module}} face should work as intended without any further configuration requiredh2. Actual behaviourUsers receive the message:  {noformat}Error: Could not connect via HTTPS to https://forge.puppetlabs.com / Unable to verify the SSL certificate / The certificate may not be signed by a valid CA / The CA bundle included with OpenSSL may not be valid or up to date”{noformat}When running the above command.h2. Problems this causesThe above error is not very user friendly and gives no advice as to how to solve the problem or that it's a known issue.  Users are left to stumble on the above troubleshooting guide either via google or a support ticket.While agents don't usually need to use the module tool, this is not so for developers who are trying to do work on windows.  There are often cases when its preferable to setup a windows machine and do testing via {{puppet apply}}  vs having to provision a fully functional master-agent lab.h2. Suggested fixThe windows installer should automatically install the GeoTrust root CA as part of agent installation.  This would give windows users a functional system immediately. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-4415) hung OS processes stall puppet (agent|apply) runs on client

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4415 
 
 
 
  hung OS processes stall puppet (agent|apply) runs on client  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 Platform, UX 
 
 
 

Created:
 

 2015/04/15 1:39 AM 
 
 
 

Environment:
 
 
centos 6.5 with internet access blocked by corporate firewall (but affects all platforms) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
When the puppet agent needs to run external processes on a node that can potentially hang, its not obvious to users that execution is waiting for a process to complete 
Expected behaviour 
Puppet should give feedback with users as to why it is 'stuck' to assure them that it has not crashed or allow them to troubleshoot why the dependent process is blocking 
Actual behaviour 
Puppet runs can appear to 'stick' for several minutes at certain poin

Jira (PUP-3450) The module tool should embed and use the root CAs it cares about

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams assigned an issue to Geoff Williams 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3450 
 
 
 
  The module tool should embed and use the root CAs it cares about  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Assignee:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4484) host resources are not idempotent

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4484 
 
 
 
  host resources are not idempotent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Attachments:
 

 host1.pp, host2.pp 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2015/04/29 5:45 AM 
 
 
 

Environment:
 
 
 
 
 
 
 
 
[geoff ~]# puppet --version 
 
 
 
 
3.7.4 (Puppet Enterprise 3.7.2) 
 
 
 
 
[geoff ~]# cat /etc/redhat-release  
 
 
 
 
CentOS release 6.6 (Final)
 
 

Jira (PUP-4484) host resources are not idempotent

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4484 
 
 
 
  host resources are not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Attachment:
 
 host2.pp 
 
 
 

Attachment:
 
 host1.pp 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4484) host resources are not idempotent

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4484 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: host resources are not idempotent  
 
 
 
 
 
 
 
 
 
 
Testcase transcript: 
 
 
 
 
 
 
[geoff ~]# puppet apply host2.pp  
 
 
 
 
Notice: Compiled catalog for geoff.puppetlabs.vm in environment production in 0.03 seconds 
 
 
 
 
Notice: Finished catalog run in 0.03 seconds 
 
 
 
 
[geoff ~]# puppet apply host1.pp  
 
 
 
 
Notice: Compiled catalog for geoff.puppetlabs.vm in environment production in 0.03 seconds 
 
 
 
 
Notice: Finished catalog run in 0.03 seconds 
 
 
 
 
[geoff ~]# vi /etc/hosts 
 
 
 
 
  ... make the changes... 
 
 
 
 
[geoff ~]# puppet apply host1.pp  
 
 
 
 
Notice: Compiled catalog for geoff.puppetlabs.vm in environment production in 0.03 seconds 
 
 

Jira (PUP-4484) host resources are not idempotent

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4484 
 
 
 
  host resources are not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 h2. OverviewThe {{host}} resource is not idempotent and can fail suddenly in production if the {{/etc/hosts}} file is altered *and* you written Puppet code that doesn't satisfy the provider's expectation of mandatory attributes.h2. Expected resultExecuting identical Puppet code should give an idempotent result, it should either always fail or always succeed so that users can have confidence in their systems.h2. Actual resultUnder certain conditions an identically configured {{host}} resource that was previously working (or more accurately not raising an error) can suddenly fail, giving the error message: {{ip is a required attribute for hosts}}h2. Steps to reproduce1.  {{puppet apply host2.pp}}2.  {{puppet apply host1.pp}}3.  Manually edit {{/etc/hosts}} and remove the entry for {{testing.puppetlabs.vm}}4.  {{puppet apply host1.pp}}At this point the previously tested and working code will generate the above error messageh2. Problems this causesUsers could potentially write _timebomb_ code that fails when entries in the {{/etc/hosts}} file are removed.  This is particularly troublesome as {{hosts}} entries are typically used to configure networking and this could conceivably cause a service outage, albeit one that is due to errors in the user's own code.h2. ExplanationThe {{ip}} attribute is mandatory for {{hosts}} resources but the provider doesn't enforce this check unless it needs to re-create the resource in question.h2.  Suggested fixMandatory parameters should be checked by providers at all times, not only a resource needs to be re-created.  This will aid users in writing robust code and will limit the opportunity for this class of problems to appear on production systems. h2. WorkaroundUsers need to remember which attributes for {{host}} resources are mandatory and must code them into their manifests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

Jira (PUP-4542) mandatory attributes on defined resource types are not required for virtual/exported resources

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4542 
 
 
 
  mandatory attributes on defined resource types are not required for virtual/exported resources  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 Language, UX 
 
 
 

Created:
 

 2015/05/07 8:05 PM 
 
 
 

Environment:
 
 
3.7.4 (Puppet Enterprise 3.7.2) CentOS release 6.6 (Final) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
When declaring a virtual or exported resource using defined resource types, Puppet does not raise an error if mandatory attributes are not supplied. 
Testcase 
Create a single text file with the content below and run with puppet apply 
 
 
 
 
 
 

Jira (PUP-4542) mandatory attributes on defined resource types are not required for virtual/exported resources

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4542 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: mandatory attributes on defined resource types are not required for virtual/exported resources  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg I did wonder if this was the case. It would be great if this could be reviewed in order to give a more consistent experience to end users 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4632) puppet agent shows warning messages in red

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4632 
 
 
 
  puppet agent shows warning messages in red  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.0 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client, UX 
 
 
 

Created:
 

 2015/05/20 12:42 AM 
 
 
 

Environment:
 
 
 
 
 
 
 
 
[geoff ~/puppetcode/modules  master±]# cat /etc/redhat-release  
 
 
 
 
CentOS release 6.6 (Final)
 
 
 
 
 
 
 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
  

Jira (PUP-4632) puppet agent shows warning messages in red

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4632 
 
 
 
  puppet agent shows warning messages in red  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Attachment:
 
 Screen Shot 2015-05-20 at 3.38.16 pm.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4632) puppet agent shows warning messages in red

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4632 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet agent shows warning messages in red  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg are you able to set the background colour and the text colour at the same time? That might be a way to fix it.  
Users are getting understandably frustrated here, red should be reserved for errors - warnings should definitely be a less jarring colour. This is an important usability issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4670) puppet parser validate gives a warning when exported resources are present

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4670 
 
 
 
  puppet parser validate gives a warning when exported resources are present  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.0 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 UX 
 
 
 

Created:
 

 2015/05/29 2:51 AM 
 
 
 

Environment:
 
 
 
 
 
 
 
 
$puppet --version 
 
 
 
 
3.8.0 (Puppet Enterprise 3.8.0)
 
 
 
 
 
 
 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 

Jira (PUP-4632) puppet agent shows warning messages in red

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4632 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet agent shows warning messages in red  
 
 
 
 
 
 
 
 
 
 
I think both of those ideas would be good compromises. Maybe even bold text instead of red text for warnings - in the regular text colour - can that be done? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-3692) Resource defaults leak between classes at the same level of scope hierarchy

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-3692 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Resource defaults leak between classes at the same level of scope hierarchy  
 
 
 
 
 
 
 
 
 
 
Charlie Sharpsteen by limiting resource defaults to containment graphs do you mean thinks like the anchor pattern and contain() function? If so, speaking for the users I've met, I can tell you that they would not find this at all intuitive.  
On our courses, we teach users about logical scopes: top level, node and class. On our advanced level training we do look at containment graphs but only really from the point of view of how to fix a graph which is misbehaving, e.g., dependencies installed in the wrong order, loops, that kind of thing. 
It's almost like we're missing another scope - "module". In-lieu of this, propagating resource defaults in class scope only looks to be a good fix. At least from the point-of-view of eliminating unintended resource default leakage. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4632) puppet agent shows warning messages in red

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4632 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet agent shows warning messages in red  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg it is unreadable - but it also stands out enough for users to say "hmm I should look at this". Getting rid of the unnecessary red error messages is a great UX improvement, thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4700) make color output work for all users

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4700 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: make color output work for all users  
 
 
 
 
 
 
 
 
 
 
I think the main thing is to use colours that don't cause unnecessary alarm like we do at the moment. Red should be reserved for errors, not warnings. I've had several customers and students bring this up with me. Happy to discuss in private. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-5722) value cannot be converted to numeric error when require metaparameter incorrectly used

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5722 
 
 
 
  value cannot be converted to numeric error when require metaparameter incorrectly used  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/18 9:21 PM 
 
 
 

Environment:
 
 
PL classroom environment/PE 2015.3.1 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
If a puppet manifest incorrectly specifies a require attribute (lower case typename instead of capitalising), user will receive an unhelpful error message with no line number. 
Expected result 
At a minimum, the user should always be given a line number with a parser error. A more helpful message would be good too, "unable to reference resource package["nginx"] at line 3" would be perfect if such a thing is possible. 
Actual result 
Users receive something similar to the following error: 
 
 
 
 
 

Jira (PUP-5722) value cannot be converted to numeric error when require metaparameter incorrectly used

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-5722 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: value cannot be converted to numeric error when require metaparameter incorrectly used  
 
 
 
 
 
 
 
 
 
 
love the explanation - thanks Henrik Lindberg! If we have line numbers that's good enough for me. Not sure if/when this new version of puppet will be released in PE and I'll have time to test it so this can probably be closed as fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-5479) segfault with augeas type when changes attribute is too long

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-5479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: segfault with augeas type when changes attribute is too long  
 
 
 
 
 
 
 
 
 
 
David Lutterkort Classroom VMs are downlable at http://downloads.puppetlabs.com/training/  
I was able to reproduce the issue with a plain cento6 VM and the attached testcase when I first spotted this which was a while ago. I would imagine that if your now unable to reproduce the issue with the testcase then its probably fixed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-1909) Priority setting also given to started processes/services

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1909 
 
 
 
  Priority setting also given to started processes/services  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

CS Priority:
 
 Needs Priority 
 
 
 

CS Impact:
 
 Gold partner in NZ has run into this and its having an impact on a large puppet installation.  I can verify that latest PE2015-3.3 is also affected by this.  Agent priority is not visibly changed using {{ps}} unless the adjustment is made in the {{[main]}} section and then it affects other parts of puppet as well.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6322) EPP and scope context

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-6322 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EPP and scope context  
 
 
 
 
 
 
 
 
 
 
Gets my vote. Keep things simple and reduce the amount of typing needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3690) puppet gives red warning about allow_virtual on every run

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3690 
 
 
 
  puppet gives red warning about allow_virtual on every run  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.2 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2014/11/23 4:25 PM 
 
 
 

Environment:
 
 
Puppet Labs Training VM 2.13 (Build 3f4da74) [root@master ~]# puppet --version 3.7.2 (Puppet Enterprise 3.7.0) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Current versions of puppet are giving scary red warning messages about allow_virtual being changed from false to true on every agent run: 
 
 
 
 
 
 
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want

Jira (PUP-3692) Resource defaults leak between classes at the same level of scope hierarchy

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3692 
 
 
 
  Resource defaults leak between classes at the same level of scope hierarchy  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 resource_default_scope_testcase.tar.gz 
 
 
 

Components:
 

 DSL 
 
 
 

Created:
 

 2014/11/23 11:57 PM 
 
 
 

Environment:
 
 
Puppet Labs Training VM 2.13 (Build 3f4da74) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Resource defaults set in 'class' scope currently leak into adjacent classes taking effect in the order they are parsed. I believe this is known internally as "dynamic scoping". 
As the use of puppet forge and modules in general has started to i

Jira (PUP-3692) Resource defaults leak between classes at the same level of scope hierarchy

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3692 
 
 
 
  Resource defaults leak between classes at the same level of scope hierarchy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 Resource defaults set in 'class' scope currently leak into adjacent classes taking effect in the order they are parsed.  I believe this is known internally as "dynamic scoping".As the use of puppet forge and modules in general has started to increase, this is starting to cause problems that are hard to diagnose and fix.This problem typically manifests itself as incorrect file ownership due to setting resource defaults for the File resource, but of-course could affect any resource type in puppet.h3.  Problems this causes*Breaks idempotency of include function*The parse order of include statements changes the effect of the final catalogue - see testcase*Resource defaults leak into unrelated classes*Depending on parse order, its possible for resource defaults to leak into unrelated classes and alter the effect of them in subtle ways - in the past this has broken the concat module to the extent that puppet fails to run (see linked issues).  I'm sure there are other examples of this too.*Hard to fix modules elegantly*Unwanted resource defaults are not easy to fix elegantly as they can require invasive code changes to protect against external influences.  I have personal experience of this with the linked bug report to the concat module.  In this case, you could argue the 'module above/including us' is the one with the problem since concat normally works fine.  It becomes hard to see elegant ways to fix problems or indeed which module has a problem in the first place - the including one? the included one? both? puppet itself?  See link to  discussion  on hunner-wordpress module's github issues page.*Against the puppet ideology*IMO puppet is supposed to be idempotent, with transparent and intuative results.  The "dynamic scoping" of resource defaults goes against these principles.h3.  TestcaseThe attached testcase has two test files that should be funtionally identical but are not, because they include classes in different orders.  This results in different file ownership for {{/tmp/defaults_testcase}} file, and worse, the {{/tmp/unrelated}} file which picks up the unwanted resource defaults even thought its in another module:{noformat}[root@master /etc/puppetlabs/puppet]# puppet apply modules/defaults_testcase/tests/order1.ppNotice: Compiled catalog for master.puppetlabs.vm in environment production in 0.11 secondsNotice: /Stage[main]/Defaults_testcase::Class_c/File[/tmp/defaults_testcase]/ensure: createdNotice: /Stage[main]/Unrelated/File[/tmp/unrelated]/ensure: createdNotice: Finished catalog run in 0.15 seconds[root@master /etc/puppetlabs/puppet]# ls -l /tmp/defaults_testcase /tmp/unrelated -rw-r--r-- 1 wordpress wordpress 0 Nov 24 07:28 /tmp/defaults_testcase-rw-r--r-- 1 wordpress wordpress 0 Nov 24 07:28 /tmp/unrelated[root@master /etc/puppetlabs/puppet]# puppet apply modules/defaults_testcase/tests/order2.ppNotice: Compiled catalog for master.puppetlabs.vm in environment production in 0.12 secondsNotice: /Stage[main]/Defaults_testcase::Class_c/File[/tmp/defaults_testcase]/owner: owner changed 'wordpress' to 'drupal'Notice: /Stage[main]/Defaults_testcase::Class_c/File[/tmp/defaults

Jira (PUP-3692) Resource defaults leak between classes at the same level of scope hierarchy

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-3692 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Resource defaults leak between classes at the same level of scope hierarchy  
 
 
 
 
 
 
 
 
 
 
moreinfo supplied by Gary Larizza 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (FACT-763) facter uses missing ifconfig command to build ipaddress fact

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-763 
 
 
 
  facter uses missing ifconfig command to build ipaddress fact  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.2.0 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 PE 
 
 
 

Created:
 

 2014/11/28 12:29 AM 
 
 
 

Environment:
 
 
CentOS Linux release 7.0.1406 (Core)  PE 3.7.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
In a minimal centos 7 environment, the ifconfig command is no longer installed by default (it's been deprecated). 
This command is used by facter to bulid the $ipaddress fact so on minimal installs this fact is no longer available by default 
.h2 Suggestions to fix Rewrite ipaddress fact to use the ip command or Facter should depend on the net-tools package 
 
 
 
 
 
 
 
 
  

Jira (FACT-763) facter uses missing ifconfig command to build ipaddress fact

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-763 
 
 
 
  facter uses missing ifconfig command to build ipaddress fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 In a minimal centos 7 environment, the {{ifconfig}} command is no longer installed by default (it's been deprecated).This command is used by facter to bulid the $ipaddress fact so on minimal installs this fact is no longer available by default . h2 .  Suggestions to fixRewrite ipaddress fact to use the {{ip}} command_or_Facter should depend on the {{net-tools}} package 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-3989) output of puppet module generate does not include a .fixtures.yml file causing tests to fail

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3989 
 
 
 
  output of puppet module generate does not include a .fixtures.yml file causing tests to fail  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Platform 
 
 
 

Created:
 

 2015/02/09 10:09 PM 
 
 
 

Environment:
 
 
CentOS Linux release 7.0.1406 (Core) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Background 
Using the command puppet module generate ... doesn't create a module with a functional RSpec testing infrastructure 
Test case 
Generate a module and observe the tests don't run out of the box: 
 
 
 
 
 
 
   

Jira (PUP-3989) output of puppet module generate does not include a .fixtures.yml file causing tests to fail

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3989 
 
 
 
  output of puppet module generate does not include a .fixtures.yml file causing tests to fail  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 h2. BackgroundUsing the command {{puppet module generate ...}} doesn't create a module with a functional RSpec testing infrastructureh2. Test caseGenerate a module and observe the tests don't run out of the box:{noformat}[root@localhost ~]# puppet module generate test-testWe need to create a metadata.json file for this module.  Please answer thefollowing questions; if the question is not applicable to this module, feel freeto leave it blank.Puppet uses Semantic Versioning (semver.org) to version modules.What version is this module?  [0.1.0]--> Who wrote this module?  [test]--> What license does this module code fall under?  [Apache 2.0]--> How would you describe this module in a single sentence?--> Where is this module's source code repository?--> Where can others go to learn more about this module?--> Where can others go to file issues about this module?--> {  "name": "test-test",  "version": "0.1.0",  "author": "test",  "summary": null,  "license": "Apache 2.0",  "source": "",  "project_page": null,  "issues_url": null,  "dependencies": [{"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"}  ]}About to generate this metadata; continue? [n/Y]--> yNotice: Generating module at /root/test-test...Notice: Populating templates...Finished; module generated in test-test.test-test/teststest-test/tests/init.pptest-test/Rakefiletest-test/spectest-test/spec/classestest-test/spec/classes/init_spec.rbtest-test/spec/spec_helper.rbtest-test/Gemfiletest-test/manifeststest-test/manifests/init.pptest-test/metadata.jsontest-test/README.md[root@localhost ~]# cd test-test/[root@localhost test-test]# bundle installDon't run Bundler as root. Bundler can ask for sudo if it is needed, andinstalling your bundle as root will break this application for all non-rootusers on this machine.Fetching gem metadata from https://rubygems.org/..Fetching version metadata from https://rubygems.org/..Resolving dependencies...Using rake 10.4.2Using CFPropertyList 2.2.8Using diff-lcs 1.2.5Using facter 2.4.0Using json_pure 1.8.2Using hiera 1.3.4Using metaclass 0.0.4Using mocha 1.1.0Using puppet 3.7.4Using puppet-lint 1.1.0Using puppet-syntax 1.4.1Using rspec-core 2.99.2Using rspec-expectations 2.99.2Using rspec-mocks 2.99.3Using rspec 2.99.0Using rspec-puppet 2.0.0Using puppetlabs_spec_helper 0.8.2Using bundler 1.7.13Your bundle is complete!Use `bundle show [gemname]` to see where a bundled gem is installed.[root@localhost test-test]# bundle exec rake spec/usr/bin/ruby -S rspec spec/classes/init_spec.rb --colorFFailures:  1) test with defaults for all parameters should contain Class[test] Failure/Error: it { should contain_class('test') } Puppet::Error:   Could not find class test for localhost.lan.asio on node localhost.lan.asio # /usr/share/ruby/benchmark.rb:296:in `realtime' # ./spec/classes/init_spec.rb:5:in `block (3 levels) in 'Finished in 0.04774 seconds1 example, 1 failureFailed examples:rspec ./spec/classes/init_spec.rb:5 # test with defaults for all parameters should contain Clas

Jira (PUP-4078) puppet resource tool output contains incorrect quoting

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4078 
 
 
 
  puppet resource tool output contains incorrect quoting  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Platform 
 
 
 

Created:
 

 2015/03/03 6:25 PM 
 
 
 

Environment:
 
 
3.7.4 (Puppet Enterprise 3.7.2) 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
puppet resource currently outputs quotes around values such as 'false' which should logically equate to true unless there are additional measures in place to parse out known values before continuing. 
Problems this causes 
As part of the preparation for PE 4.x which includes optional typing, we need to help educate users not to write code which is ambiguous or needs additional processing to work correctly. 
It's important that the RAL tool generates good puppet code because: 
   

Jira (PUP-4078) puppet resource tool output contains incorrect quoting

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4078 
 
 
 
  puppet resource tool output contains incorrect quoting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 h2. Overview{{puppet resource}} currently outputs quotes around values such as {{'false'}} which should logically equate to true unless there are additional measures in place to parse out known values before continuing.h2. Problems this causesAs part of the preparation for PE 4.x which includes optional typing, we need to help educate users not to write code which is ambiguous or needs additional processing to work correctly.It's important that the RAL tool generates _good_ puppet code because:* Its often the first puppet code a user will see (output by installer)  so we need to make sure we don't teach bad habits * Its output be used for reverse engineering systems and can end up becoming deeply embedded into a codebaseh2. Worked exampleInspecting the {{pe-puppet}} service - note quoting around boolean (and reserved word?):{noformat}[root@xagent1 ~]# puppet resource service pe-puppetservice { 'pe-puppet':  ensure => 'running',  enable => 'true',}{noformat}_Change the {{pe-puppet}} daemon to be stopped with {{puppet resource -e service pe-puppet}}_Check output of puppet resource command again, note quoting as above{noformat}[root@xagent1 ~]# puppet resource service pe-puppetservice { 'pe-puppet':  ensure => 'stopped',  enable => 'false',}{noformat}h2. Corrective action* booleans should not be quoted* reserved words should not be quoted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You re

Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4090 
 
 
 
  Zypper provider doesn't work correctly on SLES 10.4  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 h2. OverviewAttempting to run puppet with {{install_options}} set to disable GPG checks for package installation results in an error from the {{zypper}} command that the {{--name}} and {--no-gpg-checks}} options are not recognised.With the stock puppet zypper provider, its impossible to install packages with option set.h2.  Test caseThe following Puppet code was used to attempt to bypass the {{zypper}} GPG signing requirements:{noformat}  package { 'REDACTED':,  provider => 'zypper',  name => REDACTED,  ensure => $user_supplied_variable,  install_options => [ '--no-gpg-checks' ], }{noformat}Running this code resulted in an error from the {{zypper}} command being returned via a failed Puppet execution:{noformat}# /opt/puppet/bin/puppet agent --testInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for REDACTEDInfo: Applying configuration version '1425621321'Error: Could not update: Execution of '/usr/bin/zypper --terse install --auto-agree-with-licenses --no-confirm --name --no-gpg-checks REDACTED(was package name)' returned 2: Unknown option --nameUnknown option --no-gpg-checksWrapped exception:Execution of '/usr/bin/zypper --terse install --auto-agree-with-licenses --no-confirm --name --no-gpg-checks REDACTED' returned 2: Unknown option --nameUnknown option --no-gpg-checksError: /Stage[main]/REDACTED/Package[REDACTED]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/zypper --terse install --auto-agree-with-licenses --no-confirm --name --no-gpg-checks REDACTED' returned 2: Unknown option --nameUnknown option --no-gpg-checksNotice: Finished catalog run in 0.97 seconds{noformat}h2. Experimental workaroundThe {{zypper}} command in this version of SUSE expects the parameters to be ordered in a different way to that which is coded into the {{zypper.rb}} provider.  As an experiment, I was able to rearrange things so that the parameters were fed in the order that the program accepts:* --no-gpg-checks must come before the action (install)* --name doesn't seem to be recognised at any position and had to be removed* package name should directly follow the action, eg {{install foobar}}h2. Long term fixDue to the way {{zypper}} is invoked, perhaps we may need two arguments to be passed to different parts of the command to get it to work as advertised, eg:{noformat}zypper $default_options $command_options $subcommand $subcommand_options $package_name{noformat}Or perhaps the invocation of the zypper command has changed between SUSE versions? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Commen

Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4090 
 
 
 
  Zypper provider doesn't work correctly on SLES 10.4  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2015/03/05 10:12 PM 
 
 
 

Environment:
 
 
SUSE version: 
 
 
 
 
 
 
# cat /etc/SuSE-release 
 
 
 
 
SUSE Linux Enterprise Server 10 (x86_64) 
 
 
 
 
VERSION = 10 
 
 
 
 
PATCHLEVEL = 4
 
 
 
 
 
 
 
Pupp

Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4090 
 
 
 
  Zypper provider doesn't work correctly on SLES 10.4  
 
 
 
 
 
 
 
 
 
 
Patch against /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/zypper.rb to enable support for bypassing GPG checks (passed via install_options Puppet attribute) 
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Attachment:
 
 install_options_gpg_workaround.patch 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4090) Zypper provider doesn't work correctly on SLES 10.4

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4090 
 
 
 
  Zypper provider doesn't work correctly on SLES 10.4  
 
 
 
 
 
 
 
 
 
 
complete replacement zypper.rb provider (this is a hack and will almost certainly fail on systems that aren't SUSE 10 patch level 4) 
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Attachment:
 
 zypper.rb.new 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4090 
 
 
 
  Zypper provider doesn't work correctly on SLES 10.4 with install_options set  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Summary:
 
 Zypper provider doesn't work correctly on SLES 10.4  with install_options set 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4078) puppet resource tool output contains incorrect quoting

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-4078 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet resource tool output contains incorrect quoting  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg What would you say octal file permissions should be set to? At the moment we advise to write code like this: 
 
 
 
 
 
 
file { "/bla": 
 
 
 
 
  ..., 
 
 
 
 
  mode => "0755", 
 
 
 
 
}
 
 
 
 
 
 
 
Is this still correct? Maybe 0755 with no quotes would now be 'better'? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 Bu

Jira (PUP-3323) yum provider should be able to install from remote URLs

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3323 
 
 
 
  yum provider should be able to install from remote URLs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Attachment:
 
 yum.rb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-3323) yum provider should be able to install from remote URLs

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-3323 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: yum provider should be able to install from remote URLs  
 
 
 
 
 
 
 
 
 
 
I've created a PR addressing this since I also ran into this problem: https://github.com/puppetlabs/puppet/pull/5986 
Using the above testcase, I can see puppet attempting the installation directly with yum: 
 
 
 
 
 
 
Debug: Executing: '/usr/bin/yum -d 0 -e 0 -y install http://www.netconsonance.com/downloads/activemq-5.9.1-2.el6.noarch.rpm'
 
 
 
 
 
 
 
Updated yum.rb attached for convenience  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PDOC-171) generate the hiera keynames to use for parameterised classes

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-171 
 
 
 
  generate the hiera keynames to use for parameterised classes  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/08/02 7:46 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
It would be cool if puppet-strings could generate the keyname to use for hiera when documenting puppet classes. 
At the moment parameters for say an motd class are documented like this: 
Parameters: 
 

content (String) (defaults to: undef) — String to be used for motd
 

issue_content (String) (defaults to: undef) — String to be used for /etc/issue
 

issue_net_content (String) (defaults to: undef) — String to be used for /etc/issue.net identical_message (Boolean) (defaults to: false) — If true, use the main MOTD message for all messages unless overriden by issue_content and issue_net ...
 
 
I would like this to be enhanced with final name of the hiera key a user must add in order to set values, along the lines of: Parameters: 
 

content (String) (defaults to: undef; hiera key motd::content) — String to be used for motd
 

Jira (PDOC-171) generate the hiera keynames to use for parameterised classes

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PDOC-171 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: generate the hiera keynames to use for parameterised classes  
 
 
 
 
 
 
 
 
 
 
so you mean extend this ticket to cover if someone was using in-module hiera data to set defaults then pick up those and document what they resolve to? That would be even better and really useful. perhaps there could even be some _javascript_ magic so that you could see what defaults eg for different OS's 
On 3 Aug. 2017 21:25, "Henrik Lindberg (JIRA)" < issue-updates+henriklindb...@puppet.com> wrote: 
Henrik Lindberg  commented on [image: New Feature] PDOC-171  
Re: generate the hiera keynames to use for parameterised classes  
When considering adding support for hiera bindings it is also of value to make it possible to document default data bindings and lookup options. A module could for example come with lookup options configured for deep merge etc for some parameters, and could have defaults bound in hiera (as opposed to defaults in manifests). The most elegant would be if PDOC could pick up the information directly from hiera, but this gets complicated because information can come from any kind of backend. It is therefore best if this is documented in the puppet logic. If doing that, then there needs to be a structured way to mark up a parameter with such information. [image: Add Comment]  Add Comment  
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) [image: Atlassian logo] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop recei

Jira (PUP-7828) Standalone `hiera` command errors with hiera v5 config file

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7828 
 
 
 
  Standalone `hiera` command errors with hiera v5 config file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.10.5 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 

Components:
 

 Hiera & Lookup 
 
 
 

Created:
 

 2017/08/09 6:34 PM 
 
 
 

Environment:
 
 
RHEL7 $ which hiera /opt/puppetlabs/bin/hiera ]$ hiera --version 3.3.2 $ rpm -qf /opt/puppetlabs/bin/hiera puppet-agent-1.10.5-1.el7.x86_64 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview Sometimes you need to use the standalone `hiera` command to debug a hierarchy when working with tools such as onceover or when setting up a whole puppet lookup environment is impractical. 
If this is attempted using the `hiera` command shipped in puppet-agent-1.10.5-1.el7.x86_64.rpm user will always encounter a confusing error if `version` is set to `> 3` in the `hiera.yaml` file 
Expected result Expect to be able to lookup data item on the command line using `hiera` command and hiera v5 config file 
   

Jira (PUP-7828) Standalone `hiera` command errors with hiera v5 config file

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7828 
 
 
 
  Standalone `hiera` command errors with hiera v5 config file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 *Overview*Sometimes you need to use the standalone  `  {{ hiera ` }}  command to debug a hierarchy when working with tools such as {{onceover}} or when setting up a whole {{puppet lookup}} environment is impractical.If this is attempted using the  `  {{ hiera ` }}  command shipped in puppet-agent-1.10.5-1.el7.x86_64.rpm user will always encounter a confusing error if  `  {{ version ` }}  is set to  `  {{ > 3 ` }}  in the  `  {{ hiera.yaml ` }}  file*Expected result*Expect to be able to lookup data item on the command line using  `  {{ hiera ` }}  command and hiera v5 config file*Actual result*User receives the  very confusing  error:{noformat}Failed to start Hiera: RuntimeError: v4 hiera.yaml is only to be used inside an environment or a module and cannot be given to the global hiera{noformat}*Steps to reporoduce*1. Hiera.yaml{noformat}---version: 5defaults:   datadir: hieradata  data_hash: yaml_datahierarchy:  - name: "Common data"path: "common.yaml"{noformat}2. Lookup data as users:{noformat}hiera -c hiera.yaml ruh::rohFailed to start Hiera: RuntimeError: v4 hiera.yaml is only to be used inside an environment or a module and cannot be given to the global hiera{noformat}*Analysis*The error message seems to indicate that the hiera configuration file uses the old v4 format but it doesn't, its definitely version 5 and works fine with {{puppet lookup}} if dropped into the correct directory.  Looking at the sourcecode, versions > 3 will allways encounter this error and Indeed the error can be cleared by declaring {{version: 3}} in the {{hiera.yaml}} file.  I didn't check if this 'trick' still lets you work with hiera 5 functionality and wouldn't recommend it.*Workarounds*Setup the system to use  {{  puppet lookup }}  (?)*Desired fix*I'm not sure what is supposed to happen here.  I understand that hiera is now part of puppet but where does this leave the standalone hiera command?  Is it intended to work at all?  Is it deprecated in favour of {{puppet lookup}}?  Is it only intended to work with {{hiera.yaml}} files v3 and earlier?  Would be great to get some clarity around these issues as the error message about v4 configuration files is confusing when file is already in v5 format. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

Jira (HI-577) Standalone `hiera` command errors with hiera v5 config file

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  HI-577 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Standalone `hiera` command errors with hiera v5 config file  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg that comment was exactly what I'm after, thanks.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-7861) beaker instructions at ./acceptance/readme seem to be wrong

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7861 
 
 
 
  beaker instructions at ./acceptance/readme seem to be wrong  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 Test Infrastructure 
 
 
 

Created:
 

 2017/08/22 10:25 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Instructions for running beaker locally in the file acceptance/README.md seem to be broken in master. 
I've been running using: 
 
 
 
 
 
 
CONFIG=config/nodes/centos6-local.yaml SHA=#{test-commit-sha} GIT_SERVER='192.168.80.1' FORK='puppet' bundle exec rake --trace ci:test:git
 
 
 
 
 
 
 
As suggested by the instructions, I encountered 2x failures: 
Errored build: Unable to yum install rubygem-json Fix was to use a centos7 vagrant box which already has "Development Tools" metapackage installed 
Errored build: Unable to checkout puppet from git 
 
   

Jira (PUP-7861) beaker instructions at ./acceptance/readme seem to be wrong

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-7861 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: beaker instructions at ./acceptance/readme seem to be wrong  
 
 
 
 
 
 
 
 
 
 
I guess I could add back GIT_SERVER to 010_TestSetup.rb if thats OK, that seemed to be the only place its needed. I'll see what I can put together 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PDOC-177) please could we have an updated rubygem release

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-177 
 
 
 
  please could we have an updated rubygem release  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/09/21 5:14 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
There are a few fixed in master branch that are not yet released as a ruby gem which means I need to install directly from git every time I want to use puppet-strings, would it be possible to get an updated gem released please? Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-8240) ERB and EPP templates handle CRLF line endings inconsistently

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-8240 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ERB and EPP templates handle CRLF line endings inconsistently  
 
 
 
 
 
 
 
 
 
 
Garrett Guillotte Expectation would be accurate documentation at a bare minimum. I feel like the epp() function should do something sensible with CRLF too otherwise its unusable on windows in a lot of situations. Similar behaviour to ERB would work, as would a line-endings option to the epp() function itself - long as there is a documented and supported path to write files on windows I'm happy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-8240) ERB and EPP templates handle CRLF line endings inconsistently

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-8240 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ERB and EPP templates handle CRLF line endings inconsistently  
 
 
 
 
 
 
 
 
 
 
no I couldn't care less about \r\n literal escape sequences - that looks just plain wrong in the docs. 
I was using puppet 4.10.8 to test this - possibly the testcase is incorrect or newer version fixes? I was unable to get windows style line endings no matter what I tried earlier. I'm calling it a day my end but will look again next time I get a moment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-3483) Systemd provider doesn't scan for changed units

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-3483 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Systemd provider doesn't scan for changed units  
 
 
 
 
 
 
 
 
 
 
I'm hitting this too - In my case I've created the exec resource but am now having to reference it all over the place as the packaging cannot fix the things I need since I'm writing puppet code to update the systemd unit files/environment settings after-the-fact. In addition to this I'm having to write code to special-case windows in order to not attempt to interact with systemd at all. 
To me, it would be a much cleaner solution if the puppet service resource could handle any required reloads once and for all so that I don't have to 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5463) undef not usable in collector search?

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5463 
 
 
 
  undef not usable in collector search?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

CS Priority:
 
 Needs Priority 
 
 
 

CS Impact:
 
 Requesting CS assessment of this bug.  Support are hitting this with Optus: 2200nodes/$460K product sold.Dylan Ratcliffe has come up with a really ugly workaround for this customer that involves duplicating a built in type and conditionally altering the defaults.  This places the maintenance burden on the customer and could make future upgrades problematic.It would be a neater solution for all involved if we could simply fix the bug in the puppet agent.  Support ticket is here:  https://puppetlabs.zendesk.com/agent/tickets/20119 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3188) puppetdb token auth documentation is vauge on what permissions needed

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PDB-3188 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb token auth documentation is vauge on what permissions needed  
 
 
 
 
 
 
 
 
 
 
Please could the page link back to the table? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PDB-3188) puppetdb token auth documentation is vauge on what permissions needed

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PDB-3188 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppetdb token auth documentation is vauge on what permissions needed  
 
 
 
 
 
 
 
 
 
 
so the values above for view_data, edit_data are correct but the console GUI seems to speak its own different dialect and to a different RBAC API endpoint. The above fragments when fed to the consumer API will result in a 400 bad request error. Users MUST look at the API documentation where they will learn that: 
 

Instance must be set to *
 

Camel-case field names must be lowercased and underscored, eg objectType becomes object_type
 
 
That's pretty confusing behaviour, maybe a warning is in order? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4937) puppet agent runs report time spent applying catalogue but omit total time spent

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4937 
 
 
 
  puppet agent runs report time spent applying catalogue but omit total time spent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.2.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 AIO 
 
 
 

Created:
 

 2015/07/27 6:32 PM 
 
 
 

Environment:
 
 
RHEL 7 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
Puppet agent reports time spent applying the catalogue but does not report the total time spent running the command (or compiling the catalogue). 
Problems this causes 
Sometimes external factors such as https://tickets.puppetlabs.com/browse/PE-11243 cause catalogue compilation to take several minutes but the agent reports that it has only spent a few seconds running. 
This initially seems to indicate that the VM running puppet is losing time, possibly due to contention in the hypervisor system. This wastes time an

Jira (PUP-5026) error message "illegal comma separated argument list" does not give a line number

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5026 
 
 
 
  error message "illegal comma separated argument list" does not give a line number  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.2.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2015/08/12 12:39 AM 
 
 
 

Environment:
 
 
macosx 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
If code accidentally includes bad list syntax in the body of their class code, they will receive an error message that does not include a line number. This is somewhat confusing. I had this error and spent a good few minutes looking at the parameters to my class before I realised the error was in the body of my code. 
Expected behaviour 
The compile error should give a line number so that user's can find the error easily 
Actual behaviour 
User's receive the messag

Jira (PUP-5090) Message for missing title is unhelpful

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5090 
 
 
 
  Message for missing title is unhelpful  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.2.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2015/08/25 9:26 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
If customers accidentally forget to type a resource title (or forget to capitalise the first letter of a type to set resource defaults), then the error message shown by puppet is hard to understand. 
Testcase 
 
 
 
 
 
 
file { 
 
 
 
 
  owner => "root", 
 
 

Jira (PUP-5090) Message for missing title is unhelpful

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-5090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Message for missing title is unhelpful  
 
 
 
 
 
 
 
 
 
 
lindsey.smith in this case the user was trying to write a resource default but accidentally lowercased it so I made an executive decision that the symbol should be treated as a resource type (even though he didn't want it to be one): 
 
 
 
 
 
 
 ^[a-z] --> its a resource type
 
 
 
 
 
 
 
in this case, we are now obviously missing a resource title. When the user noticed this, he immediately twigged that he should have capitalised the first letter to set a resource default and was able to resolve his issue in seconds. 
We were able to detect this condition by commenting out the line to prove that it did indeed contain the error and by squinting at it we were able to see the fault in the code. 
I can see the conundrum your outlining, or at least I think I can! We don't necessarily have to solve the user's problem for him, we just have to express the problem in a more human friendly way. We both had real difficulty figuring out what exactly the message meant other then that there was an error on the line. If the above message could be simplified so that an entry level puppet coder can understand it, then that would be a good outcome for this ticket. 
As for how often this occurs, that really depends on how accurately users can type. I've only ever seen one regular user encounter this message and it stopped him in his tracks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-5090) Message for missing title is unhelpful

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-5090 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Message for missing title is unhelpful  
 
 
 
 
 
 
 
 
 
 
How about just that then? "A value was produced and then forgotten on line X:y, one or more of the expressions does not have the correct form" – or something along those lines. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-5352) PMT progress display

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5352 
 
 
 
  PMT progress display  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 PMT, UX 
 
 
 

Created:
 

 2015/10/11 10:25 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Unless PMT is run in debug mode, there is no visible indication as to whether it is encountering network problems (eg proxy server) or is simply downloading a large module or lots of dependencies. 
The current behaviour can leave users chasing non-existing problems (eg network working but slow) or can leave users with an unexpected failure several minutes after starting the command (eg network timeout due to proxy). 
It would be great if PMT could give the user an indication of what it is currently doing as sometimes downloading modules can take several minutes unless invoked with the `--debug` option. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
   

Jira (PUP-5479) segfault with augeas type when changes attribute is too long

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5479 
 
 
 
  segfault with augeas type when changes attribute is too long  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Williams 
 
 
 

Attachment:
 
 kerberos.tar.gz 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-5479) segfault with augeas type when changes attribute is too long

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5479 
 
 
 
  segfault with augeas type when changes attribute is too long  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.2.1 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2015/11/05 6:16 PM 
 
 
 

Environment:
 
 
puppet-student environment 2.33 (from PL education) 
Puppet installed via frictionless installer (curl) from PE 2015.2.1 master 
pl-training classroom installed on master and all agent nodes classified with classroom::course::practitioner 
CentOS release 6.7 (Final) Linux geoff.puppetlabs.vm 2.6.32-573.el6.i686 #1 SMP Thu Jul 23 12:37:35 UTC 2015 i686 i686 i386 GNU/Linux running under vmware-fusion 7.1.2 on macosx 10.10.5 
Packages: [master]root@geoff:~/puppetcode/modules/kerberos/tests # rpm -qa |sort abrt-2.0.8-34.el6.centos.i686 abrt-addon-ccpp-2.0.8-34.el6.centos.i686 abrt-addon-kerneloops-2.0.8-34.el6.centos.i686 abrt-addon-python-2.0.8-34.el6.centos.i686 abrt-cli-2.0.8-34.el6.centos.i686 abrt-libs-2.0.8-34.el6.centos.i686 abrt-python-2.0.8-34.el6.centos.i686 abrt-tui-2.0.8-34.el6.centos.i686 acl-2.2.49-6.el6.i686 acpid-1.0.10-2.1.el6.i686 aic94xx-firmware-30-2.el6.noarch alsa-lib-1.0.22-3.el6.i686 alsa-utils-1.0.22-9.el6_6.i686 apr-1.3.9-5.el6_2.i686 apr-util-1.3.9-3.el6_0.1.i686 apr-util-ldap-1.3.9-3.el6_0.1.i686 at-3.1.10-48.el6.i686 atk-1.30.0-1.el6.i686 atmel-firmware-1.3-7.el6.noarch attr-2.4.44-7.el6.i686 audit-2.3.7-5.el6.i686 audit-libs-2.3.7-5.el6.i686 augeas-libs-1.0.0-10.el6.i686 authconfig-6.1.12-23.el6.i686 avahi-libs-0.6.25-15.el6.i686 b43-fwcutter-012-2.2.el6.i686 b43-openfwwf-5.2-10.el6.noarch basesystem-10.0-4.el6.noarch bash-4.1.2-33.el6.i686 bc-1.06.95-1.el6.i686 bfa-firmware-3.2.23.0-2.el6.noarch bind-libs-9.8.2-0.37.rc1.el6.i686 bind-utils-9.8.2-0.37.rc1.el6.i686 binutils-2.20.51.0.2-5.43.el6.i686 biosdevname-0.6.2-1.el6.i686 blktra

Jira (PUP-5636) Puppet doesn't report missing binaries called through custom type and providers

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5636 
 
 
 
  Puppet doesn't report missing binaries called through custom type and providers  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.3.1 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Attachments:
 

 testcase_unreported_missing_command.tar.gz 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2015/12/22 10:34 PM 
 
 
 

Environment:
 
 
Puppet Enterprise 2015.3.0 running under Docker 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
Overview 
When a custom type and provider attempts to run a program that is missing (or not discoverable in $PATH), Puppet doesn't report that the program is missing. 
Expected result 
   

Jira (FACT-804) cfpropertylist is a missing dependency

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  FACT-804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cfpropertylist is a missing dependency  
 
 
 
 
 
 
 
 
 
 
I ran into this today while trying to test a module with Puppet-Rspec. 
I ended up with the Following Gemfile to workaround the problem: 
 
 
 
 
 
 
source ENV['GEM_SOURCE'] || 'https://rubygems.org' 
 
 
 
 
case RUBY_PLATFORM 
 
 
 
 
when /darwin/ 
 
 
 
 
  gem 'CFPropertyList' 
 
 
 
 
end 
 
 
 
 
gem 'puppet', '4.9.0' 
 
 
 
 
gem 'facter', '2.4.6' 
 
 
 
 
gem 'rubocop', '0.47.1'
 
 
 
 
 
 
 
Perhaps this will be useful to someone else... 
 
 
 
 
 
 
 
 
 
 
 
 

Jira (PUP-7191) Puppet errors when managing non-existent service on AIX

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-7191 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet errors when managing non-existent service on AIX  
 
 
 
 
 
 
 
 
 
 
Solaris 10 (but not 110 also affected, we found this during testing today: 
 
 
 
 
 
 
bash-3.2# /opt/puppetlabs/puppet/bin/puppet apply test.pp 
 
 
 
 
Notice: Compiled catalog for unknown in environment production in 0.09 seconds 
 
 
 
 
Error: Could not start Service[nothere]: Execution of '/usr/sbin/svcadm enable -s nothere' returned 1: svcadm: Pattern 'nothere' doesn't match any instances 
 
 
 
 
Error: /Stage[main]/Main/Service[nothere]/enable: change from false to true failed: Could not start Service[nothere]: Execution of '/usr/sbin/svcadm enable -s nothere' returned 1: svcadm: Pattern 'nothere' doesn't match any instances 
 
 
 
 
Notice: Applied catalog in 0.14 seconds 
 
 
 
 
  
 
 
 
 
bash-3.2# cat test.pp 
 
 
 
 
service { "nothere": 
 
 
 
 
  ensure => stopped, 
 
 
 
 
   

Jira (PUP-7191) Puppet errors when managing non-existent service on AIX

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-7191 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet errors when managing non-existent service on AIX  
 
 
 
 
 
 
 
 
 
 
Moses Mendoza Your right - sorry but I made a mistake in the testcase, it should indeed have been ensure stopped, enable false which DOES work correctly on Solaris 10 (I had the correct testcase on Solaris 11). 
Sorry for the noise. Starting a non-existant service is of-course an error and should always be reported as such 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-7191) Puppet errors when managing non-existent service on AIX

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PUP-7191 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet errors when managing non-existent service on AIX  
 
 
 
 
 
 
 
 
 
 
Moses Mendoza Fix verified on AIX 6.1 - thanks!: 
 
 
 
 
 
 
[0] [AIX] root@pe-aix-61-se:~/tmp # /opt/puppetlabs/puppet/bin/puppet apply test.pp 
 
 
 
 
Notice: Compiled catalog for pe-aix-61-se.delivery.puppetlabs.net in environment production in 0.12 seconds 
 
 
 
 
Notice: Applied catalog in 0.38 seconds 
 
 
 
 
[0] [AIX] root@pe-aix-61-se:~/tmp # cat test.pp  
 
 
 
 
service {"nothere": 
 
 
 
 
  ensure => stopped, 
 
 
 
 
  enable => false, 
 
 
 
 
}
 
 
 
 
 
 
 
I have produced a puppet module at https://github.com/GeoffWilliams/aix_service_fix to hotfix this if required 
 
 
 
 
 
 
 
 
 
 
 
  

Jira (PDOC-164) PDF module documentation

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-164 
 
 
 
  PDF module documentation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 CLI, UX 
 
 
 

Created:
 

 2017/02/24 6:16 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Geoff Williams 
 
 
 
 
 
 
 
 
 
 
It would be a great new feature of Puppet Strings if it could be used to generate a single PDF file documenting an entire module. This would make great leave-behind documentation for consultants who are required to hand over static documentation at the end of engagements. Of course, the HTML output is more useful but this would be a great addition for those who have no choice but to write reports for those who demand them. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

Jira (PDOC-160) strings should be able to process only updated files

[Geoff Williams (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Williams commented on  PDOC-160 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: strings should be able to process only updated files  
 
 
 
 
 
 
 
 
 
 
How about if we just didn't add the date at all? I've created a PR to do this: https://github.com/puppetlabs/puppet-strings/pull/137 
Of course the file are all regenerated but with identical content, so only real changes will need to be committed to git. I've been trying this out locally and it works quite nicely 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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