Jira (PUP-1014) PR (2147): Make puppet module build use metadata.json as primary input - thallgren
Title: Message Title gepetto-bot commented on an issue Re: PR (2147): Make puppet module build use metadata.json as primary input - thallgren thallgren commented: Corrected indentation and added related ticket to commit comment. Add Comment Puppet / PUP-1014 PR (2147): Make puppet module build use metadata.json as primary input - thallgren h2. Make puppet module build use metadata.json as primary input * Author: Thomas Hallgren * Company: Puppet Labs, Inc. * Github ID: [thallgren|https://github.com/thallgren] * [Pull Request 2147 Discussion|https://github.com/puppetlabs/puppet/pull/2147] * [Pull Request 2147 File Diff|https://github.com/puppetlabs/puppet/pull/2147/files] h2. Pull ... 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 (PDB-149) Remove v2/resources count related code
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-149 Remove v2/resources count related code Change By: Kenneth Barber Affects Version/s: 1.5.0 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 (PDB-174) 'puppet storeconfigs export' only uses [main] for settings
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-174 'puppet storeconfigs export' only uses [main] for settings Change By: Kenneth Barber Affects Version/s: 1.5.0 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 (PDB-205) Invalid configuration items cause weird exceptions that are hard for the user to debug
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-205 Invalid configuration items cause weird exceptions that are hard for the user to debug Change By: Kenneth Barber Affects Version/s: 1.5.0 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 (PDB-218) puppetdb-ssl-setup script doesn't allow specifying ssldir
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-218 puppetdb-ssl-setup script doesn't allow specifying ssldir Change By: Kenneth Barber Affects Version/s: 1.5.0 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 (PDB-241) Parameterize exit for the cli functions
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-241 Parameterize exit for the cli functions Change By: Kenneth Barber Affects Version/s: 1.6.0 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 (PDB-191) anon: Exported report file names are not good parseable tokens
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-191 anon: Exported report file names are not good parseable tokens Change By: Kenneth Barber Affects Version/s: 1.5.0 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 (PDB-180) PuppetDB binding to IPv6 interfaces only
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-180 PuppetDB binding to IPv6 interfaces only Change By: Kenneth Barber Affects Version/s: 1.5.0 Idon'tknowtheexactsourceoftheproblembutI'vebeenseeingPuppetDBtcp/8081bindto*only*IPv6interfaceswhenIPv6isenabled.Thisthencausesproblemsduringfactsubmissiononagentruns.ThisisonOracleEL6.ProblemgoesawayafterdisablingIPv6andrebooting. 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 (PDB-253) Module: ubuntu 1004 tests are failing for the puppetdb module automated system tests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-253 Module: ubuntu 1004 tests are failing for the puppetdb module automated system tests Change By: Kenneth Barber Component/s: Module 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 (PDB-199) Modify terminus spec tests in CI to support testing on Ruby 2
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-199 Modify terminus spec tests in CI to support testing on Ruby 2 Change By: Kenneth Barber Affects Version/s: 1.5.0 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 (PDB-307) A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-307 A change in rubygem 'mocha 1.0.0' has started causing rspec test failures Change By: Kenneth Barber Sprint: 20140108to20140115 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 (PDB-307) A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-307 A change in rubygem 'mocha 1.0.0' has started causing rspec test failures Change By: Kenneth Barber Assignee: KennethBarber 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 (PDB-307) A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-307 A change in rubygem 'mocha 1.0.0' has started causing rspec test failures Issue Type: Bug Affects Versions: 1.5.0 Assignee: Unassigned Created: 14/Jan/14 5:20 AM Priority: Normal Reporter: Kenneth Barber So it seems that the change from mocha '0.14.0' to '1.0.0' has caused a new rspec test failure: Failures: 1) Puppet::Reports::Puppetdb#report_to_hash should include the transaction uuid or nil Failure/Error: if subject.report_format = 4 NoMethodError: private method `report_format' called for #Puppet::Transaction::Report:0x007fbe3d8d16b8 # ./spec/unit/reports/puppetdb_spec.rb:78:in `block (3 levels) in top (required)' 2) Puppet::Reports::Puppetdb#report_to_hash events resource with events should include the resource Failure/Error: if subject.report_format = 4 NoMethodError: private method `report_format' called for #Puppet::Transaction::Report:0x007fbe3c906698 # ./spec/unit/reports/puppetdb_spec.rb:145:in `block (5 levels) in top (required)' Finished in 0.72031 seconds 117 examples, 2 failures This applies to all branches: 1.5.x, 1.6.x and master. Unfortunately our rspec tests in jenkins have not been picking this up, because 'bundle update' never gets ran so we never see it there.
Jira (PDB-290) Smoke test packages
Title: Message Title Kenneth Barber commented on an issue Re: Smoke test packages Packages uploaded internally here: http://builds.puppetlabs.lan/puppetdb/1.6.0-rc2/repos/ Add Comment PuppetDB / PDB-290 Smoke test packages 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-1436) Hiera-Acceptance-stable and -master fail on autoloading error
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-1436
Hiera-Acceptance-stable and -master fail on autoloading error
Change By:
Kurt Wall
[Unsureaboutcomponentsoleavingblank]BothHiera-Acceptance-stableandHiera-Acceptance-master , failed (onlythemastercells) toautoloadafileanderroredout onallcellsthatcombineLinuxandmaster :{code}Jan1404:26:10localhostpuppet-master[5212]:Couldnotautoloadpuppet/type/file:nosuchfiletoload--jsonJan1404:26:10localhostpuppet-master[5212]:CouldnotcreateresourcesformanagingPuppet'sfilesanddirectoriesinsections[:main,:master,:ssl,:metrics]:Couldnotautoloadpuppet/type/file:nosuchfiletoload--jsonJan1404:26:10localhostpuppet-master[5212]:Couldnotprepareforexecution:CouldnotcreateresourcesformanagingPuppet'sfilesanddirectoriesinsections[:main,:master,:ssl,:metrics]:Couldnotautoloadpuppet/type/file:nosuchfiletoload--json*#RuntimeError:PuppetAcceptance::DSL::Helpers.with_puppet_running_onfailed(checkbacktraceforlocation)because:Host'ql53mgh57ay9s6k'exitedwith1running:envRUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB}PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH}puppetmaster{code}Acoupleoflogfilestogetyoustarted:*https://jenkins.puppetlabs.com/job/Hiera-Acceptance-master/facter=1.6.x,platform=centos-5,puppet=master,slave=acc-coord/553/console*https://jenkins.puppetlabs.com/job/Hiera-Acceptance-master/facter=1.6.x,platform=centos-5,puppet=master,slave=acc-coord/553/consoleFailsonare-run,too.
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
Jira (PUP-1436) Hiera-Acceptance-stable and -master fail on autoloading error
Title: Message Title
Kurt Wall created an issue
Puppet / PUP-1436
Hiera-Acceptance-stable and -master fail on autoloading error
Issue Type:
Bug
Assignee:
Unassigned
Created:
14/Jan/14 7:12 AM
Priority:
Normal
Reporter:
Kurt Wall
[Unsure about component so leaving blank]
Both Hiera-Acceptance-stable and Hiera-Acceptance-master failed (only the master cells) to autoload a file and errored out:
Jan 14 04:26:10 localhost puppet-master[5212]: Could not autoload puppet/type/file: no such file to load -- json
Jan 14 04:26:10 localhost puppet-master[5212]: Could not create resources for managing Puppet's files and directories in sections [:main, :master, :ssl, :metrics]: Could not autoload puppet/type/file: no such file to load -- json
Jan 14 04:26:10 localhost puppet-master[5212]: Could not prepare for execution: Could not create resources for managing Puppet's files and directories in sections [:main, :master, :ssl, :metrics]: Could not autoload puppet/type/file: no such file to load -- json
*
#RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'ql53mgh57ay9s6k' exited with 1 running:
env RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB} PATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH} puppet master
A couple of log files to get you started:
https://jenkins.puppetlabs.com/job/Hiera-Acceptance-master/facter=1.6.x,platform=centos-5,puppet=master,slave=acc-coord/553/console
Jira (PDB-307) A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-307 A change in rubygem 'mocha 1.0.0' has started causing rspec test failures Change By: Kenneth Barber Fix Version/s: 1.5.X 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 (PDB-307) A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Title: Message Title
Kenneth Barber commented on an issue
Re: A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
PR is here: https://github.com/puppetlabs/puppetdb/pull/798
Add Comment
PuppetDB / PDB-307
A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
So it seems that the change from mocha '0.14.0' to '1.0.0' has caused a new rspec test failure: {code} Failures: 1) Puppet::Reports::Puppetdb#report_to_hash should include the transaction uuid or nil Failure/Error: if subject.report_format = 4 NoMethodError: private method `report_format' called for #Puppet::Transaction::Rep...
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 (PDB-290) Smoke test packages
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-290 Smoke test packages Change By: Kenneth Barber Assignee: KennethBarber 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-1437) Puppet-Acceptance-Windows-master-vcloud... failed in can_enumerate_environments.rb
Title: Message Title Kurt Wall created an issue Puppet / PUP-1437 Puppet-Acceptance-Windows-master-vcloud... failed in can_enumerate_environments.rb Issue Type: Bug Assignee: Unassigned Created: 14/Jan/14 7:52 AM Priority: Normal Reporter: Kurt Wall Apparently it is trying to use the wrong key (https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-master-vcloud-and-github/196/label=acc-coord,platform=win2003r2/console): Test Case tests/environment/can_enumerate_environments.rb reported: #RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'l1c5bhdkhzb9sy9' exited with 58 running: curl -g --cert C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/etc/ssl/certs/l1c5bhdkhzb9sy9.delivery.puppetlabs.net.pem --key C:/Documents and Settings/All Users/Application Data/PuppetLabs/puppet/etc/ssl/private_keys/l1c5bhdkhzb9sy9.delivery.puppetlabs.net.pem -k -H '' 'https://t6f7amdlqwe8udw:8140/v2.0/environments' Last 10 lines of output were: % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (58) unable to use client certificate (no key found or wrong pass phrase?) Puppet-Acceptance-Windows-master-vcloud-and-github (eg, https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-master-vcloud-and-github/196/label=acc-coord,platform=win2003r2/console)
Jira (PUP-1411) Windows agents experience intermittent SSL_connect failures in acceptance testing
Title: Message Title
Kurt Wall commented on an issue
Re: Windows agents experience intermittent SSL_connect failures in acceptance testing
And again:
https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-Per-Commit-stable/label=acc-coord,platform=win2008r2/31/console
https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-Per-Commit-master/label=acc-coord,platform=win2008r2/70/console
Add Comment
Puppet / PUP-1411
Windows agents experience intermittent SSL_connect failures in acceptance testing
Breaking this out as a separate ticket related to QA-768. During Windows acceptance testing on master, certificate requests non-deterministically fail due with SSL_connect failures: {code} #RuntimeError: PuppetAcceptance::DSL::Helpers.with_puppet_running_on failed (check backtrace for location) because: Host 'oqr39kv18vwtk49' exited with 1 running: ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-201) Custom Facts issue: Could not retrieve test: undefined method `get_fact_value' for #Facter::Util::Resolution:0x007ffec21d35d0
Title: Message Title
Vito Mule updated an issue
Facter / FACT-201
Custom Facts issue: Could not retrieve test: undefined method `get_fact_value' for #Facter::Util::Resolution:0x007ffec21d35d0
Change By:
Vito Mule
wroteacustomfactnamedtest.rbwiththiscodeinside:#!/usr/bin/ruby#defget_test()check_install=Dir.exists?('/etc/test')returncheck_installendFacter.add('test')dosetcodedoget_fact_value('test',$WEEK,'get_test')endendidIrun#sudofacter-p,itworksbutifIrunsudofactor-ptestigotthiserror:Couldnotretrievetest:undefinedmethod`get_fact_value'for#Facter::Util::Resolution:0x007ffec21d35d0 Renamingthefactfromtest.rbtosomethingelsefixedtheissue,butIthinkit'sabugthisbehavior.
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-1437) Puppet-Acceptance-Windows-master-vcloud... failed in can_enumerate_environments.rb
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-1437
Puppet-Acceptance-Windows-master-vcloud... failed in can_enumerate_environments.rb
Change By:
Kurt Wall
Apparentlyitistryingtousethewrongkey(https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-master-vcloud-and-github/196/label=acc-coord,platform=win2003r2/console):{code}TestCasetests/environment/can_enumerate_environments.rbreported:#RuntimeError:PuppetAcceptance::DSL::Helpers.with_puppet_running_onfailed(checkbacktraceforlocation)because:Host'l1c5bhdkhzb9sy9'exitedwith58running:curl-g--certC:/DocumentsandSettings/AllUsers/ApplicationData/PuppetLabs/puppet/etc/ssl/certs/l1c5bhdkhzb9sy9.delivery.puppetlabs.net.pem--keyC:/DocumentsandSettings/AllUsers/ApplicationData/PuppetLabs/puppet/etc/ssl/private_keys/l1c5bhdkhzb9sy9.delivery.puppetlabs.net.pem-k-H'''https://t6f7amdlqwe8udw:8140/v2.0/environments'Last10linesofoutputwere: %Total%Received%XferdAverageSpeedTimeTimeTimeCurrent DloadUploadTotalSpentLeftSpeed --:--::--::--:--0curl:(58)unabletouseclientcertificate(nokeyfoundorwrongpassphrase?){code}*Puppet-Acceptance-Windows-master-vcloud-and-github(eg,https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-master-vcloud-and-github/196/label=acc-coord,platform=win2003r2/console)* Puppet-Acceptance-Future-Parser-master-vcloud-and-github(https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Future-Parser-master-vcloud-and-github/label=acc-coord,platform=win2008r2/41/console)
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
Jira (PUP-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen skottler commented: I'm not sure about this. Perhaps we can make the permissions less strict for the root directory and signed certs, but I'm not comfortable with the change to the CA perms. What's the use case where this is needed @dalen? Add Comment Puppet / PUP-1430 PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen h2. Make SSL file permissions a bit more relaxed for public files * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257] * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/files] h2 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-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen dalen commented: The use case was for serving the static public files directly using Apache: https://gist.github.com/dalen/8419913 So this change only modifies the permissions for public files, not for any of the secrets. Add Comment Puppet / PUP-1430 PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen h2. Make SSL file permissions a bit more relaxed for public files * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257] * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/files] h2 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-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen domcleal commented: See also https://github.com/puppetlabs/puppet/pull/2223, @joshcooper explicitly decided to keep CA public data non-world readable. Add Comment Puppet / PUP-1430 PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen h2. Make SSL file permissions a bit more relaxed for public files * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257] * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/files] h2 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-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen skottler commented: Ah I see, makes sense; I'm fine with the change now that I understand the use case. @kylog @zaphod42 what do you guys think? Add Comment Puppet / PUP-1430 PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen h2. Make SSL file permissions a bit more relaxed for public files * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257] * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/files] h2 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
Jira (PUP-1147) Strange behaviour with file backup and purge
Title: Message Title Rob Nelson assigned an issue to Charlie Sharpsteen Per user, this functionality appears to be a bug. Per the documentation, it appears to be working by design. There are questions about the legitimacy of the design, or implementing limits on renames to avoid the $filename.$backup.[$backup...$backup] results. Referring to product owner for a decision. Puppet / PUP-1147 Strange behaviour with file backup and purge Change By: Rob Nelson Assignee: CharlieSharpsteen 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-1430) PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen dalen commented: The only file that are in both those PRs is the crlfile which is public info over the REST API. Add Comment Puppet / PUP-1430 PR (2257): Make SSL file permissions a bit more relaxed for public files - dalen h2. Make SSL file permissions a bit more relaxed for public files * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 2257 Discussion|https://github.com/puppetlabs/puppet/pull/2257] * [Pull Request 2257 File Diff|https://github.com/puppetlabs/puppet/pull/2257/files] h2 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.
Jira (PDB-308) Drop 2.7.x support for puppetdb-terminus
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-308 Drop 2.7.x support for puppetdb-terminus Issue Type: Task Assignee: Unassigned Created: 14/Jan/14 9:44 AM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber We would like to drop 2.7.x support from puppetdb-terminus for 2.0.0 if possible. This would allow us to drop the Ruby 1.8.5 tests as well. We should consider what minimum puppet version we support as part of this also going forward, as this might not include older 3.x revisions, but where we draw the line is yet to be determined. Add Comment
Jira (PUP-1438) puppet resource does not handle yum repo files with white spaec
Title: Message Title lee loucks created an issue Puppet / PUP-1438 puppet resource does not handle yum repo files with white spaec Issue Type: Bug Assignee: Unassigned Attachments: yumrepo.rb.diff Created: 14/Jan/14 9:58 AM Environment: $ rpm -q redhat-release-server redhat-release-server-6Server-6.5.0.1.el6.x86_64 $ rpm -q puppet puppet-3.3.2-1.el6.noarch Priority: Normal Reporter: lee loucks When running: puppet resource yumrepo epel puppet reports Error: Could not run: Invalid value 1. Valid values are absent. Valid values match /^(0|1)$/. This is because a Yum repository file contains white space between the equals and the 0 or the 1 for enabled or disabled. Like this [rhel-6-server-sam-source-rpms] ... enabled = 0 This particular repository file is installed via the RedHat subscription manager rpm $ rpm -qf
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Change By: Joshua Partlow Fix Version/s: 3.5.0 Fix Version/s: 3.4.3 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-1431) Pre/Post-run commands don't work under Windows
Title: Message Title Ken Johnson commented on an issue Re: Pre/Post-run commands don't work under Windows With that in mind, shouldn't this be breaking under *nix as well? I found that postrun commands worked fine on my installations on some Linux machines. Add Comment Puppet / PUP-1431 Pre/Post-run commands don't work under Windows If a postrun or prerun command is specified in puppet.conf on a Windows host it will fail to execute with a message like the following: Debug: Executing 'C:\Windows\System32\cmd.exe /c type NUL C:\from_postrun.txt' Error: Could not run command from postrun_command: CreateProcess() failed: The system cannot find the file specified.Example postr... 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-1439) managehome parameter for user resources is misleadingly named, should be 'createhome'
Title: Message Title redmine.exporter created an issue Puppet / PUP-1439 managehome parameter for user resources is misleadingly named, should be 'createhome' Issue Type: Bug Assignee: Unassigned Created: 14/Jan/14 10:37 AM Labels: redmine Priority: Normal Reporter: redmine.exporter After a user has been created via puppet user function with managehome = true it does not detect if the home directory has been deleted. This is tested on RHEL 5.5 (current). [edit] - Deprecate 'managehome' in Telly, add 'createhome'. Add Comment
Jira (PUP-522) Port final test changes from tmpfosstestsforpe back into puppet.
Title: Message Title Branan Purvine-Riley commented on an issue Re: Port final test changes from tmpfosstestsforpe back into puppet. Is there any chance this could get prioritized in the next week or two? PE 3.2 is coming up soon and at this point my options are to run with a suite in tmpfosstestsforpe that is missing the latest updated tests, or run with the suite in pe-puppet that does not have all the tweaks necessary to run properly against PE. Neither of these is super awesome. If your team can't resolve this soon, a quick write-up of what's needed would at least be great so I can do the heavy lifting. Add Comment Puppet / PUP-522 Port final test changes from tmpfosstestsforpe back into puppet. There are a few tests that have been added to https://github.com/puppetlabs/tmpfosstestsforpe since we began the testing from packages saga and started the port of pe-puppet acceptance changes back into puppet. Once we have the current integration/acceptance work merged in, and things are running on the https://jenkins.puppetlabs.com/job/PE-Puppet-Acce... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
Jira (PUP-1234) each function broken after upgrading to 3.4
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1234 each function broken after upgrading to 3.4 Change By: Henrik Lindberg Fix Version/s: 3.4.2 Fix Version/s: 3.4.3 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 (FACT-207) ldapname was soft deprecated but there's no warning message
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-207 ldapname was soft deprecated but there's no warning message Issue Type: Bug Affects Versions: 1.7.4 Assignee: Kylo Ginsberg Created: 14/Jan/14 11:13 AM Fix Versions: 1.7.5 Priority: Normal Reporter: Kylo Ginsberg Seems like we should add a deprecation warning in 1.7.5 and remove in 2.0.x. Add Comment
Jira (FACT-208) PR (602): (fact-207) Issue deprecation warning for ldapname - kylog
Title: Message Title gepetto-bot created an issue Facter / FACT-208 PR (602): (fact-207) Issue deprecation warning for ldapname - kylog Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 14/Jan/14 11:18 AM Labels: github Priority: Normal Reporter: gepetto-bot (fact-207) Issue deprecation warning for ldapname Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 602 Discussion Pull Request 602 File Diff Pull Request Description (webhooks-id:
Jira (PUP-1020) PR (2153): (#18342) WIP - Iristyle
Title: Message Title gepetto-bot commented on an issue Re: PR (2153): (#18342) WIP - Iristyle Iristyle commented: FYI – this is still WIP until I clean up the commits / verify on OSX, etc Add Comment Puppet / PUP-1020 PR (2153): (#18342) WIP - Iristyle h2. (#18342) WIP * Author: Ethan J. Brown * Company: * Github ID: [Iristyle|https://github.com/Iristyle] * [Pull Request 2153 Discussion|https://github.com/puppetlabs/puppet/pull/2153] * [Pull Request 2153 File Diff|https://github.com/puppetlabs/puppet/pull/2153/files] h2. Pull Request Description (webhooks-id: 4b89fe99d8f9a009b680... 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-522) Port final test changes from tmpfosstestsforpe back into puppet.
Title: Message Title Michelle Johansen commented on an issue Re: Port final test changes from tmpfosstestsforpe back into puppet. Joshua Partlow Can you help explain what is needed to Branan Purvine-Riley who has very graciously offered to complete this task for the Platform team. Calling in Justin Stoller and Kurt Wall if needed and as an FYI. Thank you Branan! Add Comment Puppet / PUP-522 Port final test changes from tmpfosstestsforpe back into puppet. There are a few tests that have been added to https://github.com/puppetlabs/tmpfosstestsforpe since we began the testing from packages saga and started the port of pe-puppet acceptance changes back into puppet. Once we have the current integration/acceptance work merged in, and things are running on the https://jenkins.puppetlabs.com/job/PE-Puppet-Acce... 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
Jira (FACT-205) PR (600): Feature/facter 2/fact 65 named resolutions - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (600): Feature/facter 2/fact 65 named resolutions - adrienthebo kylog commented: Re ldapname I added https://tickets.puppetlabs.com/browse/FACT-207 and associated pull for adding a deprecation warning in 1.7.5 if we choose to go that route. Add Comment Facter / FACT-205 PR (600): Feature/facter 2/fact 65 named resolutions - adrienthebo h2. Feature/facter 2/fact 65 named resolutions * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 600 Discussion|https://github.com/puppetlabs/facter/pull/600] * [Pull Request 600 File Diff|https://github.com/puppetlabs/facter/pull/600/files] h2... 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-1118) Support an $environmentsdir setting
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1118 Support an $environmentsdir setting Change By: Andrew Parker Sprint: Week2014-1-to2014-1-16 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-1150) Race condition in Puppet::Util::Lockfile
Title: Message Title Joshua Cooper assigned an issue to Peter Huene Puppet / PUP-1150 Race condition in Puppet::Util::Lockfile Change By: Joshua Cooper Assignee: PeterHuene 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-1282) puppet gem does not include platform specific gem dependencies
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1282 puppet gem does not include platform specific gem dependencies Change By: Andrew Parker Sprint: Week2014-1-15to2014-1-21 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Incorrect ordering of group and user resource purging
I agree with Daniel's assement: removing a user that is the sole member of a group cascades into removing the group as well — if the user and group share the same name. This behavior can also be reproduced using the puppet resource tool to add a group and user:
# puppet resource group foo ensure=present
notice: /Group[foo]/ensure: created
group { 'foo':
ensure = 'present',
}
# puppet resource user foo ensure=present gid=foo
notice: /User[foo]/ensure: created
user { 'foo':
ensure = 'present',
gid= '503',
}
Then, if we remove the user:
# puppet resource user foo ensure=absent
notice: /User[foo]/ensure: removed
user { 'foo':
ensure = 'absent',
}
We can see that the group was also removed by querying its status:
# puppet resource group foo
group { 'foo':
ensure = 'absent',
}
The behavior is explained in the caveats section of the userdel manpage:
If USERGROUPS_ENAB is defined to yes in /etc/login.defs, userdel will delete the group with the same name as the user. To avoid inconsistencies in the passwd and group databases, userdel will check that this group is not used as a primary group for another user, and will just warn without deleting the group otherwise. The -f option can force the deletion of this group.
This clash between Puppet behavior and /etc/login.defs has come up before with CREATE_HOME.
Looks like we need to decide whether or not the default behavior in these cases should be enforced by /etc/login.defs or Puppet. Eric Sorenson, any thoughts?
Add Comment
Jira (PUP-522) Port final test changes from tmpfosstestsforpe back into puppet.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-522 Port final test changes from tmpfosstestsforpe back into puppet. Change By: Joshua Partlow Sprint: Week2014-1-15to2014-1-21 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-753) Create a reasonable benchmark manifest
Title: Message Title Andrew Parker updated an issue Puppet / PUP-753 Create a reasonable benchmark manifest Change By: Andrew Parker Sprint: Week2014-1-15to2014-1-21 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1153 Incorrect ordering of group and user resource purging Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen EricSorenson 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-1432) Implement v2.0 API error responses
Title: Message Title Dan Lidral-Porter assigned an issue to Dan Lidral-Porter Puppet / PUP-1432 Implement v2.0 API error responses Change By: Dan Lidral-Porter Assignee: DanLidral-Porter 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-1432) Implement v2.0 API error responses
Title: Message Title Dan Lidral-Porter updated an issue Puppet / PUP-1432 Implement v2.0 API error responses Change By: Dan Lidral-Porter Sprint: Week2014-1-8to2014-1-15 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 (PDB-295) Close Resolved tickets in jira
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-295 Close Resolved tickets in jira Change By: Kenneth Barber Assignee: KennethBarber 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 (PDB-309) Update Schema config conversion logic for 2.0
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-309 Update Schema config conversion logic for 2.0 Issue Type: Task Affects Versions: 1.6.0-rc1, 1.6.0-rc2 Assignee: Unassigned Created: 14/Jan/14 12:09 PM Priority: Normal Reporter: Ryan Senior The code to convert from one schema to another (i.e. for the PuppetDB configuration) was before the Schema 2.0 new protocols were in place. I think a lot of what is currently done outside the library could be done inside of the library with those updates. Add Comment
Jira (PDB-310) Separate configuration conversion code into it's own library
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-310 Separate configuration conversion code into it's own library Issue Type: Task Affects Versions: 1.6.0-rc1, 1.6.0-rc2 Assignee: Unassigned Created: 14/Jan/14 12:11 PM Priority: Normal Reporter: Ryan Senior Christopher Price has a need for this in the TrapperKeeper codebase around the Jetty config. We should move this out into a separate JAR so that PuppetDB and TK can both use it. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-307) A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Title: Message Title
Kenneth Barber commented on an issue
Re: A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Two PR's merged for this:
https://github.com/puppetlabs/puppetdb/commit/c83e9a25305badf5b0c5551c8aee17b0b6730016 https://github.com/puppetlabs/puppetdb/commit/cf08f1f97caf6e8cf76acdb0567c6de4b509c6b5
Add Comment
PuppetDB / PDB-307
A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
So it seems that the change from mocha '0.14.0' to '1.0.0' has caused a new rspec test failure: {code} Failures: 1) Puppet::Reports::Puppetdb#report_to_hash should include the transaction uuid or nil Failure/Error: if subject.report_format = 4 NoMethodError: private method `report_format' called for #Puppet::Transaction::Rep...
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.
Jira (HI-130) GuardControl prevents from using variables multiple times
Title: Message Title
Simon created an issue
Hiera / HI-130
GuardControl prevents from using variables multiple times
Issue Type:
Bug
Affects Versions:
1.3.0
Assignee:
Eric Sorenson
Created:
14/Jan/14 12:33 PM
Environment:
Debian jessie hiera 1.3.0-1puppetlabs1 from apt.puppetlabs.com
Priority:
Major
Reporter:
Simon
If you want to use a variable (hiera or top scope/fact) multiple times the RecursiveGuard is preventing you to do this (which is definitely wrong because it should prevent you from endless loops).
yaml file:
something: 'xxx'
should_work: %{hiera('something')}%{hiera('something')}
command:
$ hiera should_work
/usr/lib/ruby/vendor_ruby/hiera/recursive_guard.rb:13:in `check': Detected in [hiera('something')] (Hiera::InterpolationLoop)
from /usr/lib/ruby/vendor_ruby/hiera/interpolate.rb:11:in `interpolate'
from /usr/lib/ruby/vendor_ruby/hiera/interpolate.rb:14:in `block in interpolate'
from /usr/lib/ruby/vendor_ruby/hiera/recursive_guard.rb:16:in `check'
from
Jira (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid
Title: Message Title Kenneth Barber commented on an issue Re: Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid Okay, we've discussed this internally and have decided to add acceptance tests modifications to support testing against this make-jpkg generated package. Otherwise, we'll have problems with PDB-88 when we retire. Add Comment PuppetDB / PDB-128 Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid I found that the JavaPackage way of creating a JDK package might potentially be a solution for users on squeeze/lucid that want JDK 7 as a package: https://wiki.debian.org/JavaPackage The trick is to use those instructions to create a package on wheezy, but then load it onto squeeze/lucid. Seems to work: https://gist.github.com/kbarber/7775906 Wh... 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
Jira (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-128 Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid Change By: Kenneth Barber IfoundthattheJavaPackagewayofcreatingaJDKpackagemightpotentiallybeasolutionforusersonsqueeze/lucidthatwantJDK7asapackage:https://wiki.debian.org/JavaPackageThetrickistousethoseinstructionstocreateapackageonwheezy,butthenloaditontosqueeze/lucid.Seemstowork:https://gist.github.com/kbarber/7775906Whilethisistroublesome,itmightworkforus.TheworkforusisreallyaboutaddingthenamesofthesegeneratedpackagestoourcontrolfileasafallbackfromthestandardJDK7packages,sothatuserscanusethesepackagesinstead. Todothisproperly,weshouldgetacceptancetestsworkingtoconfirmthissetup,thatmeansweshouldfindaplacetohostarepowiththisproposedpackagesothatsqueeze/luciduseitautomaticallywhenthispatchisapplied. 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 (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-128 Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid Making this a 5, since we seem to have lots of bad luck when changing acceptance. Change By: Kenneth Barber Story Points: 1 5 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 (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid
Title: Message Title Daniele Sluijters commented on an issue Re: Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid It would be a shame if this only gets released with PuppetDB 2.0 though seeing as that's what PDB-88 is targeted for. By then it might be a little late. Add Comment PuppetDB / PDB-128 Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid I found that the JavaPackage way of creating a JDK package might potentially be a solution for users on squeeze/lucid that want JDK 7 as a package: https://wiki.debian.org/JavaPackage The trick is to use those instructions to create a package on wheezy, but then load it onto squeeze/lucid. Seems to work: https://gist.github.com/kbarber/7775906 Wh... 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
Jira (FACT-208) PR (602): (fact-207) Issue deprecation warning for ldapname - kylog
Title: Message Title gepetto-bot commented on an issue Re: PR (602): (fact-207) Issue deprecation warning for ldapname - kylog puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-208 PR (602): (fact-207) Issue deprecation warning for ldapname - kylog h2. (fact-207) Issue deprecation warning for ldapname * Author: Kylo Ginsberg * Company: * Github ID: [kylog|https://github.com/kylog] * [Pull Request 602 Discussion|https://github.com/puppetlabs/facter/pull/602] * [Pull Request 602 File Diff|https://github.com/puppetlabs/facter/pull/602/files] h2. Pull Request Description (webhook... 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 (PDB-298) Announce release
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-298 Announce release Change By: Kenneth Barber Assignee: KennethBarber 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-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Change By: Kylo Ginsberg Assignee: KyloGinsberg 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 (HI-127) Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
Title: Message Title
Simon commented on an issue
Re: Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
this workaround doesn't work with hiera 1.3 I think.. looks like hiera 1.3 is doing multiple times a check on the string and will replace all variables and also all new generated variables afterwards as well.. at least in my case hiera 1.1 failed (exception), 1.2 worked and 1.3 gives me empty strings..
Add Comment
Hiera / HI-127
Allow escaping %{...} in hiera data so that hiera does not try to perform a replacement
I have some data that contains Apache variables (such as %{SERVER_NAME}, %{QUERY_STRING}, etc ) in a Hiera file (Yaml backend). However, when I retrieve the value, the string is replaced with empty value. For instance, for: myserver: http://%{SERVER_NAME} I got the value http// I found out that during the lookup in the YAML backend, the answ...
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 (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid
Title: Message Title Kenneth Barber commented on an issue Re: Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid No, I still want to target this for a 1.6.x, just probably a 1.6.1 or some such. Its fine to have this targeted at that older release. My point is around tests need to be added before PDB-88 - if we don't fix tests, they will break with PDB-88 any way. So this seems to be an acceptable solution to both, but we need to modify the tests first. Add Comment PuppetDB / PDB-128 Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid I found that the JavaPackage way of creating a JDK package might potentially be a solution for users on squeeze/lucid that want JDK 7 as a package: https://wiki.debian.org/JavaPackage The trick is to use those instructions to create a package on wheezy, but then load it onto squeeze/lucid. Seems to work: https://gist.github.com/kbarber/7775906 Wh... 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
Jira (PDB-298) Announce release
Title: Message Title Kenneth Barber commented on an issue Re: Announce release Email announcement here: https://groups.google.com/forum/#!topic/puppet-users/VuPd0tbW-Hs Add Comment PuppetDB / PDB-298 Announce release Send release email, and PSA on #puppet 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 (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid
Title: Message Title Daniele Sluijters commented on an issue Re: Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid Ah I see, that seems fair. Add Comment PuppetDB / PDB-128 Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid I found that the JavaPackage way of creating a JDK package might potentially be a solution for users on squeeze/lucid that want JDK 7 as a package: https://wiki.debian.org/JavaPackage The trick is to use those instructions to create a package on wheezy, but then load it onto squeeze/lucid. Seems to work: https://gist.github.com/kbarber/7775906 Wh... 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-1118) Support an $environmentsdir setting
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1118 Support an $environmentsdir setting Change By: Andrew Parker Sprint: Week2014-1- 15 8 to2014-1- 21 15 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-1118) Support an $environmentsdir setting
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-1118 Support an $environmentsdir setting Change By: Andrew Parker Assignee: AndrewParker 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-1389) Windows File resources generating 0 byte files and not populating file via content or source when title has -
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1389 Windows File resources generating 0 byte files and not populating file via content or source when title has - Change By: Michelle Johansen Component/s: PE 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-1150) Race condition in Puppet::Util::Lockfile
Title: Message Title Peter Huene commented on an issue Re: Race condition in Puppet::Util::Lockfile I've verified the changes fix the race by adding a delay between the #locked? check and the call to create the lock file and by removing the #locked? call entirely, although we have another spec that depends on #lock calling #locked?. Changes look good, except I think the new spec to test the race can be improved (i.e. forking ten processes once and ensure only one process acquired the lock instead of forking only two processes five times). Add Comment Puppet / PUP-1150 Race condition in Puppet::Util::Lockfile Puppet::Util::Lockfile does not exclude other processes from acquiring a lock between the time it checks if the lock file exists and when it writes to the lock file. This allows for a race condition, and two puppet processes started simultaneously are likely to acquire the same lock. This has been witnessed in the wild where I work because we may have... 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
Jira (PDB-238) Remove v1 API
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-238 Remove v1 API Change By: Kenneth Barber Assignee: RyanSenior 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-1150) Race condition in Puppet::Util::Lockfile
Title: Message Title Glenn Pratt commented on an issue Re: Race condition in Puppet::Util::Lockfile I left the call to locked? in speficically because of the spec lockfile_spec.rb. Not for any technical reason. I'm happy to remove that spec. I came up with the 2 forks 5 times pattern running it on Linux and Mac machines available to me - happy to change but I should probably verify 10 x 1 replicates it reliably. Just noticed a bug while looking at how this is done elsewhere: https://github.com/puppetlabs/puppet/blob/master/spec/unit/file_system/file_spec.rb#L802 I believe 5 should be num_procs. Add Comment Puppet / PUP-1150 Race condition in Puppet::Util::Lockfile Puppet::Util::Lockfile does not exclude other processes from acquiring a lock between the time it checks if the lock file exists and when it writes to the lock file. This allows for a race condition, and two puppet processes started simultaneously are likely to acquire the same lock. This has been witnessed in the wild where I work because we may have... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1440) PR (2260): Fix unused argument in file_spec.rb - glennpratt
Title: Message Title gepetto-bot created an issue Puppet / PUP-1440 PR (2260): Fix unused argument in file_spec.rb - glennpratt Issue Type: Task Assignee: Unassigned Components: Community Created: 14/Jan/14 2:09 PM Labels: github Priority: Normal Reporter: gepetto-bot Fix unused argument in file_spec.rb Author: Glenn Pratt glennpr...@gmail.com Company: Acquia Github ID: glennpratt Pull Request 2260 Discussion Pull Request 2260 File Diff Pull Request Description Noticed
Jira (PUP-1322) Puppet REST API always fails if there's at least one broken manifest
Title: Message Title Kylo Ginsberg commented on an issue Re: Puppet REST API always fails if there's at least one broken manifest I took a quick pass at verifying this but I couldn't repro the original symptom described above. I took a site.pp with a working class definition, then put some garbage in there, ran the agent again to force it to reload, then curl'd resource_types. I'd get: curlcert https://localhost:8140/production/resource_types/*?kind=class Not Found: Could not find instances in resource_type with '*' What am I doing wrong? Add Comment Puppet / PUP-1322 Puppet REST API always fails if there's at least one broken manifest Steps to reproduce: 1. Install several puppet modules 2. Make a syntax error in one or more installed manifests 3. Query host/production/resource_types/*?kind=class 4. Query the same url again Expected result: Step #3 and #4 returns the same result, containing parseable all classes *) Actual result: Step #3 fails with an error reporting the ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-41) Puppet returns different result non-existent services on EL and Debian
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-41 Puppet returns different result non-existent services on EL and Debian Change By: Michelle Johansen Assignee: AndrewParker 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-41) Puppet returns different result non-existent services on EL and Debian
Title: Message Title
Michelle Johansen commented on an issue
Re: Puppet returns different result non-existent services on EL and Debian
Eric Sorenson Can you weigh in here pls? And if this is a need for PUP 3.5.0
Add Comment
Puppet / PUP-41
Puppet returns different result non-existent services on EL and Debian
EL and Debian have different results for service resources that don't exist. On EL, `puppet resource service abcdefg` will return service { 'abcdefg': ensure = 'stopped', enable = 'false', } On Debian, this will return Error: Could not run: Could not find init script for 'abcdefg' While what is returned by puppet on EL is te...
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-202) Signal traps are broken under ruby 2.0.0
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-202 Signal traps are broken under ruby 2.0.0 Change By: Michelle Johansen Assignee: EricSorenson AndrewParker 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-202) Signal traps are broken under ruby 2.0.0
Title: Message Title Michelle Johansen commented on an issue Re: Signal traps are broken under ruby 2.0.0 Andrew Parker Can we get an update here if it's already fixed? Add Comment Puppet / PUP-202 Signal traps are broken under ruby 2.0.0 Ruby 2.0.0 does not allow Puppet to call some signal handlers as we perform a lot of operations that are unsafe within the context of a signal trap. For example, anything that manipulates a mutex is off limits. This includes sending messages to Logger objects that are using mutexes internally: http://www.mikeperham.com/2013/02/23/signal-handling-with-r... 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-536) Create endpoint for enumerating environments
Title: Message Title Michelle Johansen commented on an issue Re: Create endpoint for enumerating environments Eric Sorenson or Andrew Parker Can one of you please verify that this was pushed past 3.5.0? Add Comment Puppet / PUP-536 Create endpoint for enumerating environments Much of the Node Classifier and Continuous Delivery work is predicated on improved support for environments, and one significant gap is the absence of a way to enumerate the environments known to a puppet master. 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-1440) PR (2260): Fix unused argument in file_spec.rb - glennpratt
Title: Message Title gepetto-bot commented on an issue Re: PR (2260): Fix unused argument in file_spec.rb - glennpratt peterhuene commented: Could you prefix your commit message to have `(maint)` since this isn't directly related to an issue? Thanks. Add Comment Puppet / PUP-1440 PR (2260): Fix unused argument in file_spec.rb - glennpratt h2. Fix unused argument in file_spec.rb * Author: Glenn Pratt glennpr...@gmail.com * Company: Acquia * Github ID: [glennpratt|https://github.com/glennpratt] * [Pull Request 2260 Discussion|https://github.com/puppetlabs/puppet/pull/2260] * [Pull Request 2260 File Diff|https://github.com/puppetlabs/puppet/pull/2260/files] h2. Pull Request Descripti... 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-1440) PR (2260): Fix unused argument in file_spec.rb - glennpratt
Title: Message Title gepetto-bot commented on an issue Re: PR (2260): Fix unused argument in file_spec.rb - glennpratt glennpratt commented: Done and done. Add Comment Puppet / PUP-1440 PR (2260): Fix unused argument in file_spec.rb - glennpratt h2. Fix unused argument in file_spec.rb * Author: Glenn Pratt glennpr...@gmail.com * Company: Acquia * Github ID: [glennpratt|https://github.com/glennpratt] * [Pull Request 2260 Discussion|https://github.com/puppetlabs/puppet/pull/2260] * [Pull Request 2260 File Diff|https://github.com/puppetlabs/puppet/pull/2260/files] h2. Pull Request Descripti... 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-574) NTFS ACL module
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-574 NTFS ACL module Change By: Michelle Johansen Fix Version/s: 3.5.0 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 (FACT-16) Improve External Fact Documentation
Title: Message Title Justin Holguin assigned an issue to Justin Holguin Facter / FACT-16 Improve External Fact Documentation Change By: Justin Holguin Assignee: JustinHolguin 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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Michelle Johansen Fix Version/s: 3.6.0 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-850) Puppet 3.6 Deprecations in Preparation for Puppet 4
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-850 Puppet 3.6 Deprecations in Preparation for Puppet 4 Change By: Michelle Johansen Fix Version/s: 3.5.0 Fix Version/s: 3.6.0 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-776) Deprecate non-UTF-8 encodings for textual content
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-776 Deprecate non-UTF-8 encodings for textual content Change By: Michelle Johansen Fix Version/s: 3.5.0 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-876) upstart service operating system confine should include redhat and centos
Title: Message Title Michelle Johansen commented on an issue Re: upstart service operating system confine should include redhat and centos Michael Stahnke Is this needed for 3.5.0 or is still on the nice to have list? Add Comment Puppet / PUP-876 upstart service operating system confine should include redhat and centos RedHat EL 6 and Centos 6 both use upstart for init. The upstart service type should be able to be used on those systems as well. I have done some very minor testing to make sure it at least works to ensure services are running and stopped. 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-923) Try out Fedora 20
Title: Message Title Michelle Johansen commented on an issue Re: Try out Fedora 20 Michael Stahnke Can we get an update from your team here or a link to the proper release issues please Add Comment Puppet / PUP-923 Try out Fedora 20 Exploration of how puppet behaves in Fedora 20 (slated for 12/10/13 release). This is the closest thing to a proxy for RHEL7 that we may have in the 3.5 timeframe. Additional tickets may be generated as a result of this activity. 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-945) Unify puppet subcommands as 'puppet-command' programs
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-945 Unify puppet subcommands as 'puppet-command' programs Change By: Michelle Johansen Fix Version/s: 3.5.0 Fix Version/s: 3.6.0 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-923) Try out Fedora 20
Title: Message Title Michael Stahnke commented on an issue Re: Try out Fedora 20 We haven't had time to dive into RHEL 7/Fedora 20 yet. This is still huge if our stuff doesn't work on it. I think we (platform + ESO) should try to carve out some time for this effort. Add Comment Puppet / PUP-923 Try out Fedora 20 Exploration of how puppet behaves in Fedora 20 (slated for 12/10/13 release). This is the closest thing to a proxy for RHEL7 that we may have in the 3.5 timeframe. Additional tickets may be generated as a result of this activity. 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-1433) Deprecate manifest setting and update packaging
Title: Message Title Michelle Johansen commented on an issue Re: Deprecate manifest setting and update packaging Dan Lidral-Porter Is this needed for PUP 3.5.0? Add Comment Puppet / PUP-1433 Deprecate manifest setting and update packaging With the new dynamic environments support, we are no longer going to support an implicit environment where the manifest location is set explicitly in Puppet's configuration. Instead, packaging should ensure that the environments directory is populated with a default environment with a site.pp 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-1166) Add better error message for strict variables (current parser)
Title: Message Title Michelle Johansen commented on an issue Re: Add better error message for strict variables (current parser) Henrik Lindberg Is this still on the list for PUP 3.5.0? Add Comment Puppet / PUP-1166 Add better error message for strict variables (current parser) In 3x variable references result in undef if variable has not been set. In 3.5 an option has been added 'strict_variables' that enforces that all variables exist. It can not be on by default in 3.5. since the binder auto loads and expects to find basic facts as variables, but there are lots of tests that trigger runs without facts. This ticket is to... 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-312) Get MSI packages so that we can test windows against packages.
Title: Message Title Michelle Johansen commented on an issue Re: Get MSI packages so that we can test windows against packages. Any update here? What's needed to get this moving forward? Add Comment Puppet / PUP-312 Get MSI packages so that we can test windows against packages. Need to check with delivery and see if the pipeline can produce msi packages. * need to move to using re's packaging system (generate MSI on commit) * be able to build stable vs master puppet with appropriately versioned MSIs so that they don't collide on builds.puppetlabs.lan (sha based on the installer not puppet) * ideally, wix packaging files sho... 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-1440) PR (2260): Fix unused argument in file_spec.rb - glennpratt
Title: Message Title gepetto-bot commented on an issue Re: PR (2260): Fix unused argument in file_spec.rb - glennpratt Pull request (maint) Fix unused argument and variable in file_spec.rb has been closed. Add Comment Puppet / PUP-1440 PR (2260): Fix unused argument in file_spec.rb - glennpratt h2. Fix unused argument in file_spec.rb * Author: Glenn Pratt glennpr...@gmail.com * Company: Acquia * Github ID: [glennpratt|https://github.com/glennpratt] * [Pull Request 2260 Discussion|https://github.com/puppetlabs/puppet/pull/2260] * [Pull Request 2260 File Diff|https://github.com/puppetlabs/puppet/pull/2260/files] h2. Pull Request Descripti... 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-312) Get MSI packages so that we can test windows against packages.
Title: Message Title Matthaus Owens commented on an issue Re: Get MSI packages so that we can test windows against packages. Michelle Johansen Joshua Cooper and I met and hashed out some short and medium term tasks to move this forward. His notes have the details, so we'll be opening some related tickets based on those notes. Add Comment Puppet / PUP-312 Get MSI packages so that we can test windows against packages. Need to check with delivery and see if the pipeline can produce msi packages. * need to move to using re's packaging system (generate MSI on commit) * be able to build stable vs master puppet with appropriately versioned MSIs so that they don't collide on builds.puppetlabs.lan (sha based on the installer not puppet) * ideally, wix packaging files sho... 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 (MCO-157) PE PMT does not work with local tarballs
Title: Message Title Alex Dreyer created an issue MCollective / MCO-157 PE PMT does not work with local tarballs Issue Type: New Feature Assignee: Unassigned Created: 14/Jan/14 3:39 PM Priority: Normal Reporter: Alex Dreyer PE PMT doesn't correctly install local tarballs anymore it tries to convert the path to a module name and ask forge about it. This is high priority because it breaks the installer. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1150) Race condition in Puppet::Util::Lockfile
Title: Message Title Peter Huene commented on an issue Re: Race condition in Puppet::Util::Lockfile I'll comment on the test change on the commit, so we don't have two places where we're discussing the code. Thanks for the other fix to file_spec. Add Comment Puppet / PUP-1150 Race condition in Puppet::Util::Lockfile Puppet::Util::Lockfile does not exclude other processes from acquiring a lock between the time it checks if the lock file exists and when it writes to the lock file. This allows for a race condition, and two puppet processes started simultaneously are likely to acquire the same lock. This has been witnessed in the wild where I work because we may have... 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-1389) Windows File resources generating 0 byte files and not populating file via content or source when title has -
Title: Message Title Joshua Cooper commented on an issue Re: Windows File resources generating 0 byte files and not populating file via content or source when title has - When using WideString, I see that the ReplaceFile target string claims to be UTF-16LE, but the Win32 API is actually called with a US-ASCII string: `054ea0b8 63 3a 2f 6a 65 6e 6b 69 6e 73 2d 73 6c 61 76 65 c:/jenkins-slave `054ea0c8 2e 65 78 65 00 00 00 00 b4 07 19 27 00 54 02 80 .exe...'.T.. When using String#encode, sometimes the Win32 API is invoked with a string that doesn't contain a double NULL terminator: `0600f160 63 00 3a 00 2f 00 6a 00 65 00 6e 00 6b 00 c.:./.j.e.n.k. `0600f16e 69 00 6e 00 73 00 2d 00 73 00 6c 00 61 00 i.n.s.-.s.l.a. `0600f17c 76 00 65 00 2e 00 65 00 78 00 65 00 32 00 v.e...e.x.e.2. `0600f18a 30 00 31 00 34 00 30 00 31 00 31 00 34 00 0.1.4.0.1.1.4. `0600f198 2d 00 39 00 34 00 30 00 2d 00 6a 00 34 00 -.9.4.0.-.j.4. `0600f1a6 36 00 74 00 34 00 00 ff ff ff ff ff ff ff 6.t.4. Thanks to Peter Huene for finding the problem in the win32-api gem we are using. It's using StringValuePtr instead of StringValueCStr. For some reason, only Win2012 seems to complain about it when it happens. We should be able to work around the issue for now by appending an extra NULL terminator. Add Comment Puppet / PUP-1389 Windows File resources generating 0 byte files and not populating file via content or source when title has -
Jira (FACT-203) PR (598): Redirect Facter::Util::Resolution.exec's stderr to /dev/null - ghoneycutt
Title: Message Title gepetto-bot commented on an issue Re: PR (598): Redirect Facter::Util::Resolution.exec's stderr to /dev/null - ghoneycutt stschulte commented: @ghoneycutt Is there a related jira ticket for the pull request? Are there known non-fatal errors that are seen on stderr and we don't want to have in the facter output? Since the `exec` method also ommits the return code we'll now also ignore probable legit error messages that the user may be able to react to or may file a ticket that facter makes assumptions about the behaviour of a command that are not true for all environments. These facter bugs may be harder to detect if we discard stderr completly. Add Comment Facter / FACT-203 PR (598): Redirect Facter::Util::Resolution.exec's stderr to /dev/null - ghoneycutt h2. Redirect Facter::Util::Resolution.exec's stderr to /dev/null * Author: Garrett Honeycutt git...@garretthoneycutt.com * Company: * Github ID: [ghoneycutt|https://github.com/ghoneycutt] * [Pull Request 598 Discussion|https://github.com/puppetlabs/facter/pull/598] * [Pull Request 598 File Diff|https://github.com/puppetlabs/facter/pull/598/files]... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1020) PR (2153): (#18342) WIP - Iristyle
Title: Message Title gepetto-bot commented on an issue Re: PR (2153): (#18342) WIP - Iristyle Iristyle commented: All tests pass, but I think the comment from Andy needs to be revisited ... Add Comment Puppet / PUP-1020 PR (2153): (#18342) WIP - Iristyle h2. (#18342) WIP * Author: Ethan J. Brown * Company: * Github ID: [Iristyle|https://github.com/Iristyle] * [Pull Request 2153 Discussion|https://github.com/puppetlabs/puppet/pull/2153] * [Pull Request 2153 File Diff|https://github.com/puppetlabs/puppet/pull/2153/files] h2. Pull Request Description (webhooks-id: 4b89fe99d8f9a009b680... 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.
