Jira (PUP-8948) Enable ability to edit the "Hello" message at console login
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-8948 Enable ability to edit the "Hello" message at console login Issue Type: New Feature Assignee: Unassigned Created: 2018/06/18 8:07 AM Priority: Normal Reporter: Daniel Mcilhagga Would it be possible to enable the ability to edit the "Hello" message that you are presented with at login? A customer would like to change this so instead a legal banner is displayed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8634) Chown of ssldir Causing Failures
Title: Message Title Daniel Mcilhagga assigned an issue to Geoff Nichols Puppet / PUP-8634 Chown of ssldir Causing Failures Change By: Daniel Mcilhagga Assignee: Daniel Mcilhagga Geoff Nichols 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-8634) Chown of ssldir Causing Failures
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-8634 Chown of ssldir Causing Failures Issue Type: New Feature Assignee: Unassigned Created: 2018/04/06 1:01 AM Priority: Normal Reporter: Daniel Mcilhagga Currently Puppet as part of the install does a chown of the ssldir to puppet:puppet. A customer is currently asking if it is possible to disable this functionality. Below is a description of the customer's use case. "We only have a user called 'puppet' on a handful of our unix clients (relatively speaking - it is a few hundred), and for all other hosts the $ssldir is owned by root:root. We know why the GID isn't resolving (missing LDAP data) but as the use of a 'puppet' account on clients doesn't appear to gain us anything but causes the occasional agent installation failure (impacting our build automation) I wanted to look at preventing the chown operation during agent install." Add Comment
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Daniel Mcilhagga assigned an issue to Unassigned PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Daniel Mcilhagga Assignee: Daniel Mcilhagga 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-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Daniel Mcilhagga updated an issue PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Daniel Mcilhagga In 2017.2 when a node was marked as expired or deactivated it but node-purge-ttl wasn't invoked, it will was still searchable by using:{code:java} curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { expired is not null or deactivated is not null }' | python -m json.tool {code}Since 2017.3.*, if the node-purge-ttl setting is set to 0s (or any value) it will not be respected and the data is purged from the DB instantly. Running the above query does not display any results and any queries searching for all nodes so not show the nodes in question. 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
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Daniel Mcilhagga created an issue PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Issue Type: Bug Assignee: Unassigned Created: 2018/03/21 6:38 AM Priority: Normal Reporter: Daniel Mcilhagga In 2017.2 when a node was marked as expired or deactivated it but node-purge-ttl wasn't invoked, it will still searchable by using: curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { expired is not null or deactivated is not null }' | python -m json.tool Since 2017.3.*, if the node-purge-ttl setting is set to 0s (or any value) it will not be respected and the data is purged from the DB instantly. Running the above query does not display any results and any queries searching for all nodes so not show the nodes in question. Add Comment
Jira (PUP-8211) Allow managehome to modify home directory for existing users
Title: Message Title Daniel Mcilhagga commented on PUP-8211 Re: Allow managehome to modify home directory for existing users Raised doc bug here: https://tickets.puppetlabs.com/browse/DOCUMENT-777 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-8211) User Resource Managehome not Working Properly
Title: Message Title Daniel Mcilhagga updated an issue Puppet / PUP-8211 User Resource Managehome not Working Properly Change By: Daniel Mcilhagga When a user already exists on the system the managehome attribute for the user resource does not create the homedir: ested Tested locally on same version and managehome =true/yes doesn't create the home dir.{code}user {'john' : ensure => present, managehome => yes, }user {'john' : ensure => present, managehome => true, }{code}The docs say that if ensure=present it should be created:"Whether to manage the home directory when managing the user. This will create the home directory when ensure => present"Puppet resource user says homedir is present{code}user { 'john': ensure => 'present', gid => 1002, home => '/home/john', password => '!!', password_max_age => 9, password_min_age => 0, shell=> '/bin/bash', uid => 1002,}[root@pe-201732-master home]# pwd/home[root@pe-201732-master home]# ls -altotal 4drwxr-xr-x. 3 rootroot 20 Mar 9 2016 .dr-xr-xr-x. 18 rootroot4096 Nov 15 16:23 ..drwx-- 3 vagrant vagrant 107 Nov 28 13:34 vagrant[root@pe-201732-master home]#{code}If puppet creates user from scratch it works but not for existing users 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
Jira (PUP-8211) User Resource Managehome not Working Properly
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-8211 User Resource Managehome not Working Properly Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2017/11/28 6:00 AM Priority: Normal Reporter: Daniel Mcilhagga When a user already exists on the system the managehome attribute for the user resource does not create the homedir: ested locally on same version and managehome =true/yes doesn't create the home dir. user {'john' : ensure => present, managehome => yes,
Jira (PUP-8208) Puppet Node Purge API Query
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-8208 Puppet Node Purge API Query Issue Type: New Feature Assignee: Unassigned Created: 2017/11/24 7:46 AM Priority: Normal Reporter: Daniel Mcilhagga Currently there are API calls for revoking and deleting certificates which together emulate the puppet cert clean command. Would it be possible to include an API call that would emulate the puppet node purge command. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8139) Spelling Error in Error Message
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-8139 Spelling Error in Error Message Issue Type: Bug Assignee: Unassigned Created: 2017/11/09 7:52 AM Priority: Normal Reporter: Daniel Mcilhagga I have a customer who noticed the following spelling mistake: "To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate." This is found in: https://github.com/puppetlabs/pe-puppet/blob/08c4fbbdc7f82b7a6a3e1f10485dd6b5508665d6/lib/puppet/ssl/host.rb Add Comment
Jira (PUP-8132) Package Resource Always Uses -i Flag and Errors out if Already Installed
Title: Message Title Daniel Mcilhagga assigned an issue to Daniel Mcilhagga Puppet / PUP-8132 Package Resource Always Uses -i Flag and Errors out if Already Installed Change By: Daniel Mcilhagga Assignee: Daniel Mcilhagga 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-7581) Special Character File Names Fail when Copying
Title: Message Title Daniel Mcilhagga assigned an issue to Unassigned Puppet / PUP-7581 Special Character File Names Fail when Copying Change By: Daniel Mcilhagga Assignee: Daniel Mcilhagga 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-8035) Failed Runs showing as Unchanged in Console due to Cached Catalog
Title: Message Title Daniel Mcilhagga assigned an issue to Unassigned Puppet / PUP-8035 Failed Runs showing as Unchanged in Console due to Cached Catalog Change By: Daniel Mcilhagga Assignee: Ryan Coleman 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-8035) Failed Runs showing as Unchanged in Console due to Cached Catalog
Title: Message Title Daniel Mcilhagga moved an issue Puppet / PUP-8035 Failed Runs showing as Unchanged in Console due to Cached Catalog Change By: Daniel Mcilhagga Key: ENTERPRISE PUP - 1099 8035 Project: Puppet Enterprise 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-7993) Tidy Resource 'Type' Bug
Title: Message Title Daniel Mcilhagga updated an issue Puppet / PUP-7993 Tidy Resource 'Type' Bug Change By: Daniel Mcilhagga Team: Platform Core 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-7993) Tidy Resource 'Type' Bug
Title: Message Title Daniel Mcilhagga updated an issue Puppet / PUP-7993 Tidy Resource 'Type' Bug Change By: Daniel Mcilhagga CS Priority: Needs Priority 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-7993) Tidy Resource 'Type' Bug
Title: Message Title Daniel Mcilhagga updated an issue Puppet / PUP-7993 Tidy Resource 'Type' Bug Change By: Daniel Mcilhagga Hi I have a customer who is facing a bug when using AIX. They have the following resource:On AIX: it requires type => "mtime", # and only mtime works tidy { '/opt/log': age => '2w', recurse => 9, matches => ['*.txt', '*.gz', 'error_log.20170*', 'access_log.20170*', '*.Z', '*.zip' ], type => "mtime", }and only 'mtime' appears to work. I have asked them to run the following commands:find /opt/log/ -ctime -14 -printfind /opt/log/ -atime -14 -printfind /opt/log/ -mtime -14 -printand they all produce results which match the resource criteria specified. If they use any type except mtime it doesn't pick up any files to tidy. The affected OS is AIX 7.1. https://docs.puppet.com/puppet/latest/types/tidy.html#tidy-attribute-type 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-7993) Tidy Resource 'Type' Bug
Title: Message Title Daniel Mcilhagga assigned an issue to Unassigned Puppet / PUP-7993 Tidy Resource 'Type' Bug Change By: Daniel Mcilhagga Assignee: Ryan Coleman 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-7993) Tidy Resource 'Type' Bug
Title: Message Title Daniel Mcilhagga moved an issue Puppet / PUP-7993 Tidy Resource 'Type' Bug Change By: Daniel Mcilhagga Key: ENTERPRISE PUP - 1096 7993 Project: Puppet Enterprise 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-7581) Special Character File Names Fail when Copying
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-7581 Special Character File Names Fail when Copying Issue Type: Bug Assignee: Unassigned Created: 2017/05/22 3:48 AM Priority: Normal Reporter: Daniel Mcilhagga I have a ticket from a user on PE 3.7. They have created a module that copies a list of files from one location to another. The file names are a lot of special characters in a string (i.e _!'`!!"1!#4!b@"p!(@!.g"s!'w!.g"p!(:!}@"0!#4!}@"y!':!a!"p!(}!@!u!'g!}@"u!'@!b!"l!()!cw!u!'0!a@"4!'`!cg!u!&@!cg"h!':!aw";!'`!cw"z!'%!w"l!%8!d@"0!(!!d@"0!&:!d!"y!'`!}@"t!!cg"p!(@!@"y). When running the module on 3.7 or 3.8 it spits back an error message saying: ' Error: /Stage[main]/Main/File[files]: Failed to generate additional resources using 'eval_generate': Parameter source failed on File[/etc/puppetlabs/puppet/environments/production/modules/test/files/_!'`!~!"1!#4!b@"p!(@!.g"s!'w!.g"p!(:!~!"z!#4!b@"h!'`!cw"0!()!bw!u!(:!e@"z!(@!~@"t!#4!^@"h!'`!cw"0!()!bw"]Unable to render embedded object: File ('`!c@"1) not found.'`!cw"0!%g!}@"u!'@!b!"l!()!@"h!'4!}@"n!'`Unable to render embedded object: File ( Could not understand source file:/etc/puppetlabs/puppet/environments/production/modules/test/manifests/files/_) not found.'`!!"1!#4!b@"p!(@!.g"s!'w!.g"p!(:!!"z!#4!b@"h!'`!cw"0!()!bw!u!(:!e@"z!(@!~@"t!#4!@"h!'`!cw"0!()!bw"]!'`!c@"1!'`!cw"0!%g!}@"u!'@!b!"l!()!^@"h!'4!}@"n!'`!cg==: bad URI(is not URI?): file:/etc/puppetlabs/puppet/environments/production/modules/test/manifests/files/_!'%60!~!%221!%234!b@%22p!(@!.g%22s!'w!.g%22p!(:!~!%22z!%234!b@%22h!'%60!cw%220!()!bw!u!(:!e@%22z!(@!~@%22t!%234!%5E@%22h!'%60!cw%220!()!bw%22]!'%60!c@%221!'%60!cw%220!%25g!%7D@%22u!'@!b!%22l!()!%5E@%22h!'4!%7D@%22n!'%60!cg==' ' When the same test is ran on PE 2017.2.1 the following more generic error message is displayed: