Jira (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Alex Harvey commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Great to hear, thanks everyone. 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-1526) Package type should support environment variables
Title: Message Title Johnson Earls commented on PUP-1526 Re: Package type should support environment variables Here's a more general use case: Installing packages with the yum provider through a web proxy. There is no command line interface to yum to set the web proxy, it has to be done through the global /etc/yum.conf configuration file or through the environment variable http_proxy. Since modifying the /etc/yum.conf is not practical, especially if you only need the web proxy enabled for certain installation packages or if you need different web proxies for different circumstances, the only real solution to using a proxy with the yum provider would be to have a way to set the http_proxy environment variable. 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-2561) Docs pushed (puppet-client-tools 1.0.0)
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2561 Docs pushed (puppet-client-tools 1.0.0) Change By: Andrew Roetker Resolution: Fixed Assignee: Nicholas Fagerlund Andrew Roetker Status: Open Resolved 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-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Stefan Heijmans because the change in the PR I linked affects nearly all puppet http requests, it can't get merged as is. I think that leaves two possible workarounds for you. Carry the patch yourself from the PR in some manner Configure logback to the warn level for puppet-server. You could do that by changing the root level of INFO in logback.xml to WARN, or to only change puppet-server's loglevel add a line like to logback.xml 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-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ To add onto what Kevin Corcoran said, here is how puppet/syslog loglevels map to puppet-server/logback levels: Puppet/Syslog Puppet-Server/Logback - Trace Debug Debug InfoInfo Notice Info WarnWarn Error Error CriticalError Alert Error Emergency Error
Jira (PUP-6140) Add acceptance test for managing init.d services on systemd-default OS
Title: Message Title Michael Smith commented on PUP-6140 Re: Add acceptance test for managing init.d services on systemd-default OS Expand to Debian? 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-6142) honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6142 honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing Change By: Henrik Lindberg Release Notes Summary: Warnings from ModuleLoader regarding unresolved module dependencies are now controlled by the Puppet --strict setting. When set to 'off', no warnings or errors are produced for unresolved dependencies, and when set to 'warning' one warning per unresolved module is issued per lifetime of a compile service. When set to error, compilation will stop with an error. 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-6102) A type alias that has an alias name of a built-in type should be illegal
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6102 A type alias that has an alias name of a built-in type should be illegal Change By: Henrik Lindberg 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 (PUP-6142) honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing
Title: Message Title Henrik Lindberg commented on PUP-6142 Re: honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing merged to master at: e7b33e5 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-2593) (maint) Remove i18n tests for travis
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2593 (maint) Remove i18n tests for travis Change By: Andrew Roetker Fix Version/s: PDB 4.1.0 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-2593) (maint) Remove i18n tests for travis
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2593 (maint) Remove i18n tests for travis Issue Type: Bug Assignee: Unassigned Created: 2016/04/07 3:36 PM Priority: Normal Reporter: gepetto-bot This commit removes i18n middleware tests as they fail on travis because the locales aren't installed. They also fail locally if the spanish locale isn't installed. This is a temporary hack until we figure out a more permnanent solution. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6129) Add 'new' function support to type alias
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6129
Add 'new' function support to type alias
Change By:
Henrik Lindberg
It should be possible to call new on a type alias by having the alias delegate to its resolved type.ACCEPTANCE_CRITERIA{code:puppet} puppet apply -e ' type MyString X = String ; notice MyString X (42 ,"%#s" ) ' {code} * The above should notice Produces the output{code}Notice: Scope(Class[main]): " 42 "{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 (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Kevin Corcoran commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ No, Puppet Server uses logback which only has trace debug info warn error 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-1379) Facter returns incorrect MAC address for bonded interfaces
Title: Message Title Branan Riley assigned an issue to Branan Riley Facter / FACT-1379 Facter returns incorrect MAC address for bonded interfaces 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-6129) Add 'new' function support to type alias
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6129 Add 'new' function support to type alias Change By: Henrik Lindberg 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 (PUP-6049) lookup cli has bad documentation
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6049 lookup cli has bad documentation Change By: Henrik Lindberg 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 (PUP-6049) lookup cli has bad documentation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6049 lookup cli has bad documentation Change By: Henrik Lindberg Release Notes Summary: Help text for Puppet Lookup corrected for the --knock-out-prefix option. 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-6049) lookup cli has bad documentation
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6049
lookup cli has bad documentation
Change By:
Henrik Lindberg
puppet lookup --help shows various options like:{code}* --knock_out_prefix Can be used with the 'deep' merge strategy. Specify string value to signify prefix which deletes elements from existing element.{code}But the code has:{code} option('--knock-out-prefix PREFIX_STRING') do |arg|options[:prefix] = arg end{code}Thus it fails:{code}% puppet lookup --hiera_config hiera.yaml --merge deep --knock_out_prefix "--" --unpack-arrays "," --sort-merge-arrays --explain-options classificationError: Could not parse application options: invalid option: --knock_out_prefix{code} ACCEPTANCE CRITERIA* That the help text does not mention the faulty {{\--knock_out_prefix}} flag
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-6049) lookup cli has bad documentation
Title: Message Title Henrik Lindberg commented on PUP-6049 Re: lookup cli has bad documentation Fix consisted of fixing a single typo in one example; all other occurrences of --knock_out_prefix were already fixed. Fix was pushed to stable and master. 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-6049) lookup cli has bad documentation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6049 lookup cli has bad documentation Change By: Henrik Lindberg Fix Version/s: PUP 4.5.0 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-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number
Title: Message Title Elizabeth Plumb updated an issue Puppet / PUP-1519 Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number Change By: Elizabeth Plumb CS Priority: Reviewed Needs Priority 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-6128) QualifiedReference should retain case
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6128 QualifiedReference should retain case Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-5844) Add the Object type to the Puppet Type system
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5844 Add the Object type to the Puppet Type system Change By: Henrik Lindberg 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 (PUP-5844) Add the Object type to the Puppet Type system
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5844
Add the Object type to the Puppet Type system
Change By:
Henrik Lindberg
In the Puppet Core Type Model (PCore) that will be used to describe all serialization using the Puppet Type System it is essential to have an {{Object\[T]}} type that matches instances of user defined type {{T}}. We also need the run time abstract {{Object}} from which the concrete instances of user defined data types are derived.This work is also required to enable the full user defined type definition using the syntax:{code:puppet}type TypeName inherits SuperTypeName { # attribute definitions }{code}Which will be added in a separate ticket.UpdateWe have decided (after many rounds of proposals) to use the following syntax for the Object type:{code:puppet} type T = Object[{ parent => < parent-type >, attributes => { }. functions => { }, equality => [ ], order_by equality_includes_type => [ ] Boolean ,}]{code}Those are the basic features that the Object will have. Additional features can be expected later (separate tickets) to handle invariants.ATTRIBUTESThe attributes feature is a map from name to Type for attributes that do not require a default value, or other special settings. For attributes where more than a type is required a hash is used.{code:puppet}attributes => { name name1 => Type, name name2 => { ' type ' => Type, # the type of the value default kind => Enum[given, derived, given_or_derived, constant], value => 'default value literal', final => Boolean, override => Boolean, }}{code} This The above example shows one short form, and one long form attribute. Expect there to be additional properties that can be set on an attribute. The ability to define a {{derived}} (i.e. computed) attribute, and possibly to make at attribute be a constant (read-only). Separate tickets will be added for those. FUNCTIONSThe function feature has fewer properties. Basically this is a name to type map. {code:puppet}functions { name name1 => Callable[ ... ], name name2 => Callable[ ... ],}{code}If a long form is needed it is defined the same way as for attributes.EQUALITYEquality can be specified by giving a list of attributes that must be equal for two instances of the object to be considered equal. If not given. Equality s base on all regular fields (i.e. excluding derived/computed and constant value attributes).{code:puppet}equality => | 'a', 'b', 'c' ]{code} ORDER BYThe order of instances of the Object can be specified. If order is not stated instances are not comparable (they lack magnitude). To specify the natural order of object of this kind, an array of tuples {{\[, ]}} where is the name of an attribute, and direction is {{Enum\[ascending, descending]}}.{code:puppet}order_by => [ ['name' 'ascending''], ['gold-handicap', 'descending' ]{code} IMPLEMENTATIONObject type's not bound to an implementation can be used (a dynamic/generic implementation), but the operations are then not available. For operations to be available there must be a binding beween between an implementation type, and the Object type. Such a binding can be achieved in different ways.* via a special type alias that binds the object type to a Runtime type* via syntax to be
Jira (PDB-2592) Removed "labs" from Puppet Labs
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2592 Removed "labs" from Puppet Labs Issue Type: Bug Assignee: Unassigned Created: 2016/04/07 2:30 PM Priority: Normal Reporter: gepetto-bot 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
Jira (PUP-5844) Add the Object type to the Puppet Type system
Title: Message Title Henrik Lindberg commented on PUP-5844 Re: Add the Object type to the Puppet Type system merged to master at: 30f70dc 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-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Kylo Ginsberg commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Wrt: Puppet has a few more different logging levels available than many logging libraries: Puppet's 8 log levels correspond to syslog's 8 log levels. Is supporting those 8 log levels an option in some way with puppet server? I am asking out of complete ignorance of the implications here, so feel free to enlighten me 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-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number
Title: Message Title Reid Vandewiele commented on PUP-1519 Re: Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number Copying the suggestion originally made in the Redmine issue. Implement a type feature called `minimum_versionable`. feature :minimum_versionable, "The provider is capable of selectively upgrading to the latest version of a package if and only if the installed version is less than a provided minimum version. Using a minimum version of 1.5-2 as an example, this feature is used by specifing `>= 1.5-2` as the desired value for the package." An example implementation was also filed at that time (this was years ago) and can be found here. Add Comment
Jira (PUP-6136) newparam(:downgrade) for package type
Title: Message Title Elizabeth Plumb updated an issue Puppet / PUP-6136 newparam(:downgrade) for package type Change By: Elizabeth Plumb CS Priority: Needs Priority 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-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5296 Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Change By: Michael Smith Status: In Progress Ready for Test Assignee: William Hopper qa 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-2587) Switch i18n generated files to target directory
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2587 Switch i18n generated files to target directory Change By: Ryan Senior Story Points: 2 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-2478) Allow triggering of GC processes via POST
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2478 Allow triggering of GC processes via POST Change By: Ryan Senior Story Points: 3 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-2310) PSQLException when using outdated "select-*" syntax instead of "select_*"
Title: Message Title
Ryan Senior updated an issue
PuppetDB / PDB-2310
PSQLException when using outdated "select-*" syntax instead of "select_*"
Change By:
Ryan Senior
.. Apologies if this is known or resolved in a later release, but I couldn't find a ticket for it.PDB 3.1.1 in PE 2015.2.3When using the old {{select-facts}} operator instead of the proper {{select_facts}} operator, PDB bubbles up a postgres error that is very confusing{code}> curl -XGET localhost:8080/pdb/query/v4/fact-contents -d 'query=["in", "certname", ["extract", "certname", ["select-facts", ["=", "name", "osfamily"'Error 500 HTTP ERROR: 500Problem accessing /pdb/query/v4/fact-contents. Reason:org.postgresql.util.PSQLException: No value specified for parameter 1.
Jira (PUP-6142) honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing
Title: Message Title Chris Price updated an issue Puppet / PUP-6142 honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing Change By: Chris Price Scope Change Category: Adopted 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-6142) honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing
Title: Message Title Chris Price updated an issue Puppet / PUP-6142 honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing Change By: Chris Price Scope Change Reason: needed a PUP ticket to capture PUP work for PE-14865 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-6142) honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing
Title: Message Title Chris Price assigned an issue to Chris Price Puppet / PUP-6142 honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing Change By: Chris Price Assignee: Chris Price 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-6142) honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing
Title: Message Title Chris Price updated an issue Puppet / PUP-6142 honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing Change By: Chris Price Sprint: Server Emerald 2016-04-20 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-6142) honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing
Title: Message Title Chris Price created an issue Puppet / PUP-6142 honor strict mode and use warn_once for ModuleLoader warning, when module dependencies are missing Issue Type: Improvement Assignee: Unassigned Components: Language, Puppet Server Created: 2016/04/07 12:47 PM Priority: Normal Reporter: Chris Price The code that loads modules currently looks to see if they have a forge metadata.json file, and if so, validates that the dependencies are all installed. If any dependencies are missing (which is not uncommon for r10k users), then a warning is logged each time the environment is loaded. For the default configuration with environment_timeout = 0, this means that the warning is logged on every catalog compilation. Some users have indicated that this is causing their logs to grow very large. After discussion with Henrik Lindberg, the proposed change is: 1. if strict mode is :off - log nothing 2. if strict mode is :warning - call warn_once, so that the warning is only logged once (per jruby instance) 3. if strict mode is :error - throw an error and fail compilation
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Nate McCurdy commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
After a bit of testing, realized that this is not idempotent. The gem gets installed on every puppet run.
package { 'colored':
ensure = present
provider=> 'gem',
install_options => {'--install-dir' => 'C:\tools\ruby22\lib\ruby\gems\2.2.0', '--bindir' => 'c:\tools\ruby22\bin'},
}
The reason for that is because the is state is determined by running C:/Program Files/Puppet Labs/Puppet/sys/ruby/bin/gem.bat list --local ^colored$. So it's searching Puppet's gem list rather than the "system" gem list.
Add Comment
Jira (PUP-5616) puppet device convergence impossibility, and improved error output
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5616 puppet device convergence impossibility, and improved error output Change By: Kylo Ginsberg 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-5616) puppet device convergence impossibility, and improved error output
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5616 puppet device convergence impossibility, and improved error output Change By: Kylo Ginsberg Sprint: Client 2016-04-20 (Bigga Bugs) 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-5616) puppet device convergence impossibility, and improved error output
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5616 puppet device convergence impossibility, and improved error output Change By: Kylo Ginsberg Fix Version/s: PUP 4.5.0 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-5616) puppet device convergence impossibility, and improved error output
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5616 puppet device convergence impossibility, and improved error output Change By: Kylo Ginsberg Story Points: 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-6141) Test can pick random GID that collides with existing GID
Title: Message Title Kurt Wall commented on PUP-6141 Re: Test can pick random GID that collides with existing GID On the host system, you can see that the new group was created and that the other GID, 34, was in use by the backup group. root@hem94kl8ueb74gd:~# egrep "(^pl|34)" /etc/group backup:x:34: plugdev:x:46: nogroup:x:65534: pl975867:x:675492: I guess we've just been lucky up to now? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6141) Test can pick random GID that collides with existing GID
Title: Message Title Kurt Wall created an issue Puppet / PUP-6141 Test can pick random GID that collides with existing GID Issue Type: Bug Affects Versions: PUP 4.4.1 Assignee: Eric Sorenson Components: QA Created: 2016/04/07 12:17 PM Priority: Normal Reporter: Kurt Wall The test acceptance/tests/resource/group/should_modify_gid.rb picks two random GIDs when creating a group and changing its GID. If the generated GID already exists, the test will fail to create an new group with the same GID or will fail to change that a group's GID to a value already in use. To wit (from https://jenkins.puppetlabs.com/job/platform_puppet-server_integration-system_no-conditional_full-master/184/) Begin ruby/puppet/acceptance/tests/resource/group/should_modify_gid.rb
Jira (PUP-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Stefan Heijmans commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Just tested with the PR and both message are now gone. 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-1375) Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1375 Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes Change By: Michael Smith Status: Ready for CI Test Assignee: qa 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-6140) Add acceptance test for managing init.d services on systemd-default OS
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-6140 Add acceptance test for managing init.d services on systemd-default OS Change By: Michael Smith Assignee: Michael Smith 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-1296) Transient crash in CI when running unit tests on Windows
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1296 Transient crash in CI when running unit tests on Windows Change By: Michael Smith Status: Ready for CI Test Assignee: qa 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-5825) systemd service provider always enables service in chroot
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5825 systemd service provider always enables service in chroot Change By: Michael Smith Status: Ready for CI Test Assignee: qa 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-6140) Add acceptance test for managing init.d services on systemd-default OS
Title: Message Title Michael Smith created an issue Puppet / PUP-6140 Add acceptance test for managing init.d services on systemd-default OS Issue Type: Task Assignee: Unassigned Created: 2016/04/07 11:49 AM Priority: Normal Reporter: Michael Smith 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
Jira (PUP-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title Michael Smith commented on PUP-5353 Re: Statically-enabled systemd service is treated like SysV init scripts - enabled each run. I've submitted the question to the puppet-dev mailing list. I'll add the link later. 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-2557) Smoke test packages (PDB 0.1.0)
Title: Message Title Andrew Roetker commented on PDB-2557 Re: Smoke test packages (PDB 0.1.0) deb precise and sles-12 both look good too using the pooler with Ryan McKern's 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 (PDB-2475) Add Ubuntu 16.04 Xenial as a build/test platform
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-2475 Add Ubuntu 16.04 Xenial as a build/test platform Change By: Kenn Hussey Fix Version/s: PDB 4.1.0 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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.
Title: Message Title Michael Smith commented on PUP-5353 Re: Statically-enabled systemd service is treated like SysV init scripts - enabled each run. The Redhat provider is lying. The work-around should be to avoid saying enable => true on static services. A fix for this is going to cause an error in your manifest, because enable => true will not happen for a static service. 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Kylo Ginsberg commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Are there downsides to modify the .bat files to build a path where puppet's bin directories are at the end of the path? Offhand it does seem preferable to have Windows use the model on *nix where you can simply select the provider, gem vs puppet_gem rather than tinkering with install_options. Also, a note that if we make that change we'll also need to update the puppet_gem provider we added in puppet 4, because it's implementation at https://github.com/puppetlabs/puppet/blob/4.4.1/lib/puppet/provider/package/puppet_gem.rb#L9-L13 currently relies on the path being setup as it is, rather than the provider knowing the path to puppet's ruby's gem (as it does on *nix). 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-2475) Add Ubuntu 16.04 Xenial as a build/test platform
Title: Message Title Melissa Stone updated an issue PuppetDB / PDB-2475 Add Ubuntu 16.04 Xenial as a build/test platform Change By: Melissa Stone Sprint: RE 2016- 04 05 - 27 04 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-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens commented on PUP-6139 Re: Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Stefan Heijmans I have a PR up with a fix for this. I was able to reproduce the issue with a variation on your file manifest. If you'd like to try out the patch from the PR, I'd love to know if it resolves the issue for you. 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-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Kylo Ginsberg commented on PUP-5296 Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run William Hopper that's great. I was hoping the fix in 5825 would address this issue as well - glad to have you confirm it. Perhaps we should update the summary/description on 5825 to reflect the breadth of the scenarios fixed by the change, and mark this one as a dup of that? And yeah, +1 on acceptance tests around this. 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title
Nate McCurdy commented on PUP-6134
Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Thanks for the clarification Ben Ford. That's exactly my point.
There are many other reasons that someone would want a gem on their Windows system that have nothing to do with developing Puppet modules. Are we going to tell them to use Puppet's Ruby stack for all of those reasons? If the answer is yes, then that is completely opposite of our answer on the *nix side of things.
The gem provider should ideally function exactly the same or at least have feature parity on all Puppet supported operating systems. In its current state, it does the exact opposite of its description when used on Windows. It does what the puppet_gem provider was made for.
A user should be able to run this Puppet code on any supported OS and expect the same outcome. That is the Puppet way after all.
# - minecraftctl to interact with a MineCraft server.
# - gist to be able to share code snippets on gist.github.com.
# - github to be able to interact with GitHub's API.
# - colored to be able to add color to fun little Ruby scripts.
package { [ 'minecraftctl', 'gist', 'github', 'colored' ] :
ensure => present,
provider => gem,
Jira (PUP-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title Michael Smith assigned an issue to William Hopper Puppet / PUP-5296 Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run Change By: Michael Smith Assignee: William Hopper 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-6113) `puppet resource user` on Solaris fails when LDAP users are present
Title: Message Title Michael Smith assigned an issue to Branan Riley Puppet / PUP-6113 `puppet resource user` on Solaris fails when LDAP users are present Change By: Michael Smith 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-6122) add deprecation warning for resource_types endpoint
Title: Message Title Preben Ingvaldsen assigned an issue to Preben Ingvaldsen Puppet / PUP-6122 add deprecation warning for resource_types endpoint Change By: Preben Ingvaldsen Assignee: Preben Ingvaldsen 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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt Alt !! Thanks for helping me with this! I sent you the output of this query to your email wy...@puppetlabs.com (is a big output) 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-5296) Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Title: Message Title
William Hopper commented on PUP-5296
Re: Puppet 4.2.x agent for RHEL 7 enables System V init scripts services on each run
Commit 7a5176c8 (merged yesterday for PUP-5825) changed the enabled? method of the systemd provider to use systemctl is-enabled, as it did before 4.2.0. That ticket specifically was meant to deal with enabling services inside of a chroot, but it looks to have had the added benefit of fixing the issues described here as well.
To verify, I built and installed xymon, which was used in the original example.
One commit before this change, the issue is easily reproducible:
[root@c818zua4k1el6ot puppet]# bundle exec puppet resource service xymon ensure=running enable=true --param provider --debug
...
Debug: Executing: '/usr/bin/systemctl is-active xymon'
Debug: Executing: '/usr/bin/systemctl show xymon --property LoadState --property UnitFileState --no-pager'
Debug: Executing: '/usr/bin/systemctl unmask xymon'
Debug: Executing: '/usr/bin/systemctl enable xymon'
Notice: /Service[xymon]/enable: enable changed 'false' to 'true'
service { 'xymon':
Jira (PDB-2557) Smoke test packages (PDB 0.1.0)
Title: Message Title Andrew Roetker commented on PDB-2557 Re: Smoke test packages (PDB 0.1.0) Smoke tested using the PDB smoke testing guide https://github.com/puppetlabs/pe-puppetdb-extensions/blob/master/dev-docs/smoke_test.org on el7 and puppet-query and puppet-db subcommands both behave properly. 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-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/
Title: Message Title Matthaus Owens moved an issue Puppet / PUP-6139 Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/ Change By: Matthaus Owens Affects Version/s: SERVER 2.3.1 Affects Version/s: SERVER 1.0.2 Component/s: Puppet Server Component/s: Puppet Server Key: SERVER PUP - 388 6139 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1379) Facter returns incorrect MAC address for bonded interfaces
Title: Message Title Branan Riley assigned an issue to Unassigned Facter / FACT-1379 Facter returns incorrect MAC address for bonded interfaces 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 (FACT-1385) Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2
Title: Message Title Michael Smith created an issue Facter / FACT-1385 Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2 Issue Type: Bug Assignee: Unassigned Created: 2016/04/07 9:30 AM Priority: Normal Reporter: Michael Smith Ruby 2.2 appears to have changed the signature of rb_num2long to actually return a long. That results in unit tests failing with Ruby 2.2 on Windows, because there a long is a 32-bit type but we assume rb_num2long returns a 64-bit type. Instead of getting -1, you get INT_MAX+1 (or something close to that). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1296) Transient crash in CI when running unit tests on Windows
Title: Message Title Kylo Ginsberg commented on FACT-1296 Re: Transient crash in CI when running unit tests on Windows Re ticket hygiene: since this is a transient, I propose we close this if it makes it through CI once and just re-open it if we do see a recurrence. 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-1364) facter does not serialize integers above 32bits in structured facts in windows
Title: Message Title Michael Smith assigned an issue to Hailee Kenney Facter / FACT-1364 facter does not serialize integers above 32bits in structured facts in windows Change By: Michael Smith Assignee: Michael Smith Hailee Kenney 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-2557) Smoke test packages (PDB 0.1.0)
Title: Message Title Melissa Stone commented on PDB-2557 Re: Smoke test packages (PDB 0.1.0) Packages are available at http://builds.puppetlabs.lan/puppet-client-tools/1.0.0/ cc/ Ryan McKern 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-6138) Acceptance: pin to released version of puppet-server
Title: Message Title John Duarte created an issue Puppet / PUP-6138 Acceptance: pin to released version of puppet-server Issue Type: Improvement Affects Versions: PUP 4.4.1 Assignee: Unassigned Created: 2016/04/07 8:47 AM Priority: Normal Reporter: John Duarte Currently, the rake task for running puppet acceptance tests deploys puppet-server from nightlies. This has the potential to result in nondeterministic test results when rerunning acceptance for a given puppet or puppet-agent sha. It is recommended that the puppet acceptance testing install the latest release of puppet-server instead of nightly builds. Add Comment
Jira (PUP-6128) QualifiedReference should retain case
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6128
QualifiedReference should retain case
Change By:
Henrik Lindberg
The PL parser creates a qualified reference when it encounters a name that starts with an upper-case letter. The name is immediately downcased so that all subsequent compares involving the name are case insensitive.In many cases it would be desired to know the original name verbatim, such as when reporting type mismatches or resources that are not found. Currently, a name like {{MyGreatResource}} will be reported as {{Mygreatresource}} (an attempt is made to make it look almost as the original) which isn't quite right.In order to fix this, the AST object {{Puppet::Pops::Model::QualifiedReference}} must store the name verbatim, and be able to produce both that name and the downcased name.ACCEPTANCE CRITERIA* That errors mentioning a type retains original casing{code :puppet }2 =~ AbcDef{code} Should produce an error including:{code}Resource type not found: AbcDef{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 (PUP-6128) QualifiedReference should retain case
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6128
QualifiedReference should retain case
Change By:
Henrik Lindberg
The PL parser creates a qualified reference when it encounters a name that starts with an upper-case letter. The name is immediately downcased so that all subsequent compares involving the name are case insensitive.In many cases it would be desired to know the original name verbatim, such as when reporting type mismatches or resources that are not found. Currently, a name like {{MyGreatResource}} will be reported as {{Mygreatresource}} (an attempt is made to make it look almost as the original) which isn't quite right.In order to fix this, the AST object {{Puppet::Pops::Model::QualifiedReference}} must store the name verbatim, and be able to produce both that name and the downcased name. ACCEPTANCE CRITERIA* That errors mentioning a type retains original casing{code}2 =~ AbcDef{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 (PUP-6137) Name anonymous Object when bound to a type name.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6137 Name anonymous Object when bound to a type name. Change By: Henrik Lindberg Release Notes Summary: Part of a large new feature. 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 (PUP-6127) clientnoop agent fact not more working starting from Puppet 4.4.1
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6127 clientnoop agent fact not more working starting from Puppet 4.4.1 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-6136) newparam(:downgrade) for package type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6136 newparam(:downgrade) for package type 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-2591) Service[puppetserver] duplicate declaration
Title: Message Title
Sergey created an issue
PuppetDB / PDB-2591
Service[puppetserver] duplicate declaration
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/04/07 7:41 AM
Priority:
Major
Reporter:
Sergey
Hi,
I have profile where I include the following modules puppet puppetdb puppetdb::master::config
and apply this profile on single puppetserver node. This is hiera structure
puppetserver puppet::server: true puppet::server_foreman: false puppet::server_passenger: false puppet::server_implementation: puppetserver puppet::server_reports: puppetdb puppet::server_environments: "% {hiera('puppet::environment')}
" # code path puppet::environment: production # default environment puppet::server_environments_mode: "0775" puppet::server_external_nodes: '' puppet::additional_settings: server: puppet.improve puppet::hiera_config: /etc/puppetlabs/code/hiera.yaml puppet::server_jvm_min_heap_size: 6G puppet::server_jvm_max_heap_size: 6G puppet::server_jvm_extra_args: '-XX:MaxPermSize=256m'
#puppetdb settings puppet::server_storeconfigs_backend: puppetdb puppetdb::listen_address: 0.0.0.0 puppetdb::database: embedded puppetdb::manage_firewall: false
#puppet agent puppet::puppetmaster: puppet.improve puppet::environment: production
When applying this on puppetserver I get the duplication error:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate
Jira (PUP-6137) Name anonymous Object when bound to a type name.
Title: Message Title
Thomas Hallgren created an issue
Puppet / PUP-6137
Name anonymous Object when bound to a type name.
Issue Type:
Improvement
Assignee:
Thomas Hallgren
Created:
2016/04/07 7:18 AM
Fix Versions:
PU 4.5.0
Priority:
Normal
Reporter:
Thomas Hallgren
The new Object type introduced in PUP-5844 is anonymous and must be aliased to make it possible to refer to it by name. E.g.
type MyObject = Object[{}]
will currently create an alias "MyObject" or an anonymous Object type. This makes it hard to produce meaningful error messages about things that the Object definition may contain. To avoid this, the above _expression_ should actually name the object in case it is anonymous.
In addition, it should also be possible to pass a name in the actual initialization hash for the Object type, e.g.:
Jira (PUP-6136) newparam(:downgrade) for package type
Title: Message Title Matt Schuchard updated an issue Puppet / PUP-6136 newparam(:downgrade) for package type Change By: Matt Schuchard Environment: Theoretically all OS , but then again I have no experience with chocolatey. 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-6099) Additional file and mount autorequire
Title: Message Title Matt Schuchard updated an issue Puppet / PUP-6099 Additional file and mount autorequire Change By: Matt Schuchard Labels: puppet-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 (PUP-6136) newparam(:downgrade) for package type
Title: Message Title Matt Schuchard created an issue Puppet / PUP-6136 newparam(:downgrade) for package type Issue Type: Improvement Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/04/07 6:35 AM Environment: Theoretically all OS Fix Versions: PUP 4.4.2 Labels: puppet-agent Priority: Normal Reporter: Matt Schuchard New parameter :downgrade will downgrade a package if set to true. Defaults to true. Current non-parameter behavior is always true. Initial PR hopefully within a week. Questions: 1. Is this an improvement or new feature? If new feature, is this ok for a Puppet 4.4.x or
Jira (PUP-6127) clientnoop agent fact not more working starting from Puppet 4.4.1
Title: Message Title Rudy YAYON commented on PUP-6127 Re: clientnoop agent fact not more working starting from Puppet 4.4.1 Seems there is an issue with Puppet rspec itself. 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-5844) Add the Object type to the Puppet Type system
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5844 Add the Object type to the Puppet Type system Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-2590) /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Title: Message Title
Robert Heinzmann updated an issue
PuppetDB / PDB-2590
/sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Change By:
Robert Heinzmann
The package "puppetdb" creates template /etc/puppetdb/conf.d/jetty.ini with proper permissions of puppetdb:puppetdb. When running /sbin/puppetdb ssl-setup the file permissions change to "root" "root". If your umask is restrictive (e.g. 027) puppetdb start failes. The attached fix keeps the original file permissions initially set via rpm : . {{--- /usr/libexec/puppetdb/puppetdb-ssl-setup.ORG2015-10-14 00 Another note : 23:52.0 +0200+++ /usr/libexec/puppetdb/puppetdb-ssl-setup2016-04-07 09:04:05.21800 +0200@@ -98,6 +98,8 @@ backupfile $3 tmp=$3.tmp.`date +%s` sed "s/$1/$(echo $2 | sed -e 's/[\/ commands should be chained with & ]/\\ & /g')/g to avoid creating " $3 > $tmp+ chown --reference $3 $tmp+ chmod --reference $3 $tmp mv $tmp $3 }@@ -114,6 +116,8 @@ backupfile $2 tmp=$2.tmp.`date +%s` sed broken " /$1/ s/^/# /" $2 > $tmp+ chown --reference $2 $tmp+ chmod --reference $2 $tmp mv $tmp $2 }@@ -131,6 +135,8 @@ tmp=$2 config files . tmp.`date +%s` cat $2 > ${tmp} echo $1 >> ${tmp}+ chown --reference $2 $tmp+ chmod --reference $2 $tmp mv ${tmp} $2}}
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 (PDB-2590) /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Title: Message Title
Robert Heinzmann created an issue
PuppetDB / PDB-2590
/sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Issue Type:
Bug
Affects Versions:
PDB 2.3.8
Assignee:
Unassigned
Attachments:
fix_permissions_puppetdb_setupssl.txt
Created:
2016/04/07 12:15 AM
Environment:
[rbhe@puppet ~]$ rpm -qa | grep puppetdb puppetdb-terminus-2.3.8-1.el7.noarch puppetdb-2.3.8-1.el7.noarch
Priority:
Normal
Reporter:
Robert Heinzmann
The package "puppetdb" creates template /etc/puppetdb/conf.d/jetty.ini with proper permissions of puppetdb:puppetdb.
When running /sbin/puppetdb ssl-setup the file permissions change to "root" "root". If your umask is restrictive (e.g. 027) puppetdb start failes.
The attached fix keeps the original file permissions initially set via rpm:
{{--- /usr/libexec/puppetdb/puppetdb-ssl-setup.ORG 2015-10-14 00:23:52.0
Jira (PDB-2590) /sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Title: Message Title
Robert Heinzmann updated an issue
PuppetDB / PDB-2590
/sbin/puppetdb ssl-setup breaks file permissions on /etc/puppetdb/conf.d/jetty.ini
Change By:
Robert Heinzmann
The package "puppetdb" creates template /etc/puppetdb/conf.d/jetty.ini with proper permissions of puppetdb:puppetdb. When running /sbin/puppetdb ssl-setup the file permissions change to "root" "root". If your umask is restrictive (e.g. 027) puppetdb start failes. The attached fix keeps the original file permissions initially set via rpm: {{--- /usr/libexec/puppetdb/puppetdb-ssl-setup.ORG2015-10-14 00:23:52.0 +0200+++ /usr/libexec/puppetdb/puppetdb-ssl-setup2016-04-07 09:04:05.21800 +0200@@ -98,6 +98,8 @@ backupfile $3 tmp=$3.tmp.`date +%s` sed "s/$1/$(echo $2 | sed -e 's/[\/&]/\\&/g')/g" $3 > $tmp+ chown --reference $3 $tmp+ chmod --reference $3 $tmp mv $tmp $3 }@@ -114,6 +116,8 @@ backupfile $2 tmp=$2.tmp.`date +%s` sed "/$1/ s/^/# /" $2 > $tmp+ chown --reference $2 $tmp+ chmod --reference $2 $tmp mv $tmp $2 }@@ -131,6 +135,8 @@ tmp=$2.tmp.`date +%s` cat $2 > ${tmp} echo $1 >> ${tmp}+ chown --reference $2 $tmp+ chmod --reference $2 $tmp mv ${tmp} $2 }} }
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
Jira (PUP-6128) QualifiedReference should retain case
Title: Message Title Thomas Hallgren commented on PUP-6128 Re: QualifiedReference should retain case On master before the fix: $ git checkout 2ddfd63 $ bundle exec bin/puppet apply -e '2 =~ AbcDef' Error: Evaluation Error: Resource type not found: Abcdef at line 1:13 on node home.tada.se after the fix: $ git checkout master $ bundle exec bin/puppet apply -e '2 =~ AbcDef' Error: Evaluation Error: Resource type not found: AbcDef at line 1:13 on node home.tada.se Note the difference in case of the missing resource in the error message. Add Comment
Jira (PUP-6048) error running puppet with non existing and non default environment
Title: Message Title Kylo Ginsberg commented on PUP-6048 Re: error running puppet with non existing and non default environment Jorie Tappa is there a documentation ticket needed for the documentation update proposed above? If so, can you link it here? Thanks! 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.
