Jira (PUP-4948) config set --section main does not add [main]; ignores it if there
Title: Message Title Chris Spence commented on PUP-4948 Re: config set --section main does not add [main]; ignores it if there This still seems to be an issue on 4.3.2 on EL6: test:/etc/puppetlabs/puppet # puppet config set --section main pluginsync true test:/etc/puppetlabs/puppet # cat puppet.conf pluginsync = true [main] test:/etc/puppetlabs/puppet # puppet --version 4.3.2 Add Comment
Jira (PUP-5841) Environment string matching in the parser seems broken
Title: Message Title
Chris Spence created an issue
Puppet / PUP-5841
Environment string matching in the parser seems broken
Issue Type:
Bug
Affects Versions:
PUP 4.3.2
Assignee:
Unassigned
Created:
2016/02/09 4:26 AM
Priority:
Normal
Reporter:
Chris Spence
Using the following puppet code in puppet 4.3.2 the expectation that with the default environment of 'production' the conditional should match is not met, and the first notice doesn't happen. The second notice where environment is coerced to a string via interpolation does:
notice("double colon environment ${::environment}")
notice("environment ${environment}")
$foo = inline_template("<%= @environment.inspect %>")
Jira (PUP-5823) Puppet agent with splay on windows begets random interval between runs
Title: Message Title Chris Spence created an issue Puppet / PUP-5823 Puppet agent with splay on windows begets random interval between runs Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2016/02/05 3:31 AM Priority: Normal Reporter: Chris Spence Further to the thread at https://groups.google.com/forum/?fromgroups#!searchin/puppet-users/splay/puppet-users/56pWWnUslR8/C7iO-nmeCQAJ I'm finally getting round to logging this as an issue: We are running puppet (3.7.x) on Windows daemonized. We recently turned on splay because reasons. After having done so the interval between daemonised runs, counter to expectation, has become randomised (though we get an averageish run interval of 30 minutes (30.5 recurring)). The linuxes here have identical config and their runs are as regular as a muesli eating vegetarian. Here are some report times and approximate delta of a representative Windows 2012: Oct 21 2015 - 16:03:27 (14) Oct 21 2015 - 15:49:10 (28) Oct 21 2015 - 15:21:14 (33) Oct 21 2015 - 14:48:23 (32) Oct 21 2015 - 14:16:47 (23) Oct 21 2015 - 13:53:35 (36) Oct 21 2015 - 13:17:57 (27) Oct 21 2015 - 12:54:02 (29) Oct 21 2015 - 12:25:20 (53) Oct 21 2015 - 11:31:48
Jira (PUP-5586) Yum package installation with an epoch fails
Title: Message Title
Chris Spence created an issue
Puppet / PUP-5586
Yum package installation with an epoch fails
Issue Type:
Bug
Affects Versions:
PUP 4.3.1
Assignee:
Unassigned
Created:
2015/12/08 6:39 AM
Priority:
Normal
Reporter:
Chris Spence
After this commit https://github.com/puppetlabs/puppet/commit/1fdaeae9fa4f18c1c96da3d6fd84613dab6024f8 it is no longer possible to ensure the version at first install of a package where the package has a non-zero epoch set:
[root@acceptance ~]# cat foo.pp
package { 'mod_ssl': ensure => '1:2.4.16' }
Jira (PUP-5282) Allow local of install of a gem on windows
Title: Message Title
Chris Spence created an issue
Puppet / PUP-5282
Allow local of install of a gem on windows
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/09/25 6:27 AM
Priority:
Normal
Reporter:
Chris Spence
Attempts to install a gem from a local source on windows using the package type fail because the provider eventually passes the path as a source argument:
puppet
package { 'diplomercy':
ensure => '1.0.0',
source => 'c:/diplomercy-1.0.0.gem',
Jira (PUP-4766) Puppet packages should stick to FHS for file locations
Title: Message Title Chris Spence commented on PUP-4766 Re: Puppet packages should stick to FHS for file locations Well, yes - FHS is a Linux thing, and I agree with you about e.g. /etc/opt being a bit unpleasant. I have seen lots of other well behaved bits of software e.g. gitlab put their variable data in /var/opt and whilst the '/opt/' part of that path might be a bit sub-optimal, the leading '/var' is in line with my expectations. From memory, I think the original reason for /var/opt was to allow PE and Puppet open source to live on the same system to provide a migration path from POSS to PE. It seems that coexistence isn't possible any more by design (at least on EL - I haven't checked other platforms). That said, the fact that it's not possible for different flavours of Puppet to coexist shouldn't make the software behave in a way contrary to established system management practices by default. Harmony is OK. Not slapping cruft all across the filesystem is good, although from a system management standpoint, I personally view slapping variable data in /opt/something/somewhereelse/cache is a species of slathering - and incidentally to a location that doesn't exist on Windows. I'm not suggesting that the tool should not provide a consistent implementation, merely a consistency that conforms more in line with how the world manages systems. I still think that most unix/linuxes recommend /var as the place to put variable data. Even, and though I stand to be corrected, I'm pretty sure that this is true even on AIX. Systemd harmony with FHS is another conversation entirely, though I think I'm right in saying systemd hasn't thrown away /var yet (though when it does, I look forward to our systemd overlords storing variable data in a shared nosql database hosted somewhere in Slough (on AIX)). 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
Jira (PUP-4766) Puppet packages should stick to FHS for file locations
Title: Message Title Chris Spence created an issue Puppet / PUP-4766 Puppet packages should stick to FHS for file locations Issue Type: Bug Assignee: Unassigned Created: 2015/06/19 2:59 AM Priority: Normal Reporter: Chris Spence Following the discussion at https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/AH8yuIGtPg8 setting default file locations for e.g. vardir to locations that don't adhere to the FHS makes Puppet more tricky to implement and maintain. The major current example of this is setting the vardir to /opt/puppetlabs/puppet/cache by default when it should be /var/opt/puppetlabs according to the FHS Add Comment This message was sent by Atlassian JIRA
Jira (PUP-2983) Environment not updated via ENC if obsolete Environment in agents puppet.conf
Title: Message Title Chris Spence commented on PUP-2983 Re: Environment not updated via ENC if obsolete Environment in agents puppet.conf This issue persists into Puppet Server 2.1.0: With node_terminus set to exec (which always returns: ENC Output root@puppetmaster puppetlabs]# /platform/puppet/enc_dummy.sh sdfd --- environment: production classes: [] parameters: server_environment_class: production ) the node configured to ask for environment 'neveryoumind' gets the error:
Jira (PUP-4521) Pass agent-requested environment to external node classifiers
Title: Message Title Chris Spence commented on PUP-4521 Re: Pass agent-requested environment to external node classifiers Just curious - does this fix https://tickets.puppetlabs.com/browse/PUP-2983 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 (PDB-1467) puppetdb module has ordering problem with read_database.ini
Title: Message Title Chris Spence created an issue PuppetDB / PDB-1467 puppetdb module has ordering problem with read_database.ini Issue Type: Bug Assignee: Unassigned Created: 2015/05/01 12:51 AM Priority: Normal Reporter: Chris Spence On EL6, Puppet 3.7.4 I get this error: Error: Could not set 'file' on ensure: No such file or directory - /etc/puppetdb/conf.d/read_database.ini at 43:/platform/puppet/environment/production/modules/puppetdb/manifests/server/read_database_ini.pp when building a fresh machine Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1411) KahaDB scheduler log files pile up
Title: Message Title
Chris Spence created an issue
PuppetDB / PDB-1411
KahaDB scheduler log files pile up
Issue Type:
Bug
Affects Versions:
PDB 2.1.0
Assignee:
Unassigned
Created:
2015/04/07 2:00 AM
Environment:
EL6.3 puppetdb-2.1.0-1.el6.noarch
Priority:
Normal
Reporter:
Chris Spence
Periodically, the KabaDB scheduler directory (/var/lib/puppetdb/mq/localhost/scheduler) fills up with log files. The logs are full of entries like and the log files never vanish:
We are running Puppet 3.7.4
{annotations:{attempts:[{timestamp:2015-03-20T03:32:17.067Z,error:org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint \resource_params_cache_pkey\\n Detail: Key (resource)=(034e77ec81022dd11b3155d5d94e44d8d98ea891) already
Jira (PUP-3859) Puppet Apply dependancy cycle error exits 0 (even on detailed exit codes)
Title: Message Title Chris Spence commented on PUP-3859 Re: Puppet Apply dependancy cycle error exits 0 (even on detailed exit codes) I can confirm this behaviour on 3.7.4 also: c877wysdas02b:~ # puppet apply /tmp/apply_manifest.pp.PlMT1T Warning: Change notice: purging cron entries will be more aggressive in future versions, take care when updating your agents. See http://links.puppetlabs.com/puppet-aggressive-cron-purge (at /usr/lib/ruby/site_ruby/1.8/puppet/type/resources.rb:140:in `deprecate_params') Notice: Compiled catalog for c877wysdas02b in environment production in 4.77 seconds 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 to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type/package.rb:430:in `default') Error: Could not apply complete catalog: Found 1 dependency cycle: (File[/platform/puppet/hieradata/production] = File[/platform/puppet/hieradata/production]) Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz Notice: Finished catalog run in 0.45 seconds c877wysdas02b:~ # echo $? 0 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-3556) Older versions of Puppet fail to retrieve certificates from a 3.7.x master
Title: Message Title
Chris Spence updated an issue
Puppet / PUP-3556
Older versions of Puppet fail to retrieve certificates from a 3.7.x master
Change By:
Chris Spence
Aversion3.1.0Puppetagent(OEL6.5x86_64)requestingacertfromamasterrunning,inthiscase,3.7.2withautosignenabled(signeverything-*)failstodownloadthesignedcertificate:{quote}undefined:~#puppet-V3.1.0undefined:~#puppetagent-tInfo:CreatinganewSSLkeyforundefined.emea1.ciscloudInfo:CachingcertificateforcaInfo:CreatinganewSSLcertificaterequestforundefined.emea1.ciscloudInfo:CertificateRequestfingerprint(SHA256):F6:EB:4E:C3:19:CC:C4:11:09:05:5B:B9:76:4F:32:09:0D:73:64:03:D5:8C:E4:45:C8:B4:BD:F0:00:C1:E7:74Error:Couldnotrequestcertificate:Couldnotinternfroms:nestedasn1errorExiting;failedtoretrievecertificateandwaitforcertisdisabled{quote}Themasterhasinfactreceivedthecertrequest,andhassignedit.{quote}puppetmaster:/var/log/puppet#puppetcertlist--all|grepundefined+undefined.emea1.ciscloud(SHA256)1F:A0:FA:25:37:90:82:DA:EE:64:B5:9C:69:CF:4C:E9:BD:D9:EE:E1:B7:A6:66:5C:52:EC:5F:F8:55:EC:E1:55{quote}Meanwhiletheagentisinatailspin{quote}undefined:~#puppetagent-t --servernonprod.puppet.int.thomsonreuters.com Info:CreatinganewSSLcertificaterequestforundefined.emea1.ciscloudInfo:CertificateRequestfingerprint(SHA256):F6:EB:4E:C3:19:CC:C4:11:09:05:5B:B9:76:4F:32:09:0D:73:64:03:D5:8C:E4:45:C8:B4:BD:F0:00:C1:E7:74Error:Couldnotrequestcertificate:Couldnotinternfroms:nestedasn1errorExiting;failedtoretrievecertificateandwaitforcertisdisabled{quote}
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
Jira (PUP-3556) Older versions of Puppet fail to retrieve certificates from a 3.7.x master
Title: Message Title Chris Spence created an issue Puppet / PUP-3556 Older versions of Puppet fail to retrieve certificates from a 3.7.x master Issue Type: Bug Assignee: Unassigned Created: 28/Oct/14 2:28 AM Priority: Normal Reporter: Chris Spence A version 3.1.0 Puppet agent (OEL 6.5 x86_64) requesting a cert from a master running, in this case, 3.7.2 with autosign enabled (sign everything - *) fails to download the signed certificate: undefined:~ # puppet -V 3.1.0 undefined:~ # puppet agent -t Info: Creating a new SSL key for undefined.emea1.ciscloud Info: Caching certificate for ca Info: Creating a new SSL certificate request for undefined.emea1.ciscloud Info: Certificate Request fingerprint (SHA256): F6:EB:4E:C3:19:CC:C4:11:09:05:5B:B9:76:4F:32:09:0D:73:64:03:D5:8C:E4:45:C8:B4:BD:F0:00:C1:E7:74 Error: Could not request certificate: Could not intern from s: nested asn1 error Exiting; failed to retrieve certificate and waitforcert is disabled The master has in fact received the cert request, and has signed it. puppetmaster:/var/log/puppet # puppet cert list --all | grep undefined + undefined.emea1.ciscloud (SHA256) 1F:A0:FA:25:37:90:82:DA:EE:64:B5:9C:69:CF:4C:E9:BD:D9:EE:E1:B7:A6:66:5C:52:EC:5F:F8:55:EC:E1:55 Meanwhile the agent is in a tailspin undefined:~ # puppet agent -t --server nonprod.puppet.int.thomsonreuters.com Info: Creating a new SSL certificate request for undefined.emea1.ciscloud Info: Certificate Request fingerprint (SHA256): F6:EB:4E:C3:19:CC:C4:11:09:05:5B:B9:76:4F:32:09:0D:73:64:03:D5:8C:E4:45:C8:B4:BD:F0:00:C1:E7:74 Error: Could not request certificate: Could not intern from s: nested asn1 error
Jira (PUP-3556) Older versions of Puppet fail to retrieve certificates from a 3.7.x master
Title: Message Title
Chris Spence updated an issue
Puppet / PUP-3556
Older versions of Puppet fail to retrieve certificates from a 3.7.x master
Change By:
Chris Spence
Aversion3.1.0Puppetagent(OEL6.5x86_64)requestingacertfromamasterrunning,inthiscase,3.7. 2 1 withautosignenabled(signeverything-*)failstodownloadthesignedcertificate:{quote}undefined:~#puppet-V3.1.0undefined:~#puppetagent-tInfo:CreatinganewSSLkeyforundefined.emea1.ciscloudInfo:CachingcertificateforcaInfo:CreatinganewSSLcertificaterequestforundefined.emea1.ciscloudInfo:CertificateRequestfingerprint(SHA256):F6:EB:4E:C3:19:CC:C4:11:09:05:5B:B9:76:4F:32:09:0D:73:64:03:D5:8C:E4:45:C8:B4:BD:F0:00:C1:E7:74Error:Couldnotrequestcertificate:Couldnotinternfroms:nestedasn1errorExiting;failedtoretrievecertificateandwaitforcertisdisabled{quote}Themasterhasinfactreceivedthecertrequest,andhassignedit.{quote}puppetmaster:/var/log/puppet#puppetcertlist--all|grepundefined+undefined.emea1.ciscloud(SHA256)1F:A0:FA:25:37:90:82:DA:EE:64:B5:9C:69:CF:4C:E9:BD:D9:EE:E1:B7:A6:66:5C:52:EC:5F:F8:55:EC:E1:55{quote}Meanwhiletheagentisinatailspin{quote}undefined:~#puppetagent-tInfo:CreatinganewSSLcertificaterequestforundefined.emea1.ciscloudInfo:CertificateRequestfingerprint(SHA256):F6:EB:4E:C3:19:CC:C4:11:09:05:5B:B9:76:4F:32:09:0D:73:64:03:D5:8C:E4:45:C8:B4:BD:F0:00:C1:E7:74Error:Couldnotrequestcertificate:Couldnotinternfroms:nestedasn1errorExiting;failedtoretrievecertificateandwaitforcertisdisabled{quote}
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,
Jira (PUP-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title
Chris Spence commented on an issue
Re: Significant delay in puppet runs with growing numbers of directory environments
Probably also worth noting that e.g. puppet cert, puppet apply all do the same thing.
Add Comment
Puppet / PUP-3389
Significant delay in puppet runs with growing numbers of directory environments
When using directory environments there appears to be significant lag at the start of a puppet *agent* run whilst the agent startup explores the environment path. With 576 directory environments, each is statted 1159 times during puppet agent startup (one of the stats is opening the environment.conf) - having straced the puppet run: {{# grep -c cda_...
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-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title Chris Spence created an issue Puppet / PUP-3389 Significant delay in puppet runs with growing numbers of directory environments Issue Type: Bug Assignee: Unassigned Created: 06/Oct/14 7:38 AM Priority: Normal Reporter: Chris Spence When using directory environments there appears to be significant lag at the start of a puppet agent run whilst the agent startup explores the environment path. With 576 directory environments, each is statted 1160 times during puppet agent startup - having straced the puppet run: # grep -c cda_core_0_4_70 puppet.txt 1160 This causes significant delay in run startup - circa 20s. The agent also attempts to open an environment.conf in each environment whilst doing this (and I'm not sure this is necessary either) though this only happens 1162 times Add Comment
Jira (PUP-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title
Chris Spence updated an issue
Puppet / PUP-3389
Significant delay in puppet runs with growing numbers of directory environments
Change By:
Chris Spence
Whenusingdirectoryenvironmentsthereappearstobesignificantlagatthestartofapuppet*agent*runwhilsttheagentstartupexplorestheenvironmentpath.With576directoryenvironments,eachisstatted 1160 1159 timesduringpuppetagentstartup (oneofthestatsisopeningtheenvironment.conf) -havingstracedthepuppetrun:{{#grep-ccda_core_0_4_70puppet.txt}}{{1160}}Thiscausessignificantdelayinrunstartup-circa20s.Theagentalsoattemptstoopenanenvironment.confineachenvironmentwhilstdoingthis(andI'mnotsurethisisnecessaryeither)thoughthisonlyhappens1162times
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-3302) Puppet resource broken when directory environments enabled
Title: Message Title Chris Spence created an issue Puppet / PUP-3302 Puppet resource broken when directory environments enabled Issue Type: Bug Affects Versions: 3.7.1 Assignee: Unassigned Created: 18/Sep/14 6:15 AM Priority: Normal Reporter: Chris Spence puppet resource file /usr/share/puppet-dashboard-mirror ensure=directory source=/usr/share/puppet-dashboard recurse=true ignore='*/log/' Error: /File[/usr/share/puppet-dashboard-mirror]: Failed to generate additional resources using 'eval_generate': Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Error: /File[/usr/share/puppet-dashboard-mirror]: Could not evaluate: Could not retrieve file metadata for file:/usr/share/puppet-dashboard: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Wrapped exception: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Error: Could not run: Could not retrieve file metadata for file:/usr/share/puppet-dashboard: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist? Wrapped exception: Could not find a directory environment named 'none' anywhere in the path: /platform/puppet/environment. Does the directory exist?
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title
Chris Spence updated an issue
Puppet / PUP-3302
Puppet resource broken when directory environments enabled
Change By:
Chris Spence
# Whenrunning puppetresource ,thecommandfailsforwantofa'none'environment{quote}puppetresource file/usr/share/puppet-dashboard-mirrorensure=directorysource=/usr/share/puppet-dashboardrecurse=trueignore='* */ log / *'Error:/File[/usr/share/puppet-dashboard-mirror]:Failedtogenerateadditionalresourcesusing'eval_generate':Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Error:/File[/usr/share/puppet-dashboard-mirror]:Couldnotevaluate:Couldnotretrievefilemetadataforfile:/usr/share/puppet-dashboard:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Wrappedexception:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Error:Couldnotrun:Couldnotretrievefilemetadataforfile:/usr/share/puppet-dashboard:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist?Wrappedexception:Couldnotfindadirectoryenvironmentnamed'none'anywhereinthepath:/platform/puppet/environment.Doesthedirectoryexist? {quote}Notealso-whenalargenumberofdirectoryenvironmentsexist,thevalid_directoriesroutinein/usr/lib/ruby/site_ruby/1.8/puppet/environments.rbtakesalotoftimetostattheenvironmentdirectoryandworkoutwhetherallthedirectoriesarevalid(Icurrentlyhave224environmentsandthedelaybetweene.g.apuppetagent-t--debugandthecommandevenstartingtodisplaydebugoutputissomethinglike10s(ymmvdependingonIOetc)
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Chris Spence created an issue Puppet / PUP-3244 ENC returned environment ignored when using directory environments Issue Type: Bug Affects Versions: 3.7.0 Assignee: Unassigned Created: 15/Sep/14 8:04 AM Priority: Normal Reporter: Chris Spence Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather than failing (which is the behaviour I think I am expecting). Add Comment
Jira (PUP-3037) Pluginsync notices on Windows reports file paths with forward slashes
Title: Message Title Chris Spence updated an issue Puppet / PUP-3037 Pluginsync notices on Windows reports file paths with forward slashes Change By: Chris Spence Pluginsync/loadingfactsnoticesonWindowsoutputfilepathswithforwardslashes: ` Notice:/File[C:/ProgramData/PuppetLabs/puppet/var/lib/puppet/provider/rabbitmq_vhost]/ensure:removedInfo:LoadingfactsinC:/ProgramData/PuppetLabs/puppet/var/lib/facter/concat_basedir.rb ` Thisisclearlyalie.WhenIcopythosepathsandtrytousethem,Windowsgetsangryatme. 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-3037) Pluginsync notices on Windows reports file paths with forward slashes
Title: Message Title Chris Spence created an issue Puppet / PUP-3037 Pluginsync notices on Windows reports file paths with forward slashes Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Client Created: 08/Aug/14 4:31 AM Priority: Normal Reporter: Chris Spence Pluginsync/loading facts notices on Windows output file paths with forward slashes: `Notice: /File[C:/ProgramData/PuppetLabs/puppet/var/lib/puppet/provider/rabbitmq_ vhost]/ensure: removed Info: Loading facts in C:/ProgramData/PuppetLabs/puppet/var/lib/facter/concat_basedir.rb` This is clearly a lie. When I copy those paths and try to use them, Windows gets angry at me. Add Comment
Jira (PUP-3037) Pluginsync notices on Windows reports file paths with forward slashes
Title: Message Title
Chris Spence updated an issue
Puppet / PUP-3037
Pluginsync notices on Windows reports file paths with forward slashes
Change By:
Chris Spence
Pluginsync/loadingfactsnoticesonWindowsoutputfilepathswithforwardslashes: {quote} Notice:/File[C:/ProgramData/PuppetLabs/puppet/var/lib/puppet/provider/rabbitmq_vhost]/ensure:removedInfo:LoadingfactsinC:/ProgramData/PuppetLabs/puppet/var/lib/facter/concat_basedir.rb {quote} Thisisclearlyalie.WhenIcopythosepathsandtrytousethem,Windowsgetsangryatme.
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-2945) Puppet Windows package provider warn when source =~ /\//
Title: Message Title Chris Spence created an issue Puppet / PUP-2945 Puppet Windows package provider warn when source =~ /\// Issue Type: Improvement Assignee: Unassigned Created: 17/Jul/14 5:43 AM Priority: Normal Reporter: Chris Spence Package installation/upgrade in Windows will probably fail if the source attribute path contains / Not sure of all the ins and outs here, but I think warning is sufficient - it the path ends up really not existing to msiexec etc then the resource will fail, and the warning will give a hint as to the cause. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Chris Spence commented on an issue Re: Hiera should support alternate environments I rather think that the whole point of the ticket is so you don't have to create another distinct puppet master to be able to traverse a different hierarchy in hiera. Add Comment Hiera / HI-46 Hiera should support alternate environments Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive. Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment. 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.
