Jira (FACT-1842) The ability to blocklist individual facts
Title: Message Title Nicky Kernohan commented on FACT-1842 Re: The ability to blocklist individual facts Yep its a duplicate, closing, thanks 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-9008) puppet-agent-5.5.4-1.el6.x86_64 on Scientfic Linux 6 fails to use upstart
Title: Message Title Nicky Kernohan commented on PUP-9008 Re: puppet-agent-5.5.4-1.el6.x86_64 on Scientfic Linux 6 fails to use upstart This is now hitting some PE customers 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan commented on PUP-6936 Re: unable to read last_run_summary.yaml from user Thanks Branan Riley, could we try and get changing the permissions on the last_run_summary into future sprint? Thank you 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan commented on PUP-6936 Re: unable to read last_run_summary.yaml from user Hi, any updates? If the change in the perms for the summary is fairly straightforward, can we try and aim to get this into the next Z release? Thanks Nicky 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan commented on PUP-6936 Re: unable to read last_run_summary.yaml from user Would it be possible to open up the whole cache dir to 755 permissions? 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Nicky Kernohan Affects Version/s: PUP 5.5.z Zendesk Ticket IDs: https://puppetlabs.zendesk.com/agent/tickets/30947https://puppetlabs.zendesk.com/agent/tickets/29674 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Nicky Kernohan Zendesk Ticket IDs: https://puppetlabs.zendesk.com/agent/tickets/30947https://puppetlabs.zendesk.com/agent/tickets/29674 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-8922) Look at the permissions of files in /cache/state/
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8922 Look at the permissions of files in /cache/state/ Change By: Nicky Kernohan CS Priority: Minor CS Severity: 2 - Annoyance CS Frequency: 1 - 1-5% of Customers 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-8922) Look at the permissions of files in /cache/state/
Title: Message Title Nicky Kernohan created an issue Puppet / PUP-8922 Look at the permissions of files in /cache/state/ Issue Type: Improvement Assignee: Unassigned Created: 2018/06/11 2:39 AM Priority: Normal Reporter: Nicky Kernohan Seens to affect all versions the state.yaml and transactionstore.yaml have group read and write permissions They are set in /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/defaults.rb Is there any reason for these two files to have group read and write permissions? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Nicky Kernohan CS Priority: Normal CS Impact: Customer wants to use this file to monitor their agent runs CS Severity: 3 - Serious CS Business Value: 2 - $$$ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received
Jira (PUP-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Nicky Kernohan Zendesk Ticket IDs: https://puppetlabs.zendesk.com/agent/tickets/29674 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-7664) "Function lookup() did not find a value for the name 'classes' on node"
Title: Message Title
Nicky Kernohan updated an issue
Puppet / PUP-7664
"Function lookup() did not find a value for the name 'classes' on node"
Change By:
Nicky Kernohan
Somewhere in between 78e175e6 and 27fdad2 of puppet, puppet server tests have started failing.Specifically, [ https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppetserver_integration-system_no-conditional_smoke-master/366/LAYOUT=redhat7-64ma-windows2008r2-64a,LDAP_TYPE=default,label=beaker/consoleFull ] , with output: {code} 10:26:01 p7145rmqxgo7fs9.delivery.puppetlabs.net (redhat7-64-1) 17:26:01$ curl --silent --cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem --key /etc/puppetlabs/puppet/ssl/private_keys/p7145rmqxgo7fs9.delivery.puppetlabs.net.pem --cert /etc/puppetlabs/puppet/ssl/certs/p7145rmqxgo7fs9.delivery.puppetlabs.net.pem https://p7145rmqxgo7fs9.delivery.puppetlabs.net:8140/puppet/v3/catalog/p7145rmqxgo7fs9.delivery.puppetlabs.net?environment=production | python -m json.tool10:26:01 {10:26:02 "issue_kind": "RUNTIME_ERROR",10:26:02 "message": "Server Error: Function lookup() did not find a value for the name 'classes' on node p7145rmqxgo7fs9.delivery.puppetlabs.net"10:26:02 }10:26:02 10:26:02 p7145rmqxgo7fs9.delivery.puppetlabs.net (redhat7-64-1) executed in 1.00 seconds10:26:02 Minitest::Assertion: FAIL: Expected catalog to contain current_code_id 3aafbd686b0f884f4519de1ebd6fdac5d2454d14..{code} On repro, the actual stack trace from logs is [ https://gist.github.com/MosesMendoza/4cdedf11fb92c137404a29b28d137a48 ] . *Update*This is the result of laying down a hiera 5 yaml file in puppet instead of the previous default hiera yaml file provided by the hiera project.This was done in [ https://github.com/puppetlabs/puppet/commit/7178bf1850c1addc40b5cc31a29aa4add09f34a9 ] . The puppet install.rb runs after the hiera install.rb during the puppet agent build process, so the hiera.yaml from hiera is overwritten by the hiera.yaml from puppet.The test does not modify the default hiera yaml file. The previous default file would create a lookup hierarchy, so all the test did was add a data file with entries that would resolve via that hierarchy.The new default does not specify the same hierarchy, so lookup now fails where it previously succeeded.This is problematic because the original hiera.yaml file was never modified - which means package managers won't back it up given a new one (the hiera 5 yaml) on upgrade. If users were relying on the previous behavior their lookups will fail.
Jira (FACT-1842) The ability to blocklist individual facts
Title: Message Title Nicky Kernohan created an issue Facter / FACT-1842 The ability to blocklist individual facts Issue Type: Improvement Affects Versions: FACT 3.11.0 Assignee: Unassigned Created: 2018/03/28 2:33 AM Priority: Normal Reporter: Nicky Kernohan Facter Version: all (tested in 3.11.0) Puppet Server Version: NA OS Name/Version: NA At current, we offer the ability to blocklist facts based on their grouping https://puppet.com/docs/facter/3.9/configuring_facter.html#facts Desired Behavior: **The ability to block individual facts from being collected, I understand we have the PuppetDB blacklist but this is for stopping individual facts from being executed rather than not being stored in PuppetDB For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment
Jira (FACT-1842) The ability to blocklist individual facts
Title: Message Title Nicky Kernohan updated an issue Facter / FACT-1842 The ability to blocklist individual facts Change By: Nicky Kernohan Zendesk Ticket IDs: https://puppetlabs.zendesk.com/agent/tickets/29561 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Nicky Kernohan Zendesk Ticket IDs: https://puppetlabs.zendesk.com/agent/tickets/29674 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-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Nicky Kernohan Method Found: Customer Feedback 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-8396) Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called Change By: Nicky Kernohan Priority: Normal Major 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-3647) Puppet stores files forever in state.yaml
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-3647 Puppet stores files forever in state.yaml Change By: Nicky Kernohan Priority: Normal Major 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-3647) Puppet stores files forever in state.yaml
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-3647 Puppet stores files forever in state.yaml Change By: Nicky Kernohan Method Found: Customer Feedback 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-8396) Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called Change By: Nicky Kernohan Summary: Puppet Resource Service fails on Debain/Ubuntu when non system d systemd service is called 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-8396) Puppet Resource Service fails on Debain/Ubuntu when non system d service is called
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debain/Ubuntu when non system d service is called Change By: Nicky Kernohan Summary: Puppet Resource Service fails on Debail Debain/Ubuntu when non system d service is called 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-8396) Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called Change By: Nicky Kernohan Attachment: puppetresourcedebug.txt 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-8396) Puppet Resource Service fails on Debail when non system d service is called
Title: Message Title Nicky Kernohan created an issue Puppet / PUP-8396 Puppet Resource Service fails on Debail when non system d service is called Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Henrik Lindberg Components: Functions Created: 2018/01/25 6:07 AM Environment: Puppet 5.3.3 (PE 2017.2.3) and Ubuntu 16.04 Priority: Normal Reporter: Nicky Kernohan Puppet Version: 5.3.3 Puppet Server Version: 5.3.3 OS Name/Version: Ubuntu 16.04 Describe your issue in as much detail as possible… In 16.04 when using puppet resource service, it bombs out if some of the services aren't using systemd, and trying to contact upstart, we should be handling this error better Describe steps to reproduce… It seems that a vanilla install of Ubuntu 16.x is OK, however when intalling additional Ubuntu packages such as the GUI, we se this error To
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8002 "Attempt to redefine entity" caused by using a resource collector Change By: Nicky Kernohan CS Priority: Major CS Severity: 3 - Serious CS Frequency: 1 - 1-5% of Customers 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-3648) PuppetDB having issues with escape characters
Title: Message Title Nicky Kernohan updated an issue PuppetDB / PDB-3648 PuppetDB having issues with escape characters Hi Rob PFA the files from the customer On 31 August 2017 at 16:03, Rob Browning (JIRA) < Change By: Nicky Kernohan Attachment: jms_gw_bindings_mq.epp Attachment: bindings 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-3648) PuppetDB having issues with escape characters
Title: Message Title Nicky Kernohan updated an issue PuppetDB / PDB-3648 PuppetDB having issues with escape characters Change By: Nicky Kernohan Priority: Normal Critical 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-3648) PuppetDB having issues with escape characters
Title: Message Title Nicky Kernohan created an issue PuppetDB / PDB-3648 PuppetDB having issues with escape characters Issue Type: Bug Affects Versions: PDB 4.4.1 Assignee: Rob Browning Components: PuppetDB Created: 2017/08/30 8:29 AM Environment: 2017.2.3 Priority: Normal Reporter: Nicky Kernohan Creating a template report on the node fails in PuppetDB The report runs fine on the node, but PuppetDB reports issues with the escape characters The code line in question
Jira (PUP-7830) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan commented on PUP-7830 Re: Adding a user with a numeric group name fails This was a cloned ticket for customer visibility Can you re-open it? Thanks On 10 August 2017 at 09:54, Henrik Lindberg (JIRA) < 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-7830) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan commented on PUP-7830 Re: Adding a user with a numeric group name fails This is an external ticket for customer visibility Please do not close Thanks 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-7830) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan created an issue Puppet / PUP-7830 Adding a user with a numeric group name fails Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Components: Platform Created: 2017/08/10 1:16 AM Environment: CentOS Linux release 7.2.1511 4.10.1 Seems to apply to all versions/ *nix OS Priority: Blocker Reporter: Nicky Kernohan Basic Info On the User resource, specifying a group with a group name as a number fails CentOS is a POSIX compliant, so can accept numbers for a group name fine Puppet Version: Tested in 4.10, Customer reporting in 4.5 OS Name/Version: CentOS Linux release 7.2.1511 Describe your issue in as much detail as possible... Creating a user with a group name as a number
Jira (PUP-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Forgot to mention, we also will hit the bug for numeric usernames, don't we ?Rgds.Franz 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: It's clear to me, that different OS using different methods of treating groups and members. But, puppet knows that its installed on linux, a POSIX compilant OS, and so it has to deal with groups using the right format. A simple "man group" explains it all. Since we rely on it, we cannot continue our work. (changed logics). Please provide a timeframe when there's a fix available. Didn't you test your software for OS compliance ?Rgds.Franz 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Hi Franz,We're currently working on this, we are seeing the same behaviour in our nodes, Looking further into the code, this is intentional, there is validation around the group and checks for whole numbers, if this is the case, then you see the error we are getting.The logic there is due to the fact that different OS process groups in different ways.Please see this documentation, https://docs.puppet.com/puppet/4.5/types/group.html#group-attribute-name```The group name. While naming limitations vary by operating system, it is advisable to restrict names to the lowest common denominator, which is a maximum of 8 characters beginning with a letter.Note that Puppet considers group names to be case-sensitive, regardless of the platform’s own rules; be sure to always use the same case when referring to a given group.```For now, this is an uneasy situation for you, and I can only apologise for this, at the time of speaking, there is no way to work around this due to the inherent logic in the code, I recommend you use a group starting with a letter.I will of course raise this use case with our engineering for you, this will then be triaged by our engineering team and worked on accordingly, in terms of timescales, this depends on their workload etc. For Users, from our testing it looks OK to use numericsThanks for your understanding FranzBest regards,Nicky This comment was made by Nicholas Kernohan on Fri Aug 04 03:32:32 PDT 2017 from Zendesk Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Hi FranzThanks for your replyAs I previously mentioned, the engineering team have to triage this first, and therefore I cannot currently commit to any timeframes, I will of course inform you once I have this.Apologies for this, I completely understand your frustration here, and will do my upmost to ensure we get this to a close. Best regards,Nicky This comment was made by Nicholas Kernohan on Fri Aug 04 03:57:48 PDT 2017 from Zendesk 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Hi FranzI have created a JIRA issue for youIt can be found athttps://tickets.puppetlabs.com/browse/PUP-7817You should have access to this, let me know if you do notBest regards,Nicky This comment was made by Nicholas Kernohan on Fri Aug 04 04:20:02 PDT 2017 from Zendesk 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Pinged the internal HipChat room using the @help alias using the maintenance page on Confulence This comment was made by Nicholas Kernohan on Wed Aug 09 06:09:46 PDT 2017 from Zendesk 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Hi Nicky,positive.Can access the ticket.Rgds.Franz 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Hi Franz,I understand your frustration, but for me to be able to help find a resolution I need the requested information to debug and find the root cause. Could you also give me the exact error you're receivingThanks in advance!Nicky This comment was made by Nicholas Kernohan on Fri Aug 04 02:43:53 PDT 2017 from Zendesk 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: When changing some users secondary group, (group name 123), create_resources complains about the supplied name which is numerically.Why ? Group 123 is a posix compilant name and we clearly have a bug here !!! 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Hi Franz,Thanks for contacting customer supportCan you please provide a little more information, can you provide the code that is failing the group change please?Thanks in advanceNicky This comment was made by Nicholas Kernohan on Fri Aug 04 02:12:15 PDT 2017 from Zendesk 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: If a add a character before 123, i, of cource get an error from usermod. So, it's clearly a bug. But a huge one. Cannot believe nobody is using numeric group names and didn't stumble upon it. Rgds.Franz 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: We use hiera and cannot believe, that this cannot be possible.It's posix compilant !We use create_resources and hiera. That's all.Rgds.Franz 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-7817) Adding a user with a numeric group name fails
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Nicky Kernohan Comment: Hi FranzThanks for Providing thatCould you also give me the exact error you're receivingThanksNicky This comment was made by Nicholas Kernohan on Fri Aug 04 02:39:51 PDT 2017 from Zendesk 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-7817) Adding a user with a numeric group name fails
Title: Message Title
Nicky Kernohan updated an issue
Puppet / PUP-7817
Adding a user with a numeric group name fails
Change By:
Nicky Kernohan
_Basic Info_On the User resource, specifying a group with a group name as a number failsCentOS is a POSIX compliant, so can accept numbers for a group name fine*Puppet Version:*Tested in 4.10, Customer reporting in 4.5 *OS Name/Version:*CentOS Linux release 7.2.1511_Describe your issue in as much detail as possible..._Creating a user with a group name as a number {code:java}user {'nicky':groups => '12345678',ensure => 'present',}{code}Applying this gets the following behaviour Error: Parameter groups failed on User[ 2334 nicky ]: Group names must be provided, not GID numbers. at /home/centos/user.pp:3The code checks if the group is a number and throws the above error, which is valid for GIDsBut not for group namesDocumentation also doesn't explicitly explain that group names should start with a letter, just explains it as best practice (which of course it is)https://docs.puppet.com/puppet/4.5/types/group.html#group-attribute-name*Desired Behavior:*Accept a numeric group name*Actual Behavior:*Fails on parsing the codePlease take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.Error: Parameter groups failed on User[ 2334 nicky ]: Group names must be provided, not GID numbers. at /home/centos/user.pp:3
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
Jira (PUP-7817) Adding a user with a numeric group name fails
Title: Message Title
Nicky Kernohan updated an issue
Puppet / PUP-7817
Adding a user with a numeric group name fails
Change By:
Nicky Kernohan
Summary:
Accounts : {brief summary of issue} Adding a user with a numeric group name fails
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-7817) Accounts : {brief summary of issue}
Title: Message Title
Nicky Kernohan created an issue
Puppet / PUP-7817
Accounts : {brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 4.10.1
Assignee:
Henrik Lindberg
Components:
Functions
Created:
2017/08/04 4:17 AM
Environment:
CentOS Linux release 7.2.1511 4.10.1
Seems to apply to all versions/ *nix OS
Priority:
Blocker
Reporter:
Nicky Kernohan
Basic Info
On the User resource, specifying a group with a group name as a number fails
CentOS is a POSIX compliant, so can accept numbers for a group name fine
Puppet Version:
Tested in 4.10, Customer reporting in 4.5 OS Name/Version: CentOS Linux release 7.2.1511 Describe your issue in as much detail as possible...
Creating a user with a group name as a number
