Jira (PUP-6635) An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf
Title: Message Title
Stefan Pijnappels updated an issue
Puppet / PUP-6635
An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf
Change By:
Stefan Pijnappels
In a case where limits (such as no of file handles allowed etc.) have been set for a user on a system using either /etc/security/limits.conf or a separate file under /etc/security/limits.d/, when an exec resource is run as this user, these limits are ignored and defaults are used. This can be easily reproduced by creating a user (oracle in my tests and in customer ticket) and setting {{nofile}} hard and soft limits for this user in either /etc/security/limits.conf or by creating a file under /etc/security/limits.d/ with the appropriate prefix and username.{{[root@pe-201621-agent vagrant]# cat /etc/security/limits.conf | grep oracleoracle softnofile 4096oracle hardnofile 63536[root@pe-201621-agent vagrant]#}}Running a simple script to print the limits to the console as user oracle will print the values as defined:{{[oracle@pe-201621-agent vagrant]$ cat /tmp/test_ulimit.shecho "Hard:"/bin/bash -c 'ulimit -Hn'echo "Soft:"/bin/bash -c 'ulimit -Sn'[oracle@pe-201621-agent vagrant]$ /tmp/test_ulimit.shHard:63536Soft:4096[oracle@pe-201621-agent vagrant]$}}However, when this same script is called using puppet code, running puppet as root, different values are noted:{{[root@pe-201621-agent vagrant]# cat test_ulimit.ppinclude test_ulimitclass test_ulimit { exec { "test_ulimit":provider => "shell",user => "oracle",path => "/tmp",command => "test_ulimit.sh",logoutput => "true" }}[root@pe-201621-agent vagrant]# puppet apply test_ulimit.ppNotice: Compiled catalog for pe-201621-agent.puppetdebug.vlan in environment production in 0.07 secondsNotice: /Stage[main]/Test_ulimit/Exec[test_ulimit]/returns: Hard:Notice: /Stage[main]/Test_ulimit/Exec[test_ulimit]/returns: 4096Notice: /Stage[main]/Test_ulimit/Exec[test_ulimit]/returns: Soft:Notice: /Stage[main]/Test_ulimit/Exec[test_ulimit]/returns: 1024Notice: /Stage[main]/Test_ulimit/Exec[test_ulimit]/returns: executed successfullyNotice: Applied catalog in 0.06 seconds[root@pe-201621-agent vagrant]#}}I suspect that the script called by the exec resource is actually inheriting the limit values from the puppet process, while it does actually run as the user specified in the exec resource in puppet code.The issue is that the customer is using this exec to kick off processes which interact with an oracle database as the oracle user, and needs the increased number of open file descriptors.Is this a natural by-product of using an exec resource, or is it a bug? Is there a way to resolve this either in the puppet code written by the customer in the exec resource or in the product itself? The customer ticket is https://puppetlabs.zendesk.com/agent/tickets/20532 If I have linked to the wrong scrum team, please re-assign.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: Thomas Hallgren Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2940) puppet query does not render UTF-8 characters correctly
Title: Message Title Wyatt Alt commented on PDB-2940 Re: puppet query does not render UTF-8 characters correctly Andrew Roetker I'm thinking this is a bug in https://github.com/ajroetker/beautician. The raw API response doesn't have the issue, so it's definitely the CLI tool that's the problem. Still trying to get my head around the rust code. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2992) add jessie and wheezy to client-tools platforms
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2992 add jessie and wheezy to client-tools platforms Issue Type: Bug Assignee: Unassigned Created: 2016/08/18 5:09 PM Priority: Normal Reporter: Wyatt Alt https://github.com/puppetlabs/puppet-client-tools-vanagon/pull/16 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1460) Load facter.conf when facter. is used as a library
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1460 Load facter.conf when facter. is used as a library Change By: Maggie Dreyer Release Notes Summary: The Facter config file will now be loaded from its default location (/etc/puppetlabs/facter/facter.conf on Unix, C:\ProgramData\PuppetLabs\facter/facter.conf on Windows) when Facter is required from Ruby. Two settings will be respected: external-dir and custom-dir, which add paths to search for custom and external facts to those already specified by Puppet. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2941) PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1
Title: Message Title Priscilla Piedra commented on PDB-2941 Re: PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1 Close it... I appreciate all your help! El 18 ago. 2016 4:52 PM, "Wyatt Alt (JIRA)" < Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2941) PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1
Title: Message Title Wyatt Alt commented on PDB-2941 Re: PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1 Priscilla Piedra are you still having issues with this or can I close? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6621) Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it
Title: Message Title Branan Riley updated an issue Puppet / PUP-6621 Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it Change By: Branan Riley Release Notes Summary: Corrective Change would incorrectly fail a catalog application when a type or property was incompatible with it. It now logs this information at info level. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6621) Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it
Title: Message Title Branan Riley updated an issue Puppet / PUP-6621 Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it Change By: Branan Riley Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title Branan Riley updated an issue Puppet / PUP-6628 Corrective change should use property values directly, bypassing any munging Change By: Branan Riley Release Notes Summary: Corrective change calculation is now more robust when properties have complex munge and validate methods Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title Branan Riley updated an issue Puppet / PUP-6628 Corrective change should use property values directly, bypassing any munging Change By: Branan Riley Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Branan Riley updated an issue Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: Branan Riley Release Notes Summary: Overly aggressive autorelationships between mount and file types have been scaled back Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Branan Riley updated an issue Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: Branan Riley Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Branan Riley updated an issue Puppet / PUP-6629 Corrective Change YAML file causes errors when type parameter is a complex type Change By: Branan Riley Sprint: Client 2016-08-24 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6632) Regression when comparing user groups
Title: Message Title Branan Riley commented on PUP-6632 Re: Regression when comparing user groups This looks like a duplicate of an issue we discovered internally, and filed as PUP-6628. I'm going to confirm that my fix for that works correctly with your manifest Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Henrik Lindberg commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Nikolai R Kristiansen How did you end up attempting to use a 4.6.0 puppet's create_resources function on a Puppet 3.x agent? Function's only run master side, (or during an apply). Ping Kylo Ginsberg - am I missing something here in terms of a bona-fide way to upgrade? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Branan Riley assigned an issue to Branan Riley Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6638 create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2991) performance testing of stockpile
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2991 performance testing of stockpile Issue Type: Task Assignee: Unassigned Created: 2016/08/18 1:49 PM Priority: Normal Reporter: Wyatt Alt Test stockpile for regressions against AMQ and to establish a sense of our baseline queue performance. Results are being compiled here: https://docs.google.com/document/d/1zNS1ul0WrActpUk3t9M6Zl5i2GyBZwumdKb01hf_PnA/edit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6634) environment.conf should use standard syntax for POSIX and Windows
Title: Message Title
Henrik Lindberg commented on PUP-6634
Re: environment.conf should use standard syntax for POSIX and Windows
We could support only one of them (':' would be bad for Windows users, and ';' for Posix users) - we would need to deprecate "the other", and the annoy people with having to change.
We could support both - which could potentially be somewhat confusing. No deprecation needed, it is simply a new feature per the respective platform. There is a small problem that paths can then not contain the "other delimiter" as part of a path (that is probably a very small problem).
My vote goes to supporting both delimiters.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Paul Anderson commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed After discussing this issue with a user experiencing this issue, they suggest that in their opinion, failed is failed and doesn't need granular data in the console. (The user is concerned about a cluttered console interface). That said, if anyone on the UX team (or engineering) is interested in discussing the potential console remedy with this user, let me know. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Nikolai R Kristiansen created an issue Puppet / PUP-6638 create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Issue Type: Bug Assignee: Unassigned Created: 2016/08/18 1:39 PM Priority: Normal Reporter: Nikolai R Kristiansen When trying to upgrade from the default puppet version on Ubuntu 16.04 (http://packages.ubuntu.com/xenial/puppet 3.8.x) to the latest PC1 puppet-agent package using the puppetlabs-puppet_agent module we get the following error: Evaluation Error: Error while evaluating a Function Call, uninitialized constant Puppet::Pops::PuppetStack at ... The culprint was the usage of the Puppet::Pops::PuppetStack.stacktrace (https://github.com/puppetlabs/puppet/commit/2211c646921f85a31611f018cd8bfaab76692c98) in create_resource (https://github.com/puppetlabs/puppet/commit/01db61e24178a3baebbeaa1c58250fcbf447d8bc) which is called in the initialization of puppetlabs-apt in turn used by the puppetlabs-puppet_agent. This looks like a regression. Is it possible to only run the stacktrace generating code on 4.x agents?
Jira (PUP-6502) puppet calls dscl pathologically often
Title: Message Title John Duarte commented on PUP-6502 Re: puppet calls dscl pathologically often Submitted PR-5217 to address regression. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title John Duarte commented on FACT-1488 Re: git install on Win 2003 fails to clone puppet-win32-ruby repo Not sure where to go with this one. I don't see that github offers the ability to repack a repo. I presume git://github.delivery.puppetlabs.net/puppetlabs-puppet-win32-ruby.git is just a mirror of https://githhub.com/puppetlabs/puppet-win32-ruby.git Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6637) New attribute :create_mountpoint for Mount type
Title: Message Title Matt Schuchard commented on PUP-6637 Re: New attribute :create_mountpoint for Mount type I will start on this after PUP-6397 is merged into stable and then stable is merged into master so I do not cause merge headaches. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6637) New attribute :create_mountpoint for Mount type
Title: Message Title Matt Schuchard updated an issue Puppet / PUP-6637 New attribute :create_mountpoint for Mount type Change By: Matt Schuchard The create_mountpoint attribute for the Mount type will create the mountpoint directory with limited permissions if it is missing and the attribute is set to true. Default value for attribute is false.Since this resolves the File[mountpoint directory] --> Mount[mountpoint directory] --> File[directory permissions] circular dependency that formerly was worked around with an exec for File[mountpoint directory], we can now also implement an autobefore of Mount[mountpoint directory] --> File[directory permissions]. I encourage discussion over the worhtwhileness worthwhileness (probably not a word) of that proposal. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Matt Schuchard commented on PUP-6397 Re: File autorequire in Mount causes dependency loops Followup PUP-6637. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6637) New attribute :create_mountpoint for Mount type
Title: Message Title Matt Schuchard created an issue Puppet / PUP-6637 New attribute :create_mountpoint for Mount type Issue Type: New Feature Affects Versions: PUP 4.6.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/08/18 12:16 PM Environment: *nix Fix Versions: PUP 4.7.0 Labels: puppet-agent types mount Priority: Normal Reporter: Matt Schuchard The create_mountpoint attribute for
Jira (PUP-6636) Puppet's fileserver seems to be unable to handle a path containing a directory called "environment"
Title: Message Title Chris Price moved an issue Puppet / PUP-6636 Puppet's fileserver seems to be unable to handle a path containing a directory called "environment" Change By: Chris Price Key: SERVER PUP - 1483 6636 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Ben Ford commented on PUP-6631 Re: Apt package provider does not mark managed packages as manual Here's a man page that describes how the marking works and shows the command line tool for marking the package as manual. http://manpages.ubuntu.com/manpages/wily/man8/apt-mark.8.html Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6635) An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf
Title: Message Title Kylo Ginsberg commented on PUP-6635 Re: An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf Yep, done. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6635) An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-6635 An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf Change By: Kylo Ginsberg Affects Version/s: PE 2016.2.1 Affects Version/s: PE 2016.1.1 Component/s: puppet Key: PE PUP - 17169 6635 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups
Jira (PUP-6634) environment.conf should use standard syntax for POSIX and Windows
Title: Message Title Kylo Ginsberg commented on PUP-6634 Re: environment.conf should use standard syntax for POSIX and Windows Yep, moved to PUP and marked it as an Improvement idea. Thoughts on this suggestion, Henrik Lindberg or Ethan Brown? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1460) Load facter.conf when facter. is used as a library
Title: Message Title David Kramer updated an issue Facter / FACT-1460 Load facter.conf when facter. is used as a library Change By: David Kramer Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title John Duarte commented on FACT-1488 Re: git install on Win 2003 fails to clone puppet-win32-ruby repo Thanks Michael Smith. I missed that detail in the failure. The error you reference is exactly the issue we are trying to address. This appears to be intermittent. I have re-opened this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title John Duarte updated an issue Facter / FACT-1488 git install on Win 2003 fails to clone puppet-win32-ruby repo Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title Michael Smith commented on FACT-1488 Re: git install on Win 2003 fails to clone puppet-win32-ruby repo Still ran into mg44e2of40rx33m.delivery.puppetlabs.net (agent-2003r2-i386) 15:13:30$ mkdir .git mg44e2of40rx33m.delivery.puppetlabs.net (agent-2003r2-i386) executed in 0.12 seconds mg44e2of40rx33m.delivery.puppetlabs.net (agent-2003r2-i386) 15:13:30$ cmd /c git config pack.windowMemory 10m mg44e2of40rx33m.delivery.puppetlabs.net (agent-2003r2-i386) executed in 0.14 seconds mg44e2of40rx33m.delivery.puppetlabs.net (agent-2003r2-i386) 15:13:30$ cmd /c git config pack.packSizeLimit 20m
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title John Duarte commented on FACT-1488 Re: git install on Win 2003 fails to clone puppet-win32-ruby repo This has passed in CI https://jenkins.puppetlabs.com/job/legacy_facter_integration-system_windows_2.x/31/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title John Duarte updated an issue Facter / FACT-1488 git install on Win 2003 fails to clone puppet-win32-ruby repo Change By: John Duarte QA Risk Assessment Reason: Covered by CI execution Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title John Duarte updated an issue Facter / FACT-1488 git install on Win 2003 fails to clone puppet-win32-ruby repo Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title John Duarte updated an issue Facter / FACT-1488 git install on Win 2003 fails to clone puppet-win32-ruby repo Change By: John Duarte QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type Okay, working with Branan Riley he pointed out a comment from Michal Ruzicka on PCP-542 about stripping YAML tags before parsing. I implemented this here (excuse the code, its mainly just for show at the moment): https://github.com/puppetlabs/puppet/pull/5214/files#diff-a5348c3071a6b3d7b77bf0ed94147edfR12 Actually seems to work, rather we have no more parsing errors with acl at all now. Still figuring out if this is the right approach of course, but the stripping technique does seem solid on its own. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title Rob Reynolds commented on FACT-1488 Re: git install on Win 2003 fails to clone puppet-win32-ruby repo Michael Smith merged this into 2.x at https://github.com/puppetlabs/facter/commit/289855eea574f6f2ff5977348efa88bfd4276440 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1488) git install on Win 2003 fails to clone puppet-win32-ruby repo
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Facter / FACT-1488 git install on Win 2003 fails to clone puppet-win32-ruby repo Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title
Ken Barber updated an issue
Puppet / PUP-6629
Corrective Change YAML file causes errors when type parameter is a complex type
Change By:
Ken Barber
https://jenkins-modules.puppetlabs.com/view/3.%20windows%20only/view/acl/view/acl%20-%20master/job/forge-windows_puppetlabs-acl_intn-sys_smoke-master/PLATFORM=windows-2008r2-64a,WORKER_LABEL=beaker/20/consoleFull{code}file { 'c:/tmp': ensure => directory,}user { 'bob': ensure => present, groups => 'Users', managehome => true, password => "L0v3Pupp3t!"}acl { 'c:/tmp': permissions => [{ identity => 'bob', perm_type => 'allow', rights => ['modify'] }, ],}{code}The permissions property of acl is a hash type. This looks to be killing runs for anyone using acl or another type that has a parameter/property that is a hash type.The contents of the transactionstore.yaml are as so:{code}---resources: File[c:/temp]:parameters: ensure:system_value: :directory File[c:/temp/deny_full_rights_dir]:parameters: ensure:system_value: :directory User[bob]:parameters: ensure:system_value: :present password:system_value: L0v3Pupp3t! groups:system_value: BUILTIN\Users,Users Acl[c:/temp/deny_full_rights_dir]:parameters: permissions: system_value:- !ruby/hash:Puppet::Type::Acl::Ace { } inherit_parent_permissions:system_value: :true{ code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups
Jira (PDB-2990) reject and/or when no arguments are supplied
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2990 reject and/or when no arguments are supplied Issue Type: Bug Assignee: Unassigned Created: 2016/08/18 10:08 AM Priority: Normal Reporter: Wyatt Alt This query /pdb/query/v4/nodes?query=["extract",[["function","count"]],["and",["<","report_timestamp","2016-08-18T13:27:23.941Z"],["and"]]] fails with a SQL error. We should sniff out and/or clauses with no arguments and reject at the validation level. Add Comment
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title
Ken Barber updated an issue
Puppet / PUP-6629
Corrective Change YAML file causes errors when type parameter is a complex type
Change By:
Ken Barber
https://jenkins-modules.puppetlabs.com/view/3.%20windows%20only/view/acl/view/acl%20-%20master/job/forge-windows_puppetlabs-acl_intn-sys_smoke-master/PLATFORM=windows-2008r2-64a,WORKER_LABEL=beaker/20/consoleFull{code}file { 'c:/tmp': ensure => directory,}user { 'bob': ensure => present, groups => 'Users', managehome => true, password => "L0v3Pupp3t!"}acl { 'c:/tmp': permissions => [{ identity => 'bob', perm_type => 'allow', rights => ['modify'] }, ],}{code}The permissions property of acl is a hash type. This looks to be killing runs for anyone using acl or another type that has a parameter/property that is a hash type.The contents of the transactionstore.yaml are as so:{code} {code} ---resources: File[c:/temp]:parameters: ensure:system_value: :directory File[c:/temp/deny_full_rights_dir]:parameters: ensure:system_value: :directory User[bob]:parameters: ensure:system_value: :present password:system_value: L0v3Pupp3t! groups:system_value: BUILTIN\Users,Users Acl[c:/temp/deny_full_rights_dir]:parameters: permissions:{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title
Ken Barber updated an issue
Puppet / PUP-6629
Corrective Change YAML file causes errors when type parameter is a complex type
Change By:
Ken Barber
https://jenkins-modules.puppetlabs.com/view/3.%20windows%20only/view/acl/view/acl%20-%20master/job/forge-windows_puppetlabs-acl_intn-sys_smoke-master/PLATFORM=windows-2008r2-64a,WORKER_LABEL=beaker/20/consoleFull{code}file { 'c:/tmp': ensure => directory,}user { 'bob': ensure => present, groups => 'Users', managehome => true, password => "L0v3Pupp3t!"}acl { 'c:/tmp': permissions => [{ identity => 'bob', perm_type => 'allow', rights => ['modify'] }, ],}{code}The permissions property of acl is a hash type. This looks to be killing runs for anyone using acl or another type that has a parameter/property that is a hash type. The contents of the transactionstore.yaml are as so:{code}{code}---resources: File[c:/temp]:parameters: ensure:system_value: :directory File[c:/temp/deny_full_rights_dir]:parameters: ensure:system_value: :directory User[bob]:parameters: ensure:system_value: :present password:system_value: L0v3Pupp3t! groups:system_value: BUILTIN\Users,Users Acl[c:/temp/deny_full_rights_dir]:parameters: permissions:{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type So, I think the class Ace.rb just won't deserialize in its current form, I also believe this will show up in ORCH-1285 when you sort out the type loading problem too (at least it looks like a library path problem, but it also might be that the code isn't on the box where you run puppet job ...). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6626) Regression - puppet logs not owned by specified user on OSX
Title: Message Title John Duarte updated an issue Puppet / PUP-6626 Regression - puppet logs not owned by specified user on OSX Change By: John Duarte Affects Version/s: PUP 4.6.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6630) Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows
Title: Message Title Ken Barber commented on PUP-6630 Re: Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows This looks like a duplicate of PUP-6629. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails Fabien Wernli ok, thanks for the additional info. It definitely seems like it should throw an error if the exit code is non-zero, rather than returning an empty string. We'll try to look into that soon. I'm not sure if we have support for STDIN/STDOUT in the server implementation of Puppet::Util::Execution at the moment; can you provide an example use case for that? And maybe we should break that out into a separate ticket so that we can tackle them individually. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type This doesn't solve the issue per se, but it will at least avoid the case where the YAML corrupts and puppet can't continue: https://github.com/puppetlabs/puppet/pull/5214. This puts us in line with the approach to make corrective_change soft fail in the wild as much as possible. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6633) Puppet failed to build catalog error message is ugly
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6633 Puppet failed to build catalog error message is ugly Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Peter Kroon commented on PUP-6631 Re: Apt package provider does not mark managed packages as manual Ah, thanks for the clarification (the word regression also makes sense now ) I don't know, I've only recently started using puppet (about a week now), I've only used 4.6 so far. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Henrik Lindberg commented on PUP-6631 Re: Apt package provider does not mark managed packages as manual Peter Kroon Is this something that used to work, say on Puppet 4.5.x and now fails on Puppet 4.6.0 ? If so, when did you observe it working? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title R.I.Pienaar commented on HI-530 Re: Hiera silently drops malformed hierarchy sources missing sources is normal yes - you might have 100 hosts and only 10 have certname specific files, this should not produce errors/warnings it will be very noisy. badly formed ones should produce errors, though the feedback cycle available to hiera is limited but yeah I think if there's actually a set documented known good thing it should error when a known not good thing is given to it. I suspect the rules arent defined though so ultimately this might just end up as design feedback for lookup rather than fixes to hiera given the place in hieras life cycle. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6629 Corrective Change YAML file causes errors when type parameter is a complex type Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Peter Kroon commented on PUP-6631 Re: Apt package provider does not mark managed packages as manual Henrik Lindberg I'm afraid I don't know what you mean by that. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6630) Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6630 Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows Looks like a regression Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6631 Apt package provider does not mark managed packages as manual Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6633) Puppet failed to build catalog error message is ugly
Title: Message Title Curtis Ruck created an issue Puppet / PUP-6633 Puppet failed to build catalog error message is ugly Issue Type: Bug Affects Versions: PUP 4.6.0 Assignee: Unassigned Created: 2016/08/18 6:39 AM Environment: Windows 2012r2, Puppet Server 2.5 Priority: Normal Reporter: Curtis Ruck In Puppet Server 2.5 the server changed its Error 500 page to contain a JSON object. Puppet should pretty print this error JSON object, by extracting the message array, and printing with newlines, instead of as a giant ugly red blob that is unreadable. This issue is also related to SERVER-1482. Add Comment
Jira (PUP-6630) Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6630 Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows Change By: Henrik Lindberg Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Henrik Lindberg commented on PUP-6631 Re: Apt package provider does not mark managed packages as manual Peter Kroon Is this is a regression? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6632) Regression when comparing user groups
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6632 Regression when comparing user groups Ping Kylo Ginsberg David Kramer - looks like a regression in 4.6.0 Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6632) Regression when comparing user groups
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6632 Regression when comparing user groups Change By: Henrik Lindberg Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Henrik Lindberg commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Ping Kylo Ginsberg does problem sound familiar? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Henrik Lindberg commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard The ruby stacktrace that is logged agent side (I assume it is the agent that errors) when running as a daemon would be of great value in understanding what the cause of the problem is. Stephano Zanzin, can you try a run and dig out the stacktrace from the log on the agent? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title Henrik Lindberg commented on HI-530 Re: Hiera silently drops malformed hierarchy sources Rich tea Thanks. I asked about the rules because there is no specification that says why it is doing what it is doing, and there is also no specification of what should happen when using relative paths. For instance, it could be that the skipping is a feature - such that if you have an undefined variable that is used to interpolate a path, and it therefore ends up starting with a slash is actually a feature, and those entries are to be skipped by design. Ping R.I.Pienaar - any input here? While logging warnings is fine, making it a hard error may in practice be disruptive. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6632) Regression when comparing user groups
Title: Message Title
Mateusz Gozdek created an issue
Puppet / PUP-6632
Regression when comparing user groups
Issue Type:
Bug
Affects Versions:
PUP 4.6.0
Assignee:
Unassigned
Components:
AIO
Created:
2016/08/18 4:09 AM
Priority:
Normal
Reporter:
Mateusz Gozdek
I found, that after updating from Puppet 4.5.3 to 4.6.0, my manifest started throwing an errors.
Minimal manifest to reproduce:
@user { 'foo':
ensure => present,
Jira (HI-530) Hiera silently drops malformed hierarchy sources
Title: Message Title
Rich tea commented on HI-530
Re: Hiera silently drops malformed hierarchy sources
Henrik Lindberg I have created https://github.com/puppetlabs/hiera/pull/360 PR360
As to why, I can see why in the current code the restriction is required the method "datafile_in(datadir, source, extension)" returns the full path and name of the file (if it exists) by adding together a "base directory" (datadir), the "hierarchy source" (source) and extension. Since the source is the middle part of a full file name / path it can not have those pattens. e.g. datadir = " /etc/puppetlabs/code/environments/production/hieradata/" source = "os/${::operatingsystem}" extension = ".json" making the full file path "/etc/hieradata/os/RedHat.json"
It was my original understanding that if a "source" started with a "/" that "datadir" would be skipped, but that is not so.
looking at this now i wonder what would happen if source was something like "../../${::operatingsystem}"
I guess the method "datafile_in" could be modified to check if "source" started with a "/" and not join basedir in if so.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title
Peter Kroon created an issue
Puppet / PUP-6631
Apt package provider does not mark managed packages as manual
Issue Type:
Bug
Affects Versions:
PUP 4.6.0
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
2016/08/18 3:06 AM
Environment:
Ubuntu 16.04.1 LTS
Priority:
Normal
Reporter:
Peter Kroon
The apt package provider does not mark packages as manual. This means that if a package gets removed, some packages may get marked for deletion if nothing depends on them any longer - even though they should be installed according to Puppet.
Example: Puppet purges a package depending on `ethtool`. Nothing depends on `ethtool` any longer, so it gets marked for deletion, but is still installed. Puppet processes 'package {'ethtool': ensure -> installed}
' and does nothing, since it's already installed If something or someone then runs `apt-get -y autoremove` the package ethtool will then be removed (in my case puppet does this later in the run).
Jira (PDOC-63) Blizzard of errors and warnings when run against core code
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet Strings / PDOC-63 Blizzard of errors and warnings when run against core code Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Stephano Zanzin commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Henrik Lindberg run manually means `puppet agent -t`. We found out that the error appears when the puppet agent runs daemon mode, so after disable the daemon mode on the nodes and leaving only the cronjob running `puppet agent -t` the issue disappears. Does that make sense? Thanks a lot for your help. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6630) Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows
Title: Message Title
Kasper Brandenburg created an issue
Puppet / PUP-6630
Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows
Issue Type:
Bug
Affects Versions:
PUP 4.6.0
Assignee:
Unassigned
Components:
Modules, Puppet Server, Windows
Created:
2016/08/18 12:26 AM
Environment:
Windows Server 2016 Tech. Preview 5
Priority:
Normal
Reporter:
Kasper Brandenburg
Using puppet-agent 4.6.0 on Windows Server 2016 Tech Preview 5 Core edition, combined with puppetlabs-acl module 1.1.2, applying this simple ACL, and error is thrown in the second puppet-run (an all runs following)
acl { "c:/temp": permissions => [ { identity => 'Administrator', rights => ['full'] }
, { identity => 'Users', rights => ['read','execute'] }
], }
Error: Transaction store file
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Fabien Wernli commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails yes, I meant it works using puppet apply. The only environment this seems to be failing in is in agent mode against a v4 server. Also, STDIN/STDOUT handling seems broken (combine option in Util Execute) Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
