Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Charlie Sharpsteen updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Charlie Sharpsteen 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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6966 Tidy and File cannot remove fifo or socket files Change By: John Duarte Status: Ready for CI Test Assignee: Maggie Dreyer qa 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-5047) POSIX Exec throws error when group has no name
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-5047 POSIX Exec throws error when group has no name Change By: John Duarte Status: Ready for CI Test Assignee: Branan Riley qa 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 (FACT-1675) virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm
Title: Message Title kerminator assigned an issue to qa Facter / FACT-1675 virtual and is_virtual facts are wrong for OpenBSD VMs running within OpenBSD hypervisor vmm Change By: kerminator Status: Ready for CI Test Assignee: qa 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-3638) Work with docs to add new foss platform
Title: Message Title Melissa Stone moved an issue PuppetDB / PDB-3638 Work with docs to add new foss platform Change By: Melissa Stone Key: RE PDB - 7422 3638 Project: Release Engineering PuppetDB 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-3636) Update testing pipelines for foss sles targets
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-3636 Update testing pipelines for foss sles targets Change By: Melissa Stone Sub-team: Services Team: Release Engineering 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-3636) Update testing pipelines for foss sles targets
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-3636 Update testing pipelines for foss sles targets Change By: Melissa Stone Story Points: 3 2 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-3637) Build and Test PDB for sles 12
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-3637 Build and Test PDB for sles 12 Change By: Melissa Stone Story Points: 3 2 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-3637) Build and Test PDB for sles 12
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-3637 Build and Test PDB for sles 12 Change By: Melissa Stone Sub-team: Services Team: Release Engineering 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-3637) Build and Test PDB for sles 12
Title: Message Title Melissa Stone commented on PDB-3637 Re: Build and Test PDB for sles 12 Also, I believe only Sles 12 is required at this point. Sles 11 has an insufficient java version. 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-3637) Build and Test PDB for sles 12
Title: Message Title Melissa Stone commented on PDB-3637 Re: Build and Test PDB for sles 12 Russell Mull Rob Browning Any interest in taking this on? There should be no work other than modifying your scripts to make sure sles is added to the build and test pipelines. It would be nice to have pdb/puppetserver build/test targets more in line 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-3637) Build and Test PDB for sles 12
Title: Message Title Melissa Stone moved an issue PuppetDB / PDB-3637 Build and Test PDB for sles 12 Change By: Melissa Stone Key: RE PDB - 7946 3637 Project: Release Engineering PuppetDB 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-3636) Update testing pipelines for foss sles targets
Title: Message Title Melissa Stone moved an issue PuppetDB / PDB-3636 Update testing pipelines for foss sles targets Change By: Melissa Stone Key: RE PDB - 7421 3636 Project: Release Engineering PuppetDB 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 (FACT-1651) facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7
Title: Message Title Erik Dasher assigned an issue to Eric Delaney Facter / FACT-1651 facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7 Change By: Erik Dasher Resolution: Fixed Assignee: qa Eric Delaney Status: Ready for Test Resolved 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 (FACT-1651) facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7
Title: Message Title Erik Dasher commented on FACT-1651 Re: facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7 Resolving; I don't think this needs additional testing as the modification was a confine: in our tests. 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 (FACT-1651) facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7
Title: Message Title kerminator assigned an issue to qa Facter / FACT-1651 facter tests failures on power 8 on Ubuntu 16.04 and Rhel 7 Change By: kerminator Status: Ready for CI Test Assignee: Scott Garman qa 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Charlie Sharpsteen commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf There's one use case that we don't have a great workaround for: ensuring puppet logs go to the same source regardless of how the command is invoked. If you want Puppet daemon logs to go to a specific file, that's easy enough to configure by adding - logdest to /etc/sysconfig or a similar location. However, if you also want all invocations of puppet agent -t to log to the same file, then you're stuck in a bit of a bind. You could tell everyone to make sure they pass -logdest when running puppet, but that's going to have a high failure rate. You could write a wrapper for the Puppet command that ensures the flag is added, but that's a bit of site-specific work and carries the risk of breaking the system in ways that are hard to debug. Being able to set the log destinations in the central Puppet configuration file would be a really nice solution to this problem. 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-7818) AIX provider prefetch will fail if any package does not have a source
Title: Message Title
Branan Riley created an issue
Puppet / PUP-7818
AIX provider prefetch will fail if any package does not have a source
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/08/04 11:51 AM
Priority:
Normal
Reporter:
Branan Riley
Prefetching in AIX assumes that all packages have a valid source attribute. This is not always the case, as ensure => absent does not require such a source. Thus the following manifest will cause prefetch to fail:
package { 'sudo.rte':
ensure => latest,
source => "/mnt/my-packages"
}
Jira (PUP-7818) AIX provider prefetch will fail if any package does not have a source
Title: Message Title Branan Riley updated an issue Puppet / PUP-7818 AIX provider prefetch will fail if any package does not have a source Change By: Branan Riley Sprint: Platform Core OS Grooming 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Change By: Karen Van der Veer Sprint: AP 2017-01-11, AP 2017-03-08, Agent 2017-03-22, Platform Core 2017-09-19 Grooming 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-6959) Puppet::FileSystem.open / exclusive_open / replace_file should use Windows file system support for setting `mode`
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6959 Puppet::FileSystem.open / exclusive_open / replace_file should use Windows file system support for setting `mode` Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19 Grooming 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-6585) Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6585 Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path) Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19 Grooming 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-7315) rspec: add test for hiera interpolated options
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7315 rspec: add test for hiera interpolated options Change By: Karen Van der Veer Sprint: Agent 2017-05-03, Platform Core 2017-09-19 Grooming 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19 Grooming 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-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Karen Van der Veer Sprint: Client 2016-09-07, Platform Core 2017-09-19 Grooming 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-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6035 Puppet Throws Exception when Running Under Unicode Windows User Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19 Grooming 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-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6040 "puppet facts" outputs indirector object instead of simple fact list Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19 Grooming 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-7678) Add functions 'all' and 'any'
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7678 Add functions 'all' and 'any' Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19, Agent 2017-06-28 , Platform Core Grooming 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-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19, Agent 2017-06-14, Agent 2017-06-28 , Platform Core Grooming 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-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19 Grooming 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-2354) agent is confused about cert state
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-2354 agent is confused about cert state Change By: Karen Van der Veer Sprint: Client 2016-05-18, Platform Core 2017-09-19 Grooming 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-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7102 Insufficient logging when encountering 'permission denied' on environmentpath Change By: Karen Van der Veer Sprint: PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08, PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19, Platform Core 2017-09-19, Agent 2017-06-28, Agent 2017-07-12 , Platform Core Grooming 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-7760) Array to String formatter adds a trailing space to a separator
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7760 Array to String formatter adds a trailing space to a separator Change By: Karen Van der Veer Sprint: Platform Core 2017-09-19, Agent 2017-07-12 , Platform Core Grooming 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-7678) Add functions 'all' and 'any'
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7678 Add functions 'all' and 'any' Change By: Karen Van der Veer Sprint: Platform Core 2017-09- 05 19 , Agent 2017-06-28 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-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Karen Van der Veer Sprint: Platform Core 2017-09- 05 19 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-2354) agent is confused about cert state
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-2354 agent is confused about cert state Change By: Karen Van der Veer Sprint: Client 2016-05-18, Platform Core 2017-09- 05 19 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-3551) Sanitize non-UTF-8 data in run reports
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-3551 Sanitize non-UTF-8 data in run reports Change By: Karen Van der Veer Sprint: Platform Core 2017-09- 05 19 , Agent 2017-06-14, Agent 2017-06-28 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-7102) Insufficient logging when encountering 'permission denied' on environmentpath
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7102 Insufficient logging when encountering 'permission denied' on environmentpath Change By: Karen Van der Veer Sprint: PDE 2017-02-08, PDE 2017-02-22, PDE 2017-03-08, PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19, Platform Core 2017-09- 05 19 , Agent 2017-06-28, Agent 2017-07-12 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-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6040 "puppet facts" outputs indirector object instead of simple fact list Change By: Karen Van der Veer Sprint: Platform Core 2017-09- 05 19 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-7760) Array to String formatter adds a trailing space to a separator
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7760 Array to String formatter adds a trailing space to a separator Change By: Karen Van der Veer Sprint: Platform Core 2017-09- 05 19 , Agent 2017-07-12 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-7618) PSON -> JSON Testing
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-7618 PSON -> JSON Testing Change By: Karen Van der Veer Sprint: Agent 2017-06-28, Platform Core 2017-08-22 Grooming 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-6697) Allow full downloaded CA bundle to be stored to agent's localcacert file
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6697 Allow full downloaded CA bundle to be stored to agent's localcacert file Change By: Karen Van der Veer Sprint: Platform Core 2017-08-22 Grooming 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 (FACT-1726) Facter 2.y operatingsystemrelease fact doesn't return a useful value for Windows 2016
Title: Message Title Josh Cooper updated an issue Facter / FACT-1726 Facter 2.y operatingsystemrelease fact doesn't return a useful value for Windows 2016 Change By: Josh Cooper Team: Platform OS 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 (FACT-1726) Facter 2.y operatingsystemrelease fact doesn't return a useful value for Windows 2016
Title: Message Title Josh Cooper commented on FACT-1726 Re: Facter 2.y operatingsystemrelease fact doesn't return a useful value for Windows 2016 This is a result of FACT-341 being implemented before Windows 10 was released. 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Matthew Patton commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' I'm not blocking anything. I'm simply pointing out that 'reload' has all kinds of problems. A feature shouldn't be "experts only" or else be prepared to get burned in non-obvious ways. Maybe some consider it semantics but Puppet has no way to know the daemon did anything in response to the reload. Maybe the process was smart enough to ignore syntax errors, maybe instead it exited on said errors and now isn't running at all. Puppet isn't necessarily going to issue a Start(). So much for that 'reload', eh? Maybe it closed some file handles and not others, maybe it has processes/sockets open that are running the old config until the client disconnects or the LB let's go (if ever). That's a whole lot of Maybe's and I wasn't even trying. State machines are not about Maybes, they are about (plausible) Guarantees. Restart on the other hand ensures as best it can that the previous process has been terminated, and that subsequently all configuration files were re-read on startup; it has reasonable assurance and expectation that the intended outcome has been reached. You're able to implement your own workaround, so maybe do a wrapper type and publish on Forge? That other tools may have capitulated to the demands of people who insist on being cavalier about their state machine is not a worthwhile argument. Correctness trumps convenience and expediency. Every time. 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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title Maggie Dreyer commented on PUP-6966 Re: Tidy and File cannot remove fifo or socket files I have merged https://github.com/puppetlabs/puppet/pull/6103 to rectify this UX change. It now warns when backup can't be performed, but doesn't fail, and moves on to trying to remove the file anyway. 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-6966) Tidy and File cannot remove fifo or socket files
Title: Message Title John Duarte commented on PUP-6966 Re: Tidy and File cannot remove fifo or socket files This change modifies the UX for removing directories. Previously, attempting to remove a directory without using the --force flag notified the user that the flag was necessary to perform the remove operation. Not removing directory; use 'force' to override With this change, the user is no longer notified that the --force flag is required to complete the desired operation. Could not back up file of type directory; will not remove This causes the acceptance test for this UX interaction to fail. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Colin Alston commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' I don't understand why you're trying to block this feature simply because it "could be dangerous", absolutely everything that every configuration management tool does could be dangerous or work unexpectedly in inexperienced hands, but that's no reason to hamstring the rest of us into ugly workarounds for something which is a simple syntactic feature - especially when almost every other competing tool offers it. 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-5642) puppet module generate's manifests/init.pp is unusable
Title: Message Title David Schmitt updated an issue Puppet / PUP-5642 puppet module generate's manifests/init.pp is unusable You might want to try out the Tech Preview of the Puppet Developer Kit, which will replace puppet module generate. See https://groups.google.com/d/msg/puppet-users/_G6issIdmVY/5oUfKhwkAQAJ for the last announcement. Change By: David Schmitt Team: Puppet Developer Experience 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-7678) Add functions 'all' and 'any'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7678 Add functions 'all' and 'any' Change By: Henrik Lindberg Sprint: Platform Core 2017-09-05, Agent 2017-06-28 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-7816) Package resource' ensure attribute to use Semantic Versioning
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7816 Package resource' ensure attribute to use Semantic Versioning Change By: Henrik Lindberg Team: Platform OS 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-7816) Package resource' ensure attribute to use Semantic Versioning
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7816 Package resource' ensure attribute to use Semantic Versioning Change By: Henrik Lindberg Component/s: Types and Providers 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 Henrik Lindberg updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Henrik Lindberg Component/s: Functions Component/s: Types and Providers 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 Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 Henrik Lindberg updated an issue Puppet / PUP-7817 Adding a user with a numeric group name fails Change By: Henrik Lindberg Team: Platform OS 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Matthew Patton commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' At the risk of jacking the thread, what happens to your cluster when there is anywhere from minutes, to maybe even hours (whenever the next successful puppet run completes) where the members don't all have the same configuration? Does it split-brain? Does it improperly migrate the service or trigger competing master elections? Does it corrupt or return inconsistent data? Is it even able to establish quorum or respond correctly to a legitimate member state change? It seems you're under the impression that 'service reload' always succeeds. Sure, it might for 99% of attempts, but it's the 1% that matters. I suspect the reason this has been open for 4 years is because while it may be convenient to some, much self-inflicted.harm will result by unthinking, careless use. In the scheme of things a restart doesn't take all that much more time than a reload, and it has the benefit of being an observable state transition. 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails Hi Franz I have created a JIRA issue for you It can be found at https://tickets.puppetlabs.com/browse/PUP-7817 You should have access to this, let me know if you do not Best 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails Hi Franz Thanks for Providing that Could you also give me the exact error you're receiving Thanks Nicky 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
zendesk.jira commented on PUP-7817
Re: Adding a user with a numeric group name fails
Failing User JSON Object: { "user1" : { "purge_ssh_keys" : "true", "uid" : 10100, "password" : "!", "membership" : "inclusive", "password_min_age" : "0", "shell" : "/bin/false", "groups" : [ "123" ], "password_max_age" : "9", "gid" : 10101, "comment" : "Test 101 User", "home" : "/nonexistent", "ensure" : "present" }
}
Group Object: { "123" : { "gid" : 10105 }
}
Please send us a fix ASAP as the production host cannot be manages right now !
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
zendesk.jira commented on PUP-7817
Re: Adding a user with a numeric group name fails
Error: Failed to apply catalog: Parameter groups failed on User[user1]: Group names must be provided, not GID numbers. at /etc/puppetlabs/code/environments/production/modules/samba_knoxdata/manifests/init.pp:144
Line 144: create_resources(user, $users)
Users variable: $users = hiera('api::users', {})
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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 numerics Thanks for your understanding Franz Best 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails Hi Franz Thanks for your reply As 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 receiving Thanks 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails 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 zendesk.jira commented on PUP-7817 Re: Adding a user with a numeric group name fails Hi Franz, Thanks for contacting customer support Can you please provide a little more information, can you provide the code that is failing the group change please? Thanks in advance Nicky 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
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
Jira (PDB-2589) puppetdb module should CREATE EXTENSION pg_trgm; on backend database.
Title: Message Title Alexander Fisher commented on PDB-2589 Re: puppetdb module should CREATE EXTENSION pg_trgm; on backend database. Looks like this is fixed? https://github.com/puppetlabs/puppetlabs-puppetdb/commit/51c1b217c21453b2adbaa8d36ef4de5f192bf65a 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-3501) PQL queries using fact names with dashes does not work
Title: Message Title
Chris Barker commented on PDB-3501
Re: PQL queries using fact names with dashes does not work
As part of partner integration work, this becomes a major problem since many people want to find the certname associated with an aws instance-id.
The easiest way to do this would be via `puppet query 'inventory[certname] { facts.ec2_metadata.instance-id = "i-0763590da3427251a" }
'` if that worked.
This becomes essential for node registration and de-registration processes since we will know from services like Amazon that an instance-id was terminated, but we can't be certain what that instances certname was unless we can query puppetdb for it.
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-3501) PQL queries using fact names with dashes does not work
Title: Message Title Chris Barker updated an issue PuppetDB / PDB-3501 PQL queries using fact names with dashes does not work Change By: Chris Barker Priority: Normal Major 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-1277) service does not implement custom start / stop commands on windows
Title: Message Title Mark commented on PUP-1277 Re: service does not implement custom start / stop commands on windows It seems it still uses the default 'net stop/start [service]' and doesn't take into account what you set with 'stop' or 'start'. One of my services doesn't actually stop with 'net stop [service]', it takes a little longer. Here's an example: When I do 'net stop gitlab-runner', it throws a message after a couple of seconds: "The gitlab-runner service could not be stopped". It then actually takes another couple of seconds for the service to actually stop, but meanwhile Puppet is trying to start it again already, which results in: "The service is starting or stopping. Please try again later.". It then takes until the next Puppet run to actually start the service again. However, when I use Powershell to stop the service, it actually waits until the service is entirely stopped, using 'Stop-Service gitlab-runner'. Looks like this in Puppet DSL: stop => 'c:\windows\system32\windowspowershell\v1.0\powershell.exe Stop-Service gitlab-runner', However that does nothing. The output of the Puppet run actually says it's using 'net stop' still. And that is correct, according to the code in '/lib/puppet/provider/service/windows.rb', it doesn't take start/stop parameters into account, it always uses 'net': net(:start, @resource[:name]) net(:stop, @resource[:name]) The 'restart' parameter isn't used at all either.
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Colin Alston commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' Inflammatory statements aside, Puppet is used in numerous production environments to coordinate cluster orchestration and other tasks which heavily rely on non-disruptive configuration changes. There is no need for that to be considered any less controlled than running Kubernetes to shift workloads. pgpool and pgbouncer are not at all one-size-fits-all solutions, in fact they're exceptionally bad solutions to a far simpler issue. However managing cluster failover is an important example of why you want reloads, consider performing maintenance on a warm/hot standby pair it might be useful not to bring an entire cluster down just to update the sync destination. 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-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Matthew Patton commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' It's just happy coincidence that pg_hba.conf changes and certain changes to Apache/Nginx and some others can be done in a theoretically non-disruptive manner. Say you reload Postgres and sure, while your current sessions can continue, all new sessions are failing because you screwed something up. Or even better, some other CI push invoked reload() on the LDAP server(s) and they didn't like it for whatever obscure reason. Now your PG users are unable to authenticate. I'll happy stipulate that INIT script quality is all over the map, but I'll wager a restart() results in a reliable service outcome whereas reload() is at best a coin flip. Puppet and it's ilk are about enforcing and achieving a deterministic state. End-user disruption doesn't enter the equation one bit. To that end nobody sane runs CI on production equipment in an uncontrolled manner, EVEN IF you happen to be running daemons that (most of the time) let you get away with it. Nodes are properly drained and rotated out, they are restarted, all pertinent aspects of their health is ascertained, and then and ONLY then, are they put back into the pool. With PG you're in luck; you can leverage pgpool and pgbouncer so there is no reason not to do the Right Thing(r). There are no shortcuts in operations as much as CI/DevOPS would like to pretend they can hand-wave it away. 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 (FACT-1726) Facter 2.y operatingsystemrelease fact doesn't return a useful value for Windows 2016
Title: Message Title Tim Sharpe created an issue Facter / FACT-1726 Facter 2.y operatingsystemrelease fact doesn't return a useful value for Windows 2016 Issue Type: Bug Affects Versions: FACT 2.4.6, FACT 2.5.0 Assignee: Unassigned Created: 2017/08/04 12:13 AM Priority: Normal Reporter: Tim Sharpe Facter 2.y returns a '10.0.' (`kernelrelease`) value for the `operatingsystemrelease` fact on Windows 2016 instead of the expected '2016' Add Comment
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Colin Alston commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' No, you're missing the point of 'reload' and continuous orchestration. Assume you have some configuration change which alters a PostgreSQL pg_hba.conf for example, you can apply those changes without restarting the service and terminating active connections which would disrupt other services. A reload mitigates that by re-configuring the service without a restart. HUP signals are used a numerous other services, another good example being something like HAproxy for edge routing in cloud infrastructures where again it would be quite annoying to have your entire infrastructure blip just to on-board a new service through Puppet. 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-7816) Package resource' ensure attribute to use Semantic Versioning
Title: Message Title Matthew Patton updated an issue Puppet / PUP-7816 Package resource' ensure attribute to use Semantic Versioning Change By: Matthew Patton Labels: package resources 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-7816) Package resource' ensure attribute to use Semantic Versioning
Title: Message Title Matthew Patton created an issue Puppet / PUP-7816 Package resource' ensure attribute to use Semantic Versioning Issue Type: New Feature Assignee: Unassigned Created: 2017/08/03 11:15 PM Priority: Normal Reporter: Matthew Patton I wanted to ensure that puppet-agent 1.9.0 was not allowed on my boxes and realized there was no way for me to do so without resorting to RPM version string. I don't want to pin it to 1.8.4 or 1.9.2, nor do I want to play roulette and specify 'latest' since broken builds show up from time to time. I should be able to specify the well-known nomenclature that Module metatdata.json uses. ensure => ">= 4.8.2 < 5.0.0" References https://docs.puppet.com/puppet/5.0/modules_metadata.html#version-specifiers-in-module-metadata http://semver.org/
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Matthew Patton commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' IMO 'reload' is missing the point of Puppet. If you allow Puppet to change the state of the machine, you are by definition doing so during an outage window and have notified upstream devices (cluster manager, load-balancer, etc.) that you are unhealthy, since service disruption is to be expected. QED a restart is proper if more heavy-handed than you might like. That some handful of software has fancy in-place abilities is immaterial. I suspect implementing 'reload' will cause far more headache for users who wonder why their new configuration is not (or only partly) deployed and then either blame Puppet or have to go delve into their particular software to figure out what changes are honored under what conditions. Why make life difficult? KISS - just restart it. 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.
