Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Neil Binney updated an issue Puppet Task Runner / BOLT-832 Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9207) puppet lookup --compile returns incorrect results when trusted facts define environment
Title: Message Title Neil Binney updated an issue Puppet / PUP-9207 puppet lookup --compile returns incorrect results when trusted facts define environment Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9173) Warning messages while adding AD users into local group in Windows
Title: Message Title Neil Binney moved an issue Puppet / PUP-9173 Warning messages while adding AD users into local group in Windows Change By: Neil Binney Key: CODEMGMT PUP - 1198 9173 Project: Code Management Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-4072) HA out-of-sync after restart
Title: Message Title Neil Binney updated an issue PuppetDB / PDB-4072 HA out-of-sync after restart CS Triage CS Priority: Major CS Frequency: 1 1-5% CS Severity: 3 Serious CS Business Value: 4 CS Impact. Impacting major customer. Puppetdb resync on startup is noted in the Docs, but it should not need to resync so much data following a DB restart. Such outages will impact HA and customers DR strategy. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-4072) HA out-of-sync after restart
Title: Message Title Neil Binney updated an issue PuppetDB / PDB-4072 HA out-of-sync after restart Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9077) Inconsistent undef value received by 4.x API Ruby functions after touched by 3.x Ruby function
Title: Message Title Neil Binney updated an issue Puppet / PUP-9077 Inconsistent undef value received by 4.x API Ruby functions after touched by 3.x Ruby function Change By: Neil Binney CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8962) Type and provider info should be logged when prefetch fails
Title: Message Title Neil Binney updated an issue Puppet / PUP-8962 Type and provider info should be logged when prefetch fails Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8956) puppet agent doesn't run properly when avast anti-virus running
Title: Message Title Neil Binney updated an issue Puppet / PUP-8956 puppet agent doesn't run properly when avast anti-virus running Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Neil Binney updated an issue Puppet / PUP-8900 "puppet facts upload" face only tries first master in server_list Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8957) [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3
Title: Message Title Neil Binney updated an issue Puppet / PUP-8957 [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3 Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8710) Smarter cached catalogs
Title: Message Title Neil Binney updated an issue Puppet / PUP-8710 Smarter cached catalogs Change By: Neil Binney CS Priority: Normal CS Impact: There is a workaround where facts can be uploaded, but requires some configuration to get working.With the agent running in cron run facts locally on the agent and compare against threshold, If the threshold has not been breached the agent can continue to run against the cached catalog.Increasing compile masters in the setup would be recommend to handle additional load rather than relying on cached catalogs.It it a good idea but would require considerable update to the Puppet Agent. further user cases will be needed to make business case for this feature to be resourced. Number of large scale customers using cached catalogs is quite low. CS Severity: 2 - Annoyance CS Business Value: 2 - $$$ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7918) puppet fails to change user group membership if directory group names have spaces
Title: Message Title Neil Binney updated an issue Puppet / PUP-7918 puppet fails to change user group membership if directory group names have spaces Change By: Neil Binney CS Priority: Needs Priority Zendesk Ticket IDs: https://puppetlabs.zendesk.com/agent/tickets/29329 Zendesk Ticket Count: 1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1832) Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.
Title: Message Title Neil Binney created an issue Facter / FACT-1832 Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. Issue Type: Bug Assignee: Unassigned Attachments: facterdebug.txt, truss-output.txt Created: 2018/03/09 8:47 AM Environment: Publisher: solaris Version: 0.5.11 Build Release: 5.11 Branch: 0.175.3.29.0.4.0 Puppet: 4.10.4 Priority: Normal Reporter: Neil Binney When running facter in a zone following error occurs; 2018-03-07 12:22:40.806413 DEBUG puppetlabs.facter - resolving virtualization facts. 2018-03-07 12:22:40.806612 DEBUG puppetlabs.facter - resolving ldom facts. 2018-03-07 12:22:40.806754 DEBUG puppetlabs.facter - resolving processor facts. 2018-03-07 12:22:40.807161 DEBUG leatherman.execution:92 - executing command: /sbin/uname -p 2018-03-07 12:22:40.809843 DEBUG | - sparc 2018-03-07 12:22:40.810153 DEBUG leatherman.execution:556 - process exited with status code 0. terminate called after throwing an instance of 'facter::util::solaris::kstat_exception' what(): kstat_read failed: Permission denied (13) facter runs correctly on the global zone. 3530/1: 0.184177 ioctl(7, KSTAT_IOC_READ, "pic3") = 1410238 3530/1: 0.184229 ioctl(7, KSTAT_IOC_READ, "counters") Err#13 EACCES 3530/1: 0.185395 fstat64(2, 0xFFBFDF58) = 0 3530/1: 0.185468 write(2, " t e r m i n a t e c a".., 48) = 48 3530/1: 0.185546 write(2, " f a c t e r : : u t i l".., 38) = 38 3530/1: 0.185622 write(2, " '\n", 2) = 2 3530/1: 0.185795 write(2, " w h a t ( ) : ", 11) = 11 3530/1: 0.185870 write(2, " k s t a t _ r e a d f".., 41) = 41 3530/1: 0.185955 write(2, "\n", 1) = 1 3530/1: 0.186056 sigaction(SIGABRT, 0x, 0xFFBFE250) = 0 3530/1: 0.186107 sigaction(SIGABRT, 0xFFBFE100, 0xFFBFE1A0) = 0 3530/1: 0.186140 lwp_sigmask(SIG_SETMASK, 0x, 0x, 0
Jira (PUP-8328) Mount resource does not allow whitespace in name
Title: Message Title Neil Binney updated an issue Puppet / PUP-8328 Mount resource does not allow whitespace in name Change By: Neil Binney Zendesk Ticket IDs: 28692 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8328) Mount resource does not allow whitespace in name
Title: Message Title
Neil Binney updated an issue
Puppet / PUP-8328
Mount resource does not allow whitespace in name
Change By:
Neil Binney
Zendesk Ticket IDs:
28692
The {{mount}} resource should allow whitespace in the name. Currently any whitespace returns the error;{noformat}"Error: Parameter name failed on Mount [testmount]: name must not contain whitespace"{noformat}Puppet should either allow whitespace in the name or recognise the {{\040}} used in the fstab. Currently {{\040}} is interpreted literally by Puppet;{noformat}"Could not evaluate: Execution of '/bin/mount /var/tmp/test\040mount' returned 1: mount: can't find /var/tmp/test\040mount in /etc/fstab"{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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-8328) Mount resource does not allow whitespace in name
Title: Message Title Neil Binney created an issue Puppet / PUP-8328 Mount resource does not allow whitespace in name Issue Type: Improvement Affects Versions: PUP 5.3.3 Assignee: Unassigned Components: Types and Providers Created: 2018/01/08 4:23 AM Priority: Normal Reporter: Neil Binney The mount resource should allow whitespace in the name. Currently any whitespace returns the error; "Error: Parameter name failed on Mount [testmount]: name must not contain whitespace" Puppet should either allow whitespace in the name or recognise the \040 used in the fstab. Currently \040 is interpreted literally by Puppet;
Jira (PUP-2820) "Array" settings get misleading formatting for default values and error reporting
Title: Message Title Neil Binney assigned an issue to Neil Binney Puppet / PUP-2820 "Array" settings get misleading formatting for default values and error reporting Change By: Neil Binney Assignee: Neil Binney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-235) Create encrypted variables in tasks
Title: Message Title Neil Binney created an issue Puppet Task Runner / BOLT-235 Create encrypted variables in tasks Issue Type: New Feature Assignee: Unassigned Components: CLI, UX Created: 2017/11/23 2:17 AM Priority: Normal Reporter: Neil Binney Ability to encrypt variables within tasks / metatdata. If you do not want to pass a password from the command line everytime that a task is run there is currently no way to encrypt it with in the task. This means potential including password / sensitive data as plaintext within a task. Add Comment
Jira (PDB-3712) Delete/Purge an arbitrary report from the database
Title: Message Title Neil Binney created an issue PuppetDB / PDB-3712 Delete/Purge an arbitrary report from the database Issue Type: New Feature Assignee: Unassigned Components: PE, PuppetDB Created: 2017/10/13 2:05 AM Priority: Normal Reporter: Neil Binney Reports are timestamped by the agent node. If the time on the node is wrong this can result in reports in the puppetdb with dates in the furture. When the time on the agent node is corrected puppetdb will discard the fresh reports as the date is older than the previous report. To resolve this user should be able to; 1) delete/purge an arbitrary report from the database via PQL. 2) View reports based on a timestamp of when they were received by Puppetdb. Add Comment
Jira (PDB-3618) Applying PR 2338 required restart of puppetdb service.
Title: Message Title Neil Binney updated an issue PuppetDB / PDB-3618 Applying PR 2338 required restart of puppetdb service. Change By: Neil Binney Walmart found after After applying PR 2338 pe-puppetdb.service failed to start.Issuing `systemctl start pe-puppetdb.service` did not start the service. Not correctly, at least. `systemctl status` showed that it was `active (running)` but the logs showed no activity, we believe because the system wasn't listening on TCP 8081.Issuing systemctl restart pe-puppetdb.service` brought puppetdb back online. Of note: `systemctl start pe-puppetdb.service` didn't work because the `status` was already showing as `running (active)`. Walmart encountered this across two environments.https://github.com/puppetlabs/puppetdb/pull/2338https://puppetlabs.zendesk.com/agent/tickets/26626 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 (PDB-3618) Applying PR 2338 required restart of puppetdb service.
Title: Message Title Neil Binney created an issue PuppetDB / PDB-3618 Applying PR 2338 required restart of puppetdb service. Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2017/07/19 7:06 AM Priority: Normal Reporter: Neil Binney Walmart found after applying PR 2338 pe-puppetdb.service failed to start. Issuing `systemctl start pe-puppetdb.service` did not start the service. Not correctly, at least. `systemctl status` showed that it was `active (running)` but the logs showed no activity, we believe because the system wasn't listening on TCP 8081. Issuing systemctl restart pe-puppetdb.service` brought puppetdb back online. Of note: `systemctl start pe-puppetdb.service` didn't work because the `status` was already showing as `running (active)`. Walmart encountered this across two environments. https://github.com/puppetlabs/puppetdb/pull/2338 https://puppetlabs.zendesk.com/agent/tickets/26626
