Jira (PUP-1121) Node regex beginning with dash results in invalid tag
Title: Message Title Zachary Stern assigned an issue to Unassigned Puppet / PUP-1121 Node regex beginning with dash results in invalid tag Change By: Zachary Stern Assignee: DavidGwilliam 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 (PDB-1003) You shall not pass! error could be more informative
Title: Message Title Zachary Stern commented on PDB-1003 Re: You shall not pass! error could be more informative Worth noting that currently puppetdb ssl-setup -f breaks load-balanced PuppetDBs since they need to share a single SSL cert and that command puts the agent cert in place. 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-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title
Zachary Stern commented on PUP-3985
Re: With `storeconfigs = false` there are no warnings or errors about exported resources
Alright, so in puppet.conf on my master, I have storeconfigs == false
[root@pe-371-master ~]# puppet master --configprint storeconfigs
false
Exported resource in site.pp:
[root@pe-371-master ~]# tail /etc/puppetlabs/puppet/environments/production/manifests/site.pp -n 2
@@notify { 'foo': }
Notify | |
Restart pe-puppetserver for santiy:
[root@pe-371-master ~]# service pe-puppetserver restart
Stopping pe-puppetserver: [ OK ]
Jira (PUP-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title Zachary Stern created an issue Puppet / PUP-3985 With `storeconfigs = false` there are no warnings or errors about exported resources Issue Type: Bug Assignee: Unassigned Created: 2015/02/09 2:59 PM Priority: Normal Reporter: Zachary Stern If you set storeconfigs = false on the master, exported resources will not function, but there are no warnings or errors about this anywhere that I can see, even when compiling a manifest that exports resources. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1085) `puppetdb ssl-setup` should allow arbitrary certnames
Title: Message Title Zachary Stern created an issue PuppetDB / PDB-1085 `puppetdb ssl-setup` should allow arbitrary certnames Issue Type: New Feature Assignee: Unassigned Created: 2014/12/29 10:40 AM Priority: Normal Reporter: Zachary Stern Currently, in order to load balance PuppetDB in PE, you need to configure your multiple PuppetDBs to use a single shared certificate. The puppet_enterprise::profile::puppetdb class including with PE allows you to specify this alternate common cert to use instead of the PuppetDB node's agent cert. However, if you later use puppetdb ssl-setup, which is very commonly used in troubleshooting scenarios, this will always be overwritten, due to the way the command determines what cert to use: mycertname=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir --configprint certname` orig_public_file=`puppet master --confdir=$agent_confdir --vardir=$agent_vardir --configprint hostcert`
Jira (PDB-1085) `puppetdb ssl-setup` should allow arbitrary certnames
Title: Message Title Zachary Stern commented on PDB-1085 Re: `puppetdb ssl-setup` should allow arbitrary certnames Brett Gray you might care about this. 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 (PDB-1085) `puppetdb ssl-setup` should allow arbitrary certnames
Title: Message Title
Zachary Stern updated an issue
PuppetDB / PDB-1085
`puppetdb ssl-setup` should allow arbitrary certnames
Change By:
Zachary Stern
Currently,inordertoloadbalancePuppetDBinPE,youneedtoconfigureyourmultiplePuppetDBstouseasinglesharedcertificate.The{{puppet_enterprise::profile::puppetdb}}class including included withPEallowsyoutospecifythisalternatecommoncerttouseinsteadofthePuppetDBnode'sagentcert.However,ifyoulateruse{{puppetdbssl-setup}},whichis*very*commonlyusedintroubleshootingscenarios,thiswillalwaysbeoverwritten,duetothewaythecommanddetermineswhatcerttouse:{code}mycertname=`puppetmaster--confdir=$agent_confdir--vardir=$agent_vardir--configprintcertname`orig_public_file=`puppetmaster--confdir=$agent_confdir--vardir=$agent_vardir--configprinthostcert`orig_private_file=`puppetmaster--confdir=$agent_confdir--vardir=$agent_vardir--configprinthostprivkey`orig_ca_file=`puppetmaster--confdir=$agent_confdir--vardir=$agent_vardir--configprintlocalcacert`{code}That'sdefinitelygoingtomaketroubleshootingPuppetDBissuescumbersomeforLEIcustomers.Onepotentialremediationcouldbetoincludeacommandlineflagforspecifyinganarbitrary{{certname}},somethinglike:{{puppetdbssl-setup--certnamefoobaz}}
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
Jira (PDB-1085) `puppetdb ssl-setup` should allow arbitrary certnames
Title: Message Title Zachary Stern commented on PDB-1085 Re: `puppetdb ssl-setup` should allow arbitrary certnames Kenneth Barber do you have feelings about this? 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 (HI-14) Allow access to structured data
Title: Message Title Zachary Stern commented on HI-14 Re: Allow access to structured data It's important (probably most important) that this include the hierarchy in hiera.yaml itself, as well as the data files. 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 (PDB-1003) You shall not pass! error could be more informative
Title: Message Title Zachary Stern created an issue PuppetDB / PDB-1003 You shall not pass! error could be more informative Issue Type: Improvement Assignee: Unassigned Created: 30/Oct/14 12:20 PM Labels: support customer Priority: Normal Reporter: Zachary Stern While entertaining, it would nice if the You shall not pass! error provided useful feedback. Something like: Is your master's certname listed in PuppetDB's cetificate-whitelist file? Also, if you recently re-certed your PuppetDB node, you may need to run puppetdb ssl-setup -f and then restart PuppetDB.
Jira (PUP-3535) certificate_status endpoint is slow
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3535 certificate_status endpoint is slow Change By: Zachary Stern Security: Internal 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-1966) It should be harder to revoke your CA cert
Title: Message Title
Zachary Stern commented on an issue
Re: It should be harder to revoke your CA cert
Any movement on this?
Even just a chattr +i on the ca cert would be great.
Add Comment
Puppet / PUP-1966
It should be harder to revoke your CA cert
{{puppet cert revoke ca}} Boom, dead install. Maybe my nodes start with the letters ca. Maybe I hit enter too quickly. Who knows? We should at least prompt for a do you really want to do this?.
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-3451) Puppet generates metrics that extend past 6 decimal places under some circumstances
Title: Message Title Zachary Stern created an issue Puppet / PUP-3451 Puppet generates metrics that extend past 6 decimal places under some circumstances Issue Type: Bug Affects Versions: PUP 3.4.3 Assignee: Unassigned Created: 13/Oct/14 12:24 PM Environment: RHEL 6.5 + PE 3.2.1 Master AIX 7.1 + PE 3.2.1 Agent Priority: Normal Reporter: Zachary Stern Puppet generally produces metrics that only extend to 6 decimal places inside of a report. You can verify this by turning on stored reports, performing a few puppet runs, and examining the reports. Note that all metrics extend to a precision of 6 decimal places. However, occasionally, this is not the case. We've seen two cases where runs produce reports with data like the following. values:
Jira (PUP-3451) Puppet generates metrics that extend past 6 decimal places under some circumstances
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3451 Puppet generates metrics that extend past 6 decimal places under some circumstances Change By: Zachary Stern Labels: customersupport 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-3451) Puppet generates metrics that extend past 6 decimal places under some circumstances
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-3451
Puppet generates metrics that extend past 6 decimal places under some circumstances
Change By:
Zachary Stern
Puppetgenerallyproducesmetricsthatonlyextendto6decimalplacesinsideofareport.Youcanverifythisbyturningonstoredreports,performingafewpuppetruns,andexaminingthereports.Notethatallmetricsextendtoaprecisionof6decimalplaces.However,occasionally,thisisnotthecase.We'veseentwocaseswhererunsproducereportswithdatalikethefollowing.{code}values:--schedule-Schedule-0.002184--package-Package-8.6160649--schedo-Schedo-0.238365--mount-Mount-0.006872--no-No-2.92048498--file_line-Fileline-0.016742--file-File-11.4921386--vmo-Vmo-0.606267--usersec-Usersec-1.211225--exec-Exec-4.037464{code}Notethatsomeofthemetricsextendpast6decimalplaces.Normally,Icanperformpuppetrunsallday , andneverseedecimalplacesgobeyond6.
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-3261) puppet doc passes files to rdoc too agressively
Title: Message Title
Zachary Stern commented on an issue
Re: puppet doc passes files to rdoc too agressively
Charlie Sharpsteen notifying you as asked.
Add Comment
Puppet / PUP-3261
puppet doc passes files to rdoc too agressively
Puppet doc passes files to rdoc that it shouldn't. E.g. the existence of {{/opt/puppet/share/puppet/modules/pe_razor/bin}} in puppet enterprise results in: {code} [root@pe-323-master ~]# puppet doc --all --outputdir=/tmp/puppet-doc --mode rdoc --manifestdir=/etc/puppetlabs/puppet/environments/production/manifests/ Before reporting this, could you ...
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-3261) puppet doc passes files to rdoc too agressively
Title: Message Title Zachary Stern created an issue Puppet / PUP-3261 puppet doc passes files to rdoc too agressively Issue Type: Bug Assignee: Unassigned Created: 16/Sep/14 11:43 AM Priority: Normal Reporter: Zachary Stern Puppet doc passes files to rdoc that it shouldn't. E.g. the existence of /opt/puppet/share/puppet/modules/pe_razor/bin in puppet enterprise results in: [root@pe-323-master ~]# puppet doc --all --outputdir=/tmp/puppet-doc --mode rdoc --manifestdir=/etc/puppetlabs/puppet/environments/production/manifests/ Before reporting this, could you check that the file you're documenting has proper syntax: /opt/puppet/bin/ruby -c /opt/puppet/share/puppet/modules/pe_razor/bin/git-log-to-changelog RDoc is not a full Ruby parser and will fail when fed invalid ruby programs. The internal error was: (Errno::ENOENT) No such file or directory - dummy.rb Error: Could not generate documentation: No such file or directory - dummy.rb We should limit what we pass to rdoc strictly to the appropriate directories. E.g. at least manifests, possibly templates, possibly lib. Add Comment
Jira (PUP-3253) Allow excluded directories with puppet doc
Title: Message Title Zachary Stern created an issue Puppet / PUP-3253 Allow excluded directories with puppet doc Issue Type: New Feature Assignee: Unassigned Created: 15/Sep/14 3:27 PM Priority: Normal Reporter: Zachary Stern Sometimes, I may want to generate documentation for all my puppet code, with the exception of a few directories. For example, the pe_accounts module contains an examples directory that contains multiple example site.pp files, which convinces rdoc that their are duplicate node definitions. However, there aren't, because the examples directory isn't in the autoloader layout. To that end, it would be useful to be able to exclude arbitrary directories. Add Comment This message was sent by
Jira (PUP-2907) Regression when pluginsyncing external facts on Windows
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2907 Regression when pluginsyncing external facts on Windows Change By: Zachary Stern Labels: customersupport 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-3123) One broken exported/virtual resource causes all of the same type to fail
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3123 One broken exported/virtual resource causes all of the same type to fail Change By: Zachary Stern Labels: customersupport 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-3123) One broken exported/virtual resource causes all of the same type to fail
Title: Message Title
Zachary Stern created an issue
Puppet / PUP-3123
One broken exported/virtual resource causes all of the same type to fail
Issue Type:
Bug
Assignee:
Unassigned
Created:
21/Aug/14 11:56 AM
Priority:
Normal
Reporter:
Zachary Stern
@sshkey { ${::fqdn}_dsa:
host_aliases = [$::fqdn, $::hostname],
type = dsa,
key = $::fdslkfjsdlfkj,
}
@sshkey { ${::fqdn}_rsa:
host_aliases = [$::fqdn, $::hostname],
type = rsa,
key = $::sshrsakey,
}
@notify { 'blah':}
Sshkey | |
Notify | |
[root@pe-331-master ssh]# /opt/puppet/bin/puppet apply /vagrant/junk/foo.pp
Notice: Compiled catalog for pe-331-master.puppetdebug.vlan in environment production in 0.10 seconds
Notice: /Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_dsa]/ensure: created
Error: /Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_dsa]: Could not evaluate: Field 'key' is required
Notice: /Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]/ensure: created
Error: /Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]: Could not evaluate: Field 'key' is required
Notice: blah
Notice: /Stage[main]/Main/Notify[blah]/message: defined 'message' as 'blah'
Notice: Finished catalog run in 0.17 seconds
Note that {Could not evaluate: Field 'key' is required}
was still thrown evne for the rsa key resource, even though the key parameter is clearly supplied.
If I simply comment out the broken resource:
Jira (PUP-3123) One broken exported/virtual resource causes all of the same type to fail
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3123 One broken exported/virtual resource causes all of the same type to fail Change By: Zachary Stern Affects Version/s: 3.6.2 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-3123) One broken exported/virtual resource causes all of the same type to fail
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-3123
One broken exported/virtual resource causes all of the same type to fail
Change By:
Zachary Stern
{code}@sshkey{${::fqdn}_dsa:host_aliases=[$::fqdn,$::hostname],type=dsa,key=$::fdslkfjsdlfkj,}@sshkey{${::fqdn}_rsa:host_aliases=[$::fqdn,$::hostname],type=rsa,key=$::sshrsakey,}@notify{'blah':}Sshkey||Notify||{code}{code}[root@pe-331-masterssh]#/opt/puppet/bin/puppetapply/vagrant/junk/foo.ppNotice:Compiledcatalogforpe-331-master.puppetdebug.vlaninenvironmentproductionin0.10secondsNotice:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_dsa]/ensure:createdError:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_dsa]:Couldnotevaluate:Field'key'isrequiredNotice:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]/ensure:createdError:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]:Couldnotevaluate:Field'key'isrequiredNotice:blahNotice:/Stage[main]/Main/Notify[blah]/message:defined'message'as'blah'Notice:Finishedcatalogrunin0.17seconds{code}Notethat{ { Couldnotevaluate:Field'key'isrequired} } wasstillthrown evne even forthersakeyresource,eventhoughthekeyparameterisclearlysupplied.IfIsimplycommentoutthebrokenresource:{code}#@sshkey{${::fqdn}_dsa:#host_aliases=[$::fqdn,$::hostname],#type=dsa,#key=$::fdslkfjsdlfkj,#}@sshkey{${::fqdn}_rsa:host_aliases=[$::fqdn,$::hostname],type=rsa,key=$::sshrsakey,}@notify{'blah':}Sshkey||Notify||{code}thentheworkingoneappliesjustfine:{code}[root@pe-331-masterssh]#/opt/puppet/bin/puppetapply/vagrant/junk/foo.ppNotice:Compiledcatalogforpe-331-master.puppetdebug.vlaninenvironmentproductionin0.10secondsNotice:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]/ensure:createdNotice:blahNotice:/Stage[main]/Main/Notify[blah]/message:defined'message'as'blah'Notice:Finishedcatalogrunin0.16seconds{code}Soclearly,I'msuccessfullypassinginthekeyparameter.Thegoodvirtualresourceisbeingtaintedbythebadone.Thisaffectsexportedresourcesaswell.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3123) One broken exported/virtual resource causes all of the same type to fail
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-3123
One broken exported/virtual resource causes all of the same type to fail
Change By:
Zachary Stern
{code}@sshkey{${::fqdn}_dsa:host_aliases=[$::fqdn,$::hostname],type=dsa,key=$::fdslkfjsdlfkj,}@sshkey{${::fqdn}_rsa:host_aliases=[$::fqdn,$::hostname],type=rsa,key=$::sshrsakey,}@notify{'blah':}Sshkey||Notify||{code}{code}[root@pe-331-masterssh]#/opt/puppet/bin/puppetapply/vagrant/junk/foo.ppNotice:Compiledcatalogforpe-331-master.puppetdebug.vlaninenvironmentproductionin0.10secondsNotice:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_dsa]/ensure:createdError:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_dsa]:Couldnotevaluate:Field'key'isrequiredNotice:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]/ensure:createdError:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]:Couldnotevaluate:Field'key'isrequiredNotice:blahNotice:/Stage[main]/Main/Notify[blah]/message:defined'message'as'blah'Notice:Finishedcatalogrunin0.17seconds{code}Notethat{Couldnotevaluate:Field'key'isrequired}wasstillthrownevneforthersakeyresource,eventhoughthekeyparameterisclearlysupplied.IfIsimplycommentoutthebrokenresource:{code}#@sshkey{${::fqdn}_dsa:#host_aliases=[$::fqdn,$::hostname],#type=dsa,#key=$::fdslkfjsdlfkj,#}@sshkey{${::fqdn}_rsa:host_aliases=[$::fqdn,$::hostname],type=rsa,key=$::sshrsakey,}@notify{'blah':}Sshkey||Notify||{code}thentheworkingoneappliesjustfine:{code}[root@pe-331-masterssh]#/opt/puppet/bin/puppetapply/vagrant/junk/foo.ppNotice:Compiledcatalogforpe-331-master.puppetdebug.vlaninenvironmentproductionin0.10secondsNotice:/Stage[main]/Main/Sshkey[pe-331-master.puppetdebug.vlan_rsa]/ensure:createdNotice:blahNotice:/Stage[main]/Main/Notify[blah]/message:defined'message'as'blah'Notice:Finishedcatalogrunin0.16seconds{code}Soclearly,I'msuccessfullypassinginthekeyparameter.Thegoodvirtualresourceisbeingtaintedbythebadone. Thisaffectsexportedresourcesaswell.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3078) Virtual and Exported Resources Should Validate at Declaration
Title: Message Title
Zachary Stern created an issue
Puppet / PUP-3078
Virtual and Exported Resources Should Validate at Declaration
Issue Type:
Improvement
Assignee:
Unassigned
Created:
18/Aug/14 4:25 PM
Priority:
Normal
Reporter:
Zachary Stern
Virtual and exported resources aren't validated when they are declared, and so problems aren't visible until they're collected.
E.g.:
[root@mgtm6e8juxq8e3n ~]# cat foo.pp
@sshkey { ${::fqdn}_dsa:
host_aliases = [$::fqdn, $::hostname],
type = dsa,
key = $::fdslkfjsdlfkj,
}
[root@mgtm6e8juxq8e3n ~]# puppet apply foo.pp
Notice: Compiled catalog for mgtm6e8juxq8e3n.delivery.puppetlabs.net in environment production in 0.08 seconds
Notice: Finished catalog run in 0.03 seconds
And now let's collect it:
[root@mgtm6e8juxq8e3n ~]# cat foo.pp
@sshkey { ${::fqdn}_dsa:
host_aliases = [$::fqdn, $::hostname],
type = dsa,
key = $::fdslkfjsdlfkj,
}
Sshkey | |
[root@mgtm6e8juxq8e3n ~]# puppet apply foo.pp
Notice: Compiled catalog for mgtm6e8juxq8e3n.delivery.puppetlabs.net in environment production in 0.08 seconds
Notice: /Stage[main]/Main/Sshkey[mgtm6e8juxq8e3n.delivery.puppetlabs.net_dsa]/ensure: created
Error: /Stage[main]/Main/Sshkey[mgtm6e8juxq8e3n.delivery.puppetlabs.net_dsa]: Could not evaluate: Field 'key' is required
Notice: Finished catalog run in 0.02 seconds
The same is true for exported resources. Debugging these sorts of issues would be far easier if the resources were validated
Jira (PUP-3078) Virtual and Exported Resources Should Validate at Declaration
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3078 Virtual and Exported Resources Should Validate at Declaration Change By: Zachary Stern Labels: customersupport 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-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-3062
The default unit for `splaylimit` should not be seconds.
Change By:
Zachary Stern
{{runinterval}}defaultstominutes,and{{splaylimit}}defaultsto{{runinterval}}What'smore,Ican'timagineeverwantingtosplaybysecondsinsteadofminutes.I'mnotopposedtotheoptionexisting,butitshouldnotbethedefault units unit .I'veseenthisconfuseatleastonecustomer,anditcertainlytookmetimetonoticethisinthedocs.OfcourseIshouldhavereadthemmoreclosely,butthisisstillconfusingonitsface.
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-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. Change By: Zachary Stern Labels: customersupport 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-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title
Zachary Stern commented on an issue
Re: The default unit for `splaylimit` should not be seconds.
The obvious caveat here would be that this change would break backwards compatibility. If this request is accepted it should be at some major release bump.
Add Comment
Puppet / PUP-3062
The default unit for `splaylimit` should not be seconds.
{{runinterval}} defaults to minutes, and {{splaylimit}} defaults to {{runinterval}} What's more, I can't imagine ever wanting to splay by seconds instead of minutes. I'm not opposed to the option existing, but it should not be the default unit. I've seen this confuse at least one customer, and it certainly took me time to notice this in the docs
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
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Zachary Stern created an issue Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. Issue Type: Improvement Assignee: Unassigned Created: 14/Aug/14 2:49 PM Priority: Normal Reporter: Zachary Stern runinterval defaults to minutes, and splaylimit defaults to runinterval What's more, I can't imagine ever wanting to splay by seconds instead of minutes. I'm not opposed to the option existing, but it should not be the default units. I've seen this confuse at least one customer, and it certainly took me time to notice this in the docs. Of course I should have read them more closely, but this is still confusing on its face. Add Comment This message was sent by Atlassian
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Zachary Stern commented on an issue Re: a metaparameter to control the timeout of that resource evaluation/application, along with a default value. +1 to Charlie's idea. As a sysadmin I would expect most resources to just work most of the time, and to have perhaps one or two that misbehave, that I could set a timeout on. Add Comment Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I had some service (iscsid) which hung for ever for some reason (missing config file), when stopping it via `service iscsid stop`. As puppet should stop that service, puppet hung as well. Over days... I think it's pretty reasonable to expect services to be stopped after some time (like 10 minutes?) and if they didn't return so far, give up (and kill... 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
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Zachary Stern commented on an issue Re: a metaparameter to control the timeout of that resource evaluation/application, along with a default value. Eric Sorenson what are your thoughts on this? I would expect this to be a common problem with customers attempting to install pip packages or gems that involve compiling native extensions. Add Comment Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I had some service (iscsid) which hung for ever for some reason (missing config file), when stopping it via `service iscsid stop`. As puppet should stop that service, puppet hung as well. Over days... I think it's pretty reasonable to expect services to be stopped after some time (like 10 minutes?) and if they didn't return so far, give up (and kill... 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
Jira (PUP-2990) Puppet should support forking processes to apply catalogs as a specific user
Title: Message Title Zachary Stern created an issue Puppet / PUP-2990 Puppet should support forking processes to apply catalogs as a specific user Issue Type: New Feature Assignee: Unassigned Created: 29/Jul/14 4:23 PM Labels: support customer Priority: Normal Reporter: Zachary Stern Currently, there's no built in functionality for realizing specific resources or classes as a specific user. It would be useful in some scenarios to be able to do this. One possible solution would be to: Add a new meta-parameter, perhaps for use with the resources resource, called run_user or similar, who's default value is root. If specified, everything within the relevant scope would be run as the specified user. Fork a process/thread on the agent during the puppet run that realizes the relevant resources as the non-root user and captures the output and any errors.
Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Zachary Stern created an issue Puppet / PUP-2958 Rapid-fire puppet runs cause race condition with SSL data Issue Type: Bug Assignee: Unassigned Created: 21/Jul/14 2:16 PM Priority: Normal Reporter: Zachary Stern It appears that two rapid-fire puppet runs can cause a race condition of some kind when: Puppet requests a certificate from the master. An additional puppet run is triggered immediately, before the signed certificate is received. New private keys are generated - but the master has already received the original CSR. The master continuously returns the original certificate, which does not match the newly generated private keys / csr on the agent, from the second puppet run. This shouldn't be possible, but I've seen it demonstrated by a customer. It's also possible I'm misinterpreting exactly what is happening. /cc Reid Vandewiele for comment - he's seen the bug in the past but couldn't nail it down cohesively.
Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2958 Rapid-fire puppet runs cause race condition with SSL data Change By: Zachary Stern Labels: customersupport 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-2868) `puppet config print` confusing for users
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Zachary Stern Assignee: ZacharyStern AndyParker 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-2868) `puppet config print` confusing for users
Title: Message Title
Zachary Stern commented on an issue
Re: `puppet config print` confusing for users
+1 to what Nick said.
People run puppet config print server and expect to get the value of server they've set in [main] or [agent], and get back puppet. They then start wondering why their configuration in puppet.conf isn't taking effect, when in fact it is, and they're simply using puppet config print wrong.
Add Comment
Puppet / PUP-2868
`puppet config print` confusing for users
{{puppet config print}} doesn't require a {{\-\-section}} to be specified and doesn't inform the user what section of the config file it is showing the value for. Users then get unexpected information from the command. The command needs to change in some way to make it clear what sections the information is coming from and provide a good way to request...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To
Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title
Zachary Stern commented on an issue
Re: Certname must be lowercase error not helpful
Eric Sorenson I can, but having read the redmine ticket top to bottom several times, I'm not quite sure what it should say. I get that the CA, currently, doesn't support mixed-case certnames, but I'm not quite sure what we'd want to give as the reason.
Add Comment
Puppet / PUP-2551
Certname must be lowercase error not helpful
Currently if you set a non lowercase certname you get this error: {code} Error: Could not initialize global default settings: Certificate names must be lower case; see #1168 {code} Its not terribly helpful for a couple reasons. # We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say oh right, redmine, duh. # #1168 i...
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
Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title
Zachary Stern commented on an issue
Re: Certname must be lowercase error not helpful
I think in a case like this, where it's something you absolutely should be able to do (e.g. DNS names are not case sensitive, and on Windows machines, hostnames are by default upper case), then yes.
In general, perhaps not.
Add Comment
Puppet / PUP-2551
Certname must be lowercase error not helpful
Currently if you set a non lowercase certname you get this error: {code} Error: Could not initialize global default settings: Certificate names must be lower case; see #1168 {code} Its not terribly helpful for a couple reasons. # We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say oh right, redmine, duh. # #1168 i...
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
Jira (PUP-2723) Better logging around ENC timeouts
Title: Message Title Zachary Stern created an issue Puppet / PUP-2723 Better logging around ENC timeouts Issue Type: Bug Assignee: Unassigned Created: 03/Jun/14 1:09 PM Priority: Normal Reporter: Zachary Stern When there's a timeout of the ENC script, an error shows up on the agent side, but nothing on the master. By putting in an ENC script that just waits for 500 seconds, I was able to produce this: ``` [root@pe-313-master ~]# puppet agent --test Error: Failed to apply catalog: Timeout::Error ``` However, there was no corresponding error in the master logs. If the master tries to run the ENC script, but times out, shouldn't there be an error of some kind logged on the master side? Add Comment This
Jira (PUP-2723) Better logging around ENC timeouts
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-2723
Better logging around ENC timeouts
Change By:
Zachary Stern
Whenthere'satimeoutoftheENCscript,anerrorshowsupontheagentside,butnothingonthemaster.ByputtinginanENCscriptthatjustwaitsfor500seconds,Iwasabletoproducethis: ``` {code} [root@pe-313-master~]#puppetagent--testError:Failedtoapplycatalog:Timeout::Error ``` {code} However,therewasnocorrespondingerrorinthemasterlogs.IfthemastertriestoruntheENCscript,buttimesout,shouldn'ttherebeanerrorofsomekindloggedonthemasterside?
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-449) Facter is very slow in presence of large number of network interfaces
Title: Message Title Zachary Stern updated an issue Facter / FACT-449 Facter is very slow in presence of large number of network interfaces Change By: Zachary Stern Labels: customersupport 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-2551) Certname must be lowercase error not helpful
Title: Message Title
Zachary Stern commented on an issue
Re: Certname must be lowercase error not helpful
Would it be possible in the interim to simply provide a better error message, without doing any actual fixing of the problem in the current CA?
Add Comment
Puppet / PUP-2551
Certname must be lowercase error not helpful
Currently if you set a non lowercase certname you get this error: {code} Error: Could not initialize global default settings: Certificate names must be lower case; see #1168 {code} Its not terribly helpful for a couple reasons. # We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say oh right, redmine, duh. # #1168 i...
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-1140) improve invalid parameter error message from create resources
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-1140
improve invalid parameter error message from create resources
Change By:
Zachary Stern
Theerrormessagefromcreate_resources()whenaninvalidparameterisgivenisalittledifficulttounderstand.ForexampleifIhavesomeHieradatalikethis(wherethe'enable'parameterismis-speltas'enabled'): {code} service:puppet:enabled:true {code} Thenitwouldbemorehelpfuliftheerrormessagelookedsomethinglikethis: {{ Invalidparameterenabledforresourcetype'service'viacreate_resources()onnodefoo }} Insteadofwhatitdoesnow: {{ Invalidparameterenabledonnodefoo }}
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-1157) puppet should support data in modules
Title: Message Title Zachary Stern updated an issue Puppet / PUP-1157 puppet should support data in modules Change By: Zachary Stern Labels: customer redmine 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-42) Support data and puppet extensions contributed from modules
Title: Message Title Zachary Stern updated an issue Puppet / PUP-42 Support data and puppet extensions contributed from modules Change By: Zachary Stern Labels: customer 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-2486) Per-environment cert management, with RBAC
Title: Message Title Zachary Stern created an issue Puppet / PUP-2486 Per-environment cert management, with RBAC Issue Type: New Feature Assignee: Unassigned Created: 06/May/14 9:57 AM Labels: support customer Priority: Normal Reporter: Zachary Stern It would be useful in some scenarios to have per-environment certificates, along with RBAC over who can generate and manage those certificates. In that way, a customer could control which nodes and which environment can be managed by whom. Add Comment
Jira (PUP-1320) service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop
Title: Message Title Zachary Stern updated an issue Puppet / PUP-1320 service puppet ensure stopped kills off cron-run puppet with Caught TERM; calling stop Change By: Zachary Stern Labels: customer redmine 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-2094) File resources do not create parent directories if they are missing.
Title: Message Title Zachary Stern created an issue Puppet / PUP-2094 File resources do not create parent directories if they are missing. Issue Type: New Feature Assignee: Unassigned Created: 28/Mar/14 2:34 PM Labels: customer support Priority: Normal Reporter: Zachary Stern File resourced currently do not have a method or automatically creating parent directories. It would be useful if there was an automatic method for doing so. Add Comment This message was sent by
Jira (PUP-2094) File resources do not create parent directories if they are missing.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2094 File resources do not create parent directories if they are missing. Change By: Zachary Stern File resourced resources currentlydonothaveamethodorautomaticallycreatingparentdirectories.Itwouldbeusefuliftherewasanautomaticmethodfordoingso. 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-2094) File resources do not create parent directories if they are missing.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2094 File resources do not create parent directories if they are missing. Change By: Zachary Stern Fileresourcescurrentlydonothaveamethod or of automaticallycreatingparentdirectories.Itwouldbeusefuliftherewasanautomaticmethodfordoingso. 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-2094) File resources do not create parent directories if they are missing.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-2094 File resources do not create parent directories if they are missing. Change By: Zachary Stern Fileresourcescurrentlydonothaveamethod of or automaticallycreatingparentdirectories.Itwouldbeusefuliftherewasanautomaticmethodfordoingso -andseveralcustomershaverequestedthisfeatureovertime . 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-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title
Zachary Stern commented on an issue
Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Andy Parker it's not so much wrong as that it always shows settings from the User runmode, rather than master or agent, and that's generally not what customers are looking to find.
This ends mostly just confusing people.
As to specifying a specific block of configuration, I'm confused by your example {{ puppet config print --section }}.
lolcalhost :: ~ % puppet config print -- master certname
master =
certname = lolcalhost.wifi.puppetlabs.net
lolcalhost :: ~ % puppet config print master certname
master =
certname = lolcalhost.wifi.puppetlabs.net
I consider the above output to be strange? What's master =
In addition, customers generally are not looking for a command to tell them what's in the file. They are looking for a command that shows them the resolved value of that setting, for that runmdode.
Add Comment
Puppet / PUP-2038
`puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
{{puppet config print}} is rarely accurate, and mostly just confusing to users. It should be deprecated in favor of {{puppet agent --configprint someoption}}, which currently works fairly well. Puppet 3.something should issue deprecation warnings, and Puppet 4 should remove it entirely.
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title Zachary Stern created an issue Puppet / PUP-2038 `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4 Issue Type: Bug Assignee: Unassigned Created: 25/Mar/14 4:50 PM Priority: Normal Reporter: Zachary Stern puppet config print is rarely accurate, and mostly just confusing to users. It should be deprecated in favor of puppet agent --configprint someoption, which currently works fairly well. Puppet 3.something should issue deprecation warnings, and Puppet 4 should remove it entirely. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2038) `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Title: Message Title
Zachary Stern commented on an issue
Re: `puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
Or alternatively, come up with a way to specify runmode with config print, and keep it, to maintain consistency with the newly implemented puppet config set, and deprecate --configprint.
Add Comment
Puppet / PUP-2038
`puppet config print` should issue deprecation warnings, and then be removed for Puppet 4
{{puppet config print}} is rarely accurate, and mostly just confusing to users. It should be deprecated in favor of {{puppet agent --configprint someoption}}, which currently works fairly well. Puppet 3.something should issue deprecation warnings, and Puppet 4 should remove it entirely.
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
Jira (PDB-515) puppetdb-ssl-setup should have certs-only option
Title: Message Title
Zachary Stern commented on an issue
Re: puppetdb-ssl-setup should have certs-only option
Essentially, a situation where there's nothing wrong with the jetty.ini file, but the certs have been screwed up in some way.
E.g. we've regenerated the agent cert for the PuppetDB server.
This is generally a non-issue, unless the customer has done some special configuration in jetty.ini, which did come up once for me.
Add Comment
PuppetDB / PDB-515
puppetdb-ssl-setup should have certs-only option
Customers frequently use {{puppetdb-ssl-setup}} to fix cert issues in their PE-based PuppetDB deployments. They generally have to use -f to make anything happen, since otherwise the script leaves everything alone, if configs/ssldata appears to be in place. However, there should be a third option - configure certificates only. Most of the time when w...
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
Jira (FACT-407) Facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Zachary Stern created an issue Facter / FACT-407 Facts hang on certain kernels when IO.read is called on /proc filesystem Issue Type: Bug Assignee: Eric Sorenson Created: 20/Mar/14 11:06 AM Priority: Normal Reporter: Zachary Stern 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-407) Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Zachary Stern updated an issue Facter / FACT-407 Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem Change By: Zachary Stern Summary: Facts Blockdevicefacts hangoncertainkernelswhenIO.readiscalledon/procfilesystem 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-407) Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem
Title: Message Title Zachary Stern updated an issue Facter / FACT-407 Blockdevice facts hang on certain kernels when IO.read is called on /proc filesystem Change By: Zachary Stern Labels: customersupport 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-1540) Puppet should support compilation failure if a variable is undefined
Title: Message Title
Zachary Stern commented on an issue
Re: Puppet should support compilation failure if a variable is undefined
That might do it! That's not in any PE releases yet, but some folks will definitely be excited about that when it arrives.
Add Comment
Puppet / PUP-1540
Puppet should support compilation failure if a variable is undefined
Currently, if a variable is undefined in puppet code, compilation succeeds, and the value is undef. E.g. {noformat} notify { $foo: } {noformat} results in {noformat} Notice: /Stage[main]//Notify[undef]/message: defined 'message' as 'undef' {noformat} Similarly, if you try to use an undefined variable inside a template, in interpolates to an ...
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
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. Change By: Zachary Stern Labels: customer redmine support Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1540) Puppet should support compilation failure if a variable is undefined
Title: Message Title
Zachary Stern created an issue
Puppet / PUP-1540
Puppet should support compilation failure if a variable is undefined
Issue Type:
New Feature
Assignee:
Eric Sorenson
Created:
29/Jan/14 12:49 PM
Labels:
customer support
Priority:
Normal
Reporter:
Zachary Stern
Currently, if a variable is undefined in puppet code, compilation succeeds, and the value is undef. E.g.
notify { $foo: }
results in
Notice: /Stage[main]//Notify[undef]/message: defined 'message' as 'undef'
Similarly, if you try to use an undefined variable inside a template, in interpolates to an empty string.
The problem with this is that you don't generally want an empty string inside your config file.
Therefore, it would be useful if puppet could run in a strict mode, where variable interpolation failures equal failed compile.
Essentially, the equivalent of this, but for all variables:
if $foo {
}
else {
fail('$foo is undefined')
}
Jira (PUP-1244) Yum provider using version-release to validate installation.
Title: Message Title Zachary Stern updated an issue Puppet / PUP-1244 Yum provider using version-release to validate installation. Change By: Zachary Stern Labels: customer redmineyum Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
