Jira (PUP-6772) Decision - Support extended UTF-8 characters in tags?
Title: Message Title James Stocks commented on PUP-6772 Re: Decision - Support extended UTF-8 characters in tags? Looks like this was actually done in PUP-7579 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7076) Maintaining existing eyaml when adopting Hiera 5
Title: Message Title James Stocks updated an issue Puppet / PUP-7076 Maintaining existing eyaml when adopting Hiera 5 Change By: James Stocks QA Risk Assessment Reason: We should have some acceptance testing to protect against regression with eyaml QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7230) acceptance: hiera5 eyaml backend and deep merges
Title: Message Title James Stocks updated an issue Puppet / PUP-7230 acceptance: hiera5 eyaml backend and deep merges Change By: James Stocks QA Risk Assessment: Needs Assessment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7242) review flanders hiera5 docs
Title: Message Title James Stocks commented on PUP-7242 Re: review flanders hiera5 docs Docs currently about 50% done; look good so far. Putting the ticket back on to "To Do" and default assignee until docs are ready for review. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7242) review flanders hiera5 docs
Title: Message Title James Stocks assigned an issue to Nicholas Fagerlund Puppet / PUP-7242 review flanders hiera5 docs Change By: James Stocks Assignee: James Stocks Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7242) review flanders hiera5 docs
Title: Message Title James Stocks updated an issue Puppet / PUP-7242 review flanders hiera5 docs Change By: James Stocks Component/s: QA Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7242) review flanders hiera5 docs
Title: Message Title James Stocks updated an issue Puppet / PUP-7242 review flanders hiera5 docs Change By: James Stocks Sprint: PDE 2017-03-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7226) Remove vendored Rgen gem
Title: Message Title James Stocks commented on PUP-7226 Re: Remove vendored Rgen gem I don't think this needs any new/explicit QA; but might this change benefit from a release note? (Might any users reasonably be running their own ruby code against our vendored Ruby?) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7237) fix puppet acceptance Rake tasks
Title: Message Title James Stocks updated an issue Puppet / PUP-7237 fix puppet acceptance Rake tasks Change By: James Stocks QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6854) OSX: Warning output when using puppet resource service
Title: Message Title James Stocks created an issue Puppet / PUP-6854 OSX: Warning output when using puppet resource service Issue Type: Bug Assignee: Unassigned Created: 2016/11/01 3:47 AM Environment: puppet-agent (master) 1.7.1.179.g4d636ee SUITE_COMMIT 4d636ee2ab6b598e10b9b19019ffa046bc66f534 TEST_TARGET osx1012-64a Priority: Normal Reporter: James Stocks puppet resource service .* always seems to include some warning output. puppet seems to be able to query and modify services despite the warning. rfoie66a86vs98y:~ root# puppet resource service puppet Warning: The /System/Library/LaunchDaemons/com.apple.jetsamproperties.Mac.plist plist does not contain a 'label' key; Puppet is skipping it
Jira (PUP-6829) Improve agent mutex on Windows
Title: Message Title James Stocks created an issue Puppet / PUP-6829 Improve agent mutex on Windows Issue Type: Improvement Affects Versions: PUP 4.7.1 Assignee: Unassigned Components: Windows Created: 2016/10/17 2:27 PM Priority: Normal Reporter: James Stocks Current behaviour: puppet agent on Windows starts ruby.exe, that takes some time to launch, then ruby checks for an existing agent PID file and exits if puppet agent is already running Suggestion: Improve this so that puppet agent exits immediately. The time to launch ruby can be significant (~12 seconds on our Windows 2008 vmpooler VMs) and may cause complications with newer PE features that run puppet on demand.
Jira (PUP-6817) Improve how corrective_change is determined for exec resource
Title: Message Title
James Stocks created an issue
Puppet / PUP-6817
Improve how corrective_change is determined for exec resource
Issue Type:
Improvement
Assignee:
Kylo Ginsberg
Components:
Client
Created:
2016/10/13 1:05 PM
Priority:
Normal
Reporter:
James Stocks
Raising this as an enhancement rather than a bug; as the current behaviour has been reviewed and accepted as a document item (PE-17036)
Current behaviour:
If I have an exec resource with a descriptive title like:
exec { 'My important log file' :
command => '/usr/bin/touch /tmp/logfile',
unless => '/usr/bin/test -e /tmp/logfile',
Jira (PUP-6772) Decision - Support extended UTF-8 characters in tags?
Title: Message Title James Stocks updated an issue Puppet / PUP-6772 Decision - Support extended UTF-8 characters in tags? Change By: James Stocks Summary: Decision - Support extended UTF-8 characters in tags ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6772) Support extended UTF-8 characters in tags
Title: Message Title James Stocks assigned an issue to Larissa Lane Puppet / PUP-6772 Support extended UTF-8 characters in tags Change By: James Stocks Assignee: Larissa Lane Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6702) Windows service in Paused state cannot be managed
Title: Message Title James Stocks created an issue Puppet / PUP-6702 Windows service in Paused state cannot be managed Issue Type: Bug Affects Versions: PUP 4.6.2 Assignee: Unassigned Components: Windows Created: 2016/09/14 3:33 AM Environment: TEST_TARGET=windows2008r2-64a SUITE_VERSION=1.6.2.135.g8a48f21 SUITE_COMMIT=8a48f210f6901be0edba16eb49c1bfbfb07d338b Priority: Normal Reporter: James Stocks When a service is in the Paused state; it's 'ensure' property cannot be managed by Puppet Note that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage ) To reproduce: Install puppet-agent
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title James Stocks commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions John Duarte Thomas Hallgren - the acceptance test differs here from the intended reproduction steps, in that it reconfigures environmentpath instead of putting the faulty environment into the default environment path. I'm not sure if that is relevant; but it might relate to the unexpected stack trace in Thomas' last comment? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3989) output of puppet module generate does not include a .fixtures.yml file causing tests to fail
Title: Message Title James Stocks commented on PUP-3989 Re: output of puppet module generate does not include a .fixtures.yml file causing tests to fail +1 on this ticket. Related to this (though not a PUP issue) - our module authoring documentation should guide new authors towards using rspec and all the provided rake checks while writing their puppet code. This issue (missing .fixtures.yml) leaves a new author in a position where the documentation doesn't explain what to do; and the provided rake tasks to prepare for forge publishing just don't work Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title James Stocks assigned an issue to James Stocks Puppet / PUP-6295 Include corrective_change field in reports Change By: James Stocks Assignee: qa James Stocks Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title James Stocks commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) Ethan Brown I submitted a basic acceptance test that would catch this in future: https://github.com/puppetlabs/puppet/pull/5160 I notice that there are existing tests for user and group; and that they test thoroughly by querying the users or groups natively (e.g. here ) and then comparing the results from 'puppet resource' with the resources found natively. I cannot immediately create such a test for 'resource service' as there isn't an equivalent host.service_list in beaker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title James Stocks updated an issue Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: James Stocks QA Highest Test Level: Acceptance QA Risk Assessment: High QA Risk Severity Reason: Puppet cannot work with service resources QA Risk Probability: Medium QA Risk Severity: High QA Highest Test Level Reason: We should ensure 'puppet resource service' works on all of the agent OSs we support QA Status: Reviewed Add Comment
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title James Stocks commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) I think we are also seeing this in pxp-agent's acceptance tests on windows-10ent-32 (32bit) When I log into the host, any use of "puppet agent resource ..." results in WARNING: Failed to retreive description for the XboxNetApiSvc service. Error: Could not run: No such device or address - QueryServiceConfig2: The handle is invalid.> Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6295) Include corrective_change field in reports
Title: Message Title James Stocks updated an issue Puppet / PUP-6295 Include corrective_change field in reports Change By: James Stocks QA Risk Assessment Reason: New report data. QA Highest Test Level: Acceptance QA Risk Probability Reason: Future changes may cause regression or unintended logic here QA Risk Assessment: High QA Risk Severity Reason: Reporting in PE will be incorrect QA Risk Probability: Medium QA Risk Severity: High QA Status: Reviewed Add Comment
Jira (FACT-1419) Add a 'privileged' element to the identity fact
Title: Message Title James Stocks updated an issue Facter / FACT-1419 Add a 'privileged' element to the identity fact Previous comment was incorrect - user was in Administrator group; but the command prompt (and therefore the facter process) did have elevated privileges. Attached screenshot shows privileged is true when facter is run with elevated privileges Change By: James Stocks Attachment: Screen Shot 2016-05-23 at 18.22.15.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1419) Add a 'privileged' element to the identity fact
Title: Message Title James Stocks updated an issue Facter / FACT-1419 Add a 'privileged' element to the identity fact Attaching screenshot relating to previous comment to show that james_admin is in the local Administrators group Change By: James Stocks Attachment: Screen Shot 2016-05-23 at 17.55.10.png Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1419) Add a 'privileged' element to the identity fact
Title: Message Title
James Stocks commented on FACT-1419
Re: Add a 'privileged' element to the identity fact
Tested in puppet-agent 1.5.0.60.g4aac788
Appears to work on EL7, but on Windows 2012 R2 it returns false for a local administrator user
EL7 -
-bash-4.2$ facter identity
{
gid => 1000,
group => "james",
privileged => false,
uid => 1000,
user => "james"
}
-bash-4.2$ exit
logout
Jira (FACT-1419) Add a 'privileged' element to the identity fact
Title: Message Title James Stocks assigned an issue to James Stocks Facter / FACT-1419 Add a 'privileged' element to the identity fact Change By: James Stocks Assignee: qa James Stocks Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1419) Add a 'privileged' element to the identity fact
Title: Message Title James Stocks updated an issue Facter / FACT-1419 Add a 'privileged' element to the identity fact Change By: James Stocks QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title James Stocks commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Henrik Lindberg - yes. It was using the pxp-agent pre-suite (here) - there is one "master" host and one agent. We start "puppetserver" service on the master; then set it as the puppet server for the agent and generate certs. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title
James Stocks updated an issue
Puppet / PUP-6241
puppet agent ostensibly succeeds when environment directory has wrong permissions
Change By:
James Stocks
I noticed this when using beaker methods to create test environments*To reproduce:* * Create a new environment (e.g _cd /etc/puppetlabs/code/environments_ then _cp -r production my_test_ ) * Edit the environment so it has some resources e.g. edit site.pp to have something like{code}node default { notify {'Hello agent':}}{code} * On the agent, run _puppet agent -t --environment my_test_ and confirm that you see the notify resource being applied{code}[root@nhttpwkcahz856y ~]# puppet agent -t --environment my_testInfo: Using configured environment 'my_test'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for nhttpwkcahz856y.delivery.puppetlabs.netInfo: Applying configuration version '1461841741'Notice: Hello agentNotice: /Stage[main]/Main/Node[default]/Notify[ Notify resources cause a Puppet run to have a 'changed' outcome Hello agent ]/message: defined 'message' as 'Hello agent'Notice: Applied catalog in 0.01 seconds{code} * On the master, apply _chmod 644 /etc/puppetlabs/code/environments/my_test * On the agent, run _puppet agent -t --environment my_test_ again*Expected:* * Permissions are wrong, agent should fail with some error that the environment was unusable.*Actual:* * The agent appears to succeed, but with no resources applied{code}[root@nhttpwkcahz856y ~]# puppet agent -t --environment my_testInfo: Using configured environment 'my_test'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for nhttpwkcahz856y.delivery.puppetlabs.netInfo: Applying configuration version '1461841854'Notice: Applied catalog in 0.01 seconds{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title James Stocks created an issue Puppet / PUP-6241 puppet agent ostensibly succeeds when environment directory has wrong permissions Issue Type: Bug Affects Versions: PUP 4.4.2 Assignee: Unassigned Created: 2016/04/28 4:12 AM Environment: puppet-agent stable 1.4.1.139.ge06bf91 1x master and 1x agent - both el7 Priority: Normal Reporter: James Stocks I noticed this when using beaker methods to create test environments To reproduce: Create a new environment (e.g cd /etc/puppetlabs/code/environments then cp -r production my_test ) Edit the environment so it has some resources e.g. edit site.pp to have something like
Jira (PUP-5801) exec resource may lose return code if command terminated
Title: Message Title James Stocks updated an issue Puppet / PUP-5801 exec resource may lose return code if command terminated Change By: James Stocks Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5806) exec on Windows - command string interpreted differently than in cmd
Title: Message Title James Stocks created an issue Puppet / PUP-5806 exec on Windows - command string interpreted differently than in cmd Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/02/03 4:31 AM Priority: Minor Reporter: James Stocks In Windows Command Prompt, on a box with cygwin I can do the following to sleep a while and ignore the return code: sleep 5 || true However the following manifest appears to be the same command, but does not work:
Jira (PUP-5801) exec resource may lose return code if command terminated
Title: Message Title James Stocks created an issue Puppet / PUP-5801 exec resource may lose return code if command terminated Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/02/02 3:56 AM Environment: el7 Priority: Normal Reporter: James Stocks Reproduction: Open 2 terminals to a host In one terminal, run '/bin/sleep 100' In the other terminal, after a couple of seconds find the pid of sleep and execute 'kill SIGALARM [pid]'
Jira (PUP-5801) exec resource may lose return code if command terminated
Title: Message Title
James Stocks updated an issue
Puppet / PUP-5801
exec resource may lose return code if command terminated
Change By:
James Stocks
*Reproduction:* * Open 2 terminals to a an agent host * In one terminal, run '/bin/sleep 100' * In the other terminal, after a couple of seconds find the pid of sleep and execute 'kill SIGALARM \[pid\]' * In the first terminal, echo $? to see the exit code - note that it is the [number of seconds sleep had remaining before it was signalled|http://linux.die.net/man/3/sleep]. * Now repeat in Puppet, with a module like:{code}class sleep { exec { 'sleep_a_while': command => '/bin/sleep 100', }}{code} * Run Puppet with this module included, and while the catalog run is stuck on the sleep, signal SIGALARM to sleep as before*Expected:* * The exec resource should fail because the returned value is \[seconds remaining\] and not 0*Actual:* * The exec does fail, but it appears that the return value has been lost:{noformat}Info: Using configured environment 'sleep'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Caching catalog for ybbp6dpgky283nf.delivery.puppetlabs.netInfo: Applying configuration version '1454413025'Error: /bin/sleep 300 returned instead of one of [0]Error: /Stage[main]/Sleep/Exec[sleep_a_while]/returns: change from notrun to 0 failed: /bin/sleep 300 returned instead of one of [0]{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and
Jira (PUP-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title James Stocks commented on PUP-5294 Re: Capability resource params without default values fail during env catalog compilation Nick Lewis I got it working The attached tar needed to be set up as a module in the modules dir; I was trying to use the tar'ed folder as an environment folder. Apologies for the noise. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title James Stocks commented on PUP-5294 Re: Capability resource params without default values fail during env catalog compilation Nick Lewis - I'm taking a 2nd look at this ticket with a view to adding an acceptance tests. Does the following output indicate that the bug is present? [root@dmvw844xdnqeql9 pup5294]# puppet job run --url https://dmvw844xdnqeql9.delivery.puppetlabs.net:8143 --environment pup5294 Starting deployment of pup5294 environment... java.lang.Exception: HTTP GET to https://dmvw844xdnqeql9.delivery.puppetlabs.net:8140/puppet/v3/environment/pup5294:500: Server Error: Pup5294::Consumer[foobar]: expects a value for parameter 'foo' in environment pup5294 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5480) Puppet does not apply inheritable SYSTEM permissions to directories it manages on Windows under certain circumstances
Title: Message Title James Stocks commented on PUP-5480 Re: Puppet does not apply inheritable SYSTEM permissions to directories it manages on Windows under certain circumstances Note that PCP-151 appears to be this same issue. I just tested with 1.2.7.422.g3af913f and the bug did not repeat. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title James Stocks updated an issue PuppetDB / PDB-1589 If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works Change By: James Stocks QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title James Stocks updated an issue PuppetDB / PDB-1589 If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works Change By: James Stocks QA Risk Severity: Medium QA Risk Probability: Low QA Risk Severity Reason: APIendpointwillbenon-functionalforcustomer;causeandworkaroundwillnotbeobvioustothecustomer QA Risk Assessment: Low QA Risk Probability Reason: Lowriskofregression;thisshouldbeaonce-in-timebugwhereauser-errorcasewasn'tbeinghandled QA Risk Assessment Reason: Unlikelytoregress Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title James Stocks commented on PDB-1589 Re: If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works Kenneth Barber - as far as I can see, it's not possible to have a null value in facter; and this issue only occurs when a mistake is made while generating JSON facts for PuppetDB. Facter seems to just remove a fact with no value - I tried creating a custom fact that is set to Ruby nil; this just results in the fact not being included in the node's fact list. A fact set to Ruby empty string results in a JSON empty string. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1589) If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works
Title: Message Title James Stocks created an issue PuppetDB / PDB-1589 If JSON null is passed in as a fact value to replace facts v4 then facts endpoint no longer works Issue Type: Bug Assignee: Unassigned Attachments: NullFact.json Components: PE Created: 2015/06/04 6:59 AM Priority: Normal Reporter: James Stocks Noticed this during QA of Puppet Enterprise... To reproduce: Send the attached JSON to replace facts v4 (note that osfamily has a JSON null value - this was due to a bug in our test data generator tool) Expected behaviour: I'm not sure. Either null should be accepted and handled
