Jira (PUP-3483) Systemd provider doesn't scan for changed units
Title: Message Title Damon Atkins commented on PUP-3483 Re: Systemd provider doesn't scan for changed units What if a person drops a file in /etc/init.d and starts the service with puppet then latter changes it it again requires a daemon-reload Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3674) confdir not set to /etc/puppet SSL Directories issue on config re-read
Title: Message Title Damon Atkins assigned an issue to Charlie Sharpsteen No update on this for 12 months.. Puppet / PUP-3674 confdir not set to /etc/puppet SSL Directories issue on config re-read Change By: Damon Atkins Assignee: Damon Atkins Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3674) confdir not set to /etc/puppet SSL Directories issue on config re-read
Title: Message Title Damon Atkins commented on PUP-3674 Re: confdir not set to /etc/puppet SSL Directories issue on config re-read Just running the master on the command line no background debug mode 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-3696) Settings in puppet.conf not available in puppet itself
Title: Message Title Damon Atkins commented on PUP-3696 Re: Settings in puppet.conf not available in puppet itself Thanks Guys, given the comments 1) Puppet DB should use the variable, and Puppet should scan for /etc/puppet hard coded in other modules. And fix all of them to use the variable. 2) This is very much hidden https://docs.puppetlabs.com/puppet/3/reference/lang_variables.html#facts-and-built-in-variables Facts and Built-In Variables should have its own page so its easy to spot. Because this page is name lang variables the assumptions is, that its about the syntax of variables names. 3) https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html should reference this new page. And maybe in the first few para say values variable under $settings::name of setting If you wish to close this and open new issues or change the title its up to you. THanks. 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-1640) Provide agnostic mechanism for Hiera Based Data in Modules
Title: Message Title Damon Atkins commented on PUP-1640 Re: Provide agnostic mechanism for Hiera Based Data in Modules We just want a function which looks up a name file in a module data dir. E.g. heira_local_data (relative file name, key). It does not have to do bindings for params. E.g.heira_local_data($osfamily,'packagename') 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-3674) confdir not set to /etc/puppet SSL Directories issue on config re-read
Title: Message Title Damon Atkins commented on PUP-3674 Re: confdir not set to /etc/puppet SSL Directories issue on config re-read puppet config print --section master confdir /prj/master/puppet puppet config print --section master ssldir /prj/master/puppet/ssl puppet config print --section master vardir /prj/master/puppet/var puppet config print --section agent confdir /prj/master/puppet 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-3674) confdir not set to /etc/puppet SSL Directories issue on config re-read
Title: Message Title Damon Atkins updated an issue Puppet / PUP-3674 confdir not set to /etc/puppet SSL Directories issue on config re-read Change By: Damon Atkins Assignee: DamonAtkins CharlieSharpsteen 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-3696) Settings in puppet.conf not available in puppet itself
Title: Message Title
Damon Atkins created an issue
Puppet / PUP-3696
Settings in puppet.conf not available in puppet itself
Issue Type:
Bug
Affects Versions:
PUP 3.7.3
Assignee:
Unassigned
Components:
Puppet Server
Created:
2014/11/24 8:18 PM
Environment:
All
Labels:
puppetdb
Priority:
Normal
Reporter:
Damon Atkins
Here is an example from puppetdb module. It hard codes the location of puppet configuration directory.
./params.pp: $puppet_confdir = '/etc/puppetlabs/puppet' ./params.pp: $puppet_confdir = '/etc/puppet' ./params.pp: $puppet_conf = $ {puppet_confdir}
/puppet.conf
Jira (PUP-3674) confdir not set to /etc/puppet SSL Directories issue on config re-read
Title: Message Title Damon Atkins created an issue Puppet / PUP-3674 confdir not set to /etc/puppet SSL Directories issue on config re-read Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Eric Sorenson Components: Community Created: 2014/11/16 2:47 AM Environment: Linux Priority: Normal Reporter: Damon Atkins It should not be looking in /etc/puppet/ssl as confdir is not set to /etc/puppet Manual States ssldir Where SSL certificates are kept. Default: $confdir/ssl ssldir is not set in puppet.conf Notice: Config file /etc/puppet/puppet.conf changed; triggering re-parse of all config files. Error: Could not set 'directory' on ensure: Permission denied - /etc/puppet/ssl Error: Could not set 'directory' on ensure: Permission denied - /etc/puppet/ssl Wrapped exception: Permission denied - /etc/puppet/ssl Error: /File[/etc/puppet/ssl]/ensure: change from absent to directory failed: Could not set 'directory' on ensure:
Jira (PUP-1157) puppet should support data in modules
Title: Message Title Damon Atkins commented on an issue Re: puppet should support data in modules +1 Private Data in modules. e.g. Instead of if this OS then set this multiple page case statement. Add Comment Puppet / PUP-1157 puppet should support data in modules At present there is a way to store data in modules using the puppet backend for hiera but it is optional and kind of broken. The site hierarchy impacts how the puppet backend behaves which makes it impossible for module authors to supply data in their modules they can rely on I propose a new hiera backend that loads a hierarchy of data from the 'data'... 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-42) Support data and puppet extensions contributed from modules
Title: Message Title Damon Atkins commented on an issue Re: Support data and puppet extensions contributed from modules + Private Data in Modules with a function to look it up. i.e. First Found and Merge, function contains search patterns, and a flag to report an error if no value is found. Add Comment Puppet / PUP-42 Support data and puppet extensions contributed from modules At present there is a way to store data in modules using the puppet backend for hiera but it is optional and kind of broken. The site hierarchy impacts how the puppet backend behaves which makes it impossible for module authors to supply data in their modules they can rely on I propose a new hiera backend that loads a hierarchy of data from the ‘data’ ... 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,
Jira (FACT-428) Should not use the users path by default to find executables
Title: Message Title Damon Atkins commented on an issue Re: Should not use the users path by default to find executables Most people who write secure shell scripts set and export the path in their shell script. People who want consistent results set the PATH in shell script so that they Know which binaries will be used. Your suggest that your want different results between Fred testing and Jim Testing. If an agent dies and some one starts it by hand, it may have a different path to the one it was original started possible producing different results and possible impacting the systems configuration being applied, it will not be obvious to anyone that the difference will be the path when trying to solve why it is not working as expected. Add Comment Facter / FACT-428 Should not use the users path by default to find executables Factor should have a reasonable default path per platform/kernel. Reasons: 1. Puppet/Factor can be started by cron, a user, startup scripts and in each case have a different path and possible a different result is produced. 2. Security, Ensure puppet runs commands expected in the location expected/trusted. e.g. $PATH for example is not under change ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-448) Facter::Core::Execution.execute
Title: Message Title Damon Atkins created an issue Facter / FACT-448 Facter::Core::Execution.execute Issue Type: Improvement Affects Versions: 2.1 Assignee: Adrien Thebo Components: Community Created: 26/Mar/14 5:39 PM Environment: All Labels: trivial Priority: Normal Reporter: Damon Atkins Maybe execute should have a on error extra parameter e.g.: Param 1 Error Reporting to logs, can calling code *ignore all exit status errors and can not execute errors (i.e. behavior like exec) *ignore all exit status errors and report can not execute errors *if can execute report non-0 exit status *report any issues Param 2 Value to set the fact to on error Param 3 Value to set the fact to when no error and no output is return. Param 4 Command etc Ensure factor aborts on out of memory errors or
Jira (FACT-409) Raising errors on non-existent commands too disruptive
Title: Message Title Damon Atkins commented on an issue Re: Raising errors on non-existent commands too disruptive Please ensure in debug mode it still reports command not found, error ignored Add Comment Facter / FACT-409 Raising errors on non-existent commands too disruptive The fix for FACT-651 changed Facter::Core::Execution.exec to raise exceptions by default if the given command does not exist. This is more correct behavior but is quite backwards incompatible. The change will badly break facts written for Facter 1.x and doesn't provide much immediate value to fact developers. Instead of changing the behavior of .exec we s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-409) Raising errors on non-existent commands too disruptive
Title: Message Title Damon Atkins commented on an issue Re: Raising errors on non-existent commands too disruptive Maybe execute should have an option e.g.: *ignore all exit status errors and can not execute errors *ignore all exit status errors and report can not execute errors *if can execute report non-0 exit status *report any issues Ensure factor aborts on out of memory errors or similar, and these facts are not sent back to puppet master. Last thing we want is when a system is broken for puppet to produce a different catalog. Add Comment Facter / FACT-409 Raising errors on non-existent commands too disruptive The fix for FACT-651 changed Facter::Core::Execution.exec to raise exceptions by default if the given command does not exist. This is more correct behavior but is quite backwards incompatible. The change will badly break facts written for Facter 1.x and doesn't provide much immediate value to fact developers. Instead of changing the behavior of .exec we s... 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
Jira (FACT-428) Should not use the users path by default to find executables
Title: Message Title Damon Atkins created an issue Facter / FACT-428 Should not use the users path by default to find executables Issue Type: Bug Affects Versions: 2.0.1, 2.1, 2.0.2 Assignee: Adrien Thebo Components: Community Created: 24/Mar/14 6:59 PM Environment: All Platforms Priority: Normal Reporter: Damon Atkins Factor should have a reasonable default path per platform/kernel. Reasons: 1. Puppet/Factor can be started by cron, a user, startup scripts and in each case have a different path and possible a different result is produced. 2. Security, Ensure puppet runs commands expected in the location expected/trusted. e.g. $PATH for example is not under change control and may contain '.' Factor should also warn if . is found in the path it is using. Add option --use-my-path to use PATH from environment instead of puppet.conf
Jira (FACT-408) facter-2.0.1.rc2 Solaris lspci command not found
Title: Message Title Damon Atkins updated an issue Facter / FACT-408 facter-2.0.1.rc2 Solaris lspci command not found Change By: Damon Atkins Assignee: DamonAtkins AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-408) facter-2.0.1.rc2 Solaris lspci command not found
Title: Message Title Damon Atkins created an issue Facter / FACT-408 facter-2.0.1.rc2 Solaris lspci command not found Issue Type: Bug Affects Versions: 2.0.1 Assignee: Adrien Thebo Components: Community Created: 21/Mar/14 4:59 AM Environment: Solaris 11 Priority: Critical Reporter: Damon Atkins The follow error says it all /var/ruby/1.8/gem_home/bin/facter -p Could not load Puppet: can't activate facter (~ 1.6, runtime) for [puppet-3.4.3], already activated facter-2.0.1.rc2 for [] Could not retrieve fact='virtual', resolution='anonymous': Could not execute 'lspci 2/dev/null': command not found Could not retrieve fact='virtual', resolution='anonymous': Could not execute 'lspci 2/dev/null': command not found Could not retrieve fact='virtual', resolution='anonymous': Could not execute 'lspci 2/dev/null': command not found architecture = i86pc bios_release_date = 07/13/2006 bios_vendor = American Megatrends Inc. bios_version = System Version domain = oz facterversion = 2.0.1-rc2 fqdn = beta.oz hardwareisa = i386 hardwaremodel = i86pc hostname = beta id = root interfaces = lo0,yge0 ipaddress = 192.168.53.1 ipaddress_lo0 = 127.0.0.1 ipaddress_yge0 =
Jira (FACT-408) facter-2.0.1.rc2 Solaris lspci command not found
Title: Message Title Damon Atkins updated an issue Facter / FACT-408 facter-2.0.1.rc2 Solaris lspci command not found Change By: Damon Atkins Thefollowerrorsaysitall/var/ruby/1.8/gem_home/bin/facter-pCouldnotloadPuppet:can'tactivatefacter(~1.6,runtime)for[puppet-3.4.3],alreadyactivatedfacter-2.0.1.rc2for[]Couldnotretrievefact='virtual',resolution='anonymous':Couldnotexecute'lspci2/dev/null':commandnotfoundCouldnotretrievefact='virtual',resolution='anonymous':Couldnotexecute'lspci2/dev/null':commandnotfoundCouldnotretrievefact='virtual',resolution='anonymous':Couldnotexecute'lspci2/dev/null':commandnotfoundarchitecture=i86pcbios_release_date=07/13/2006bios_vendor=AmericanMegatrendsInc.bios_version=SystemVersiondomain= oz X facterversion=2.0.1-rc2fqdn= beta X . oz X hardwareisa=i386hardwaremodel=i86pchostname= beta X id=rootinterfaces=lo0,yge0ipaddress=192.168. 53 X .1ipaddress_lo0=127.0.0.1ipaddress_yge0=192.168. 53 X .1is_virtual=truekernel=SunOSkernelmajversion=11.0kernelrelease=5.11kernelversion=11.0macaddress=00:15:f2:39:5e:c4macaddress_yge0=00:15:f2:39:5e:c4manufacturer=Systemmanufacturermemoryfree=221.54MBmemoryfree_mb=221.54memorysize=3.50GBmemorysize_mb=3584.00mtu_lo0=8232mtu_yge0=1500netmask=255.255.255.0netmask_lo0=255.0.0.0netmask_yge0=255.255.255.0network_lo0=127.0.0.0network_yge0=192.168. 53 X .0operatingsystem=Solarisoperatingsystemrelease=5.11osfamily=Solarispath=/usr/sbin:/usr/binphysicalprocessorcount=1processor0=Intel(r)Pentium(r)DCPU2.80GHzprocessor1=Intel(r)Pentium(r)DCPU2.80GHzprocessorcount=2productname=SystemProductNameps=ps-efrubysitedir=/usr/ruby/1.8/lib/ruby/site_ruby/1.8rubyversion=1.8.7serialnumber=SystemSerialNumbersshdsakey=removedsshfp_dsa=removedsshfp_rsa=removedsshrsakey=removedswapfree=1.56GBswapfree_mb=1599.97swapsize=1.75GBswapsize_mb=1791.00timezone=ESTtype=0x3(desktop)uniqueid=removeduptime=133daysuptime_days=133uptime_hours=3214uptime_seconds=11571180uuid=removedzfs_version=5zone_global_brand=solariszone_global_id=0zone_global_iptype=sharedzone_global_name=globalzone_global_path=/zone_global_status=runningzone_global_uuid=zonename=globalzones=1zpool_version=33 Add Comment
Jira (FACT-408) facter-2.0.1.rc2 Solaris lspci command not found
Title: Message Title
Damon Atkins commented on an issue
Re: facter-2.0.1.rc2 Solaris lspci command not found
It Solaris 11 on direct H/W, no visualisation at all. lspci is a Linux command. It should not be run on a Solaris system at all. Their seems to be a lack of OS checks {Facter.value(:kernel)}
before commands are executed. This should be consider dangerous as puppet runs commands as root.
Their needs to be a lot more of if Facter.value(:kernel) checks in the code before executing commands... You can not guarantee that a command is safe to execute on all OS. It also should contain the full path or set the path before executing.
Is their a check to see if . is in a path... See facter-2.0.1.rc2/lib/facter/util/virtual.rb
Puppet/Factor/etc should be audited to see if it is executing valid commands for an OS.
It might be worth running Solaris x86 in a virtual systems to see this issue as I assume it will happen even if the system is Virtual or Physical. Cheers
Add Comment
Facter / FACT-408
facter-2.0.1.rc2 Solaris lspci command not found
The follow error says it all /var/ruby/1.8/gem_home/bin/facter -p Could not load Puppet: can't activate facter (~ 1.6, runtime) for [puppet-3.4.3], already activated facter-2.0.1.rc2 for [] Could not retrieve fact='virtual', resolution='anonymous': Could not execute 'lspci 2/dev/null': command not found Could not retrieve fact='virtual', resolut...
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Damon Atkins commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
modulepath also needs OS flavour e.g. solaris, linux, aix, windows etc. You could do osfamily
manifest = $confdir/manifest/$environment modulepath = $confdir/modules/$environment:$confdir/modules/$environment/$osflavour:configdir/modules/$osflavour:$confdir/modules/common Note: $osfamily is to specific... i.e. RHEL, OEL, Deb etc are 97% the same so linux would be best to describe them as a set.
If you have windows systems and linux systems in the same environment unix code will try to run on windows system?
Add Comment
Puppet / PUP-1596
Make modulepath, manifest, and config_version configurable per-environment
In order to make the new environment system fully usable, the default modulepath, manifest, and config_version needs to be overridable on a per-environment basis. This is possible in the current system with the environment stanzas and similar flexibility needs to be retained in the directory environments. Each environment should optionally have an {{en...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
