Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Jacky Leung commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error I found another area that caused the issue. The offending SQL is: SELECT reports.receive_time AS receive_time, reports.corrective_change AS corrective_change, reports.code_id AS code_id, reports.noop AS noop, reports.certname AS certname, reports.puppet_version AS puppet_version, encode(reports.hash::bytea, 'hex') AS hash, reports.cached_catalog_status AS cached_catalog_status, reports.transaction_uuid::text AS transaction_uuid, reports.configuration_version AS configuration_version,
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Jacky Leung commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Hi i can give some update and can confirm it is racing condition. I followed Andrey Galkin suggestion and modified my puppetserver. here is the log on puppetdb Before: puppetserver.docker_default - - [14/Mar/2017:04:31:23 +] "GET /pdb/query/v4/nodes/search-slave-4.srv.fish/facts HTTP/1.1" 200 22984 "-" "Apache-HttpAsyncClient/4.1.1 (Java/1.8.0_91)" puppetserver.docker_default - - [14/Mar/2017:04:31:24 +] "POST /pdb/cmd/v1?checksum=49141ee1c6874add827e8d1c0954cfe39b3634c7=5=search-slave-4.srv.fish=replace_facts HTTP/1.1" 200 53 "-" "Apache-HttpAsyncClient/4.1.1 (Java/1.8.0_91)" puppetserver.docker_default - - [14/Mar/2017:04:31:24 +] "GET /pdb/query/v4/nodes/search-slave-4.srv.fish/facts HTTP/1.1" 200 22984 "-" "Apache-HttpAsyncClient/4.1.1 (Java/1.8.0_91)" 2017-03-14 04:31:24,516 INFO [p.p.command] [a2c40a11-6973-427c-a86f-a70670a7af42] [replace facts] search-slave-4.srv.fish puppetserver.docker_default - - [14/Mar/2017:04:31:24 +] "POST /pdb/cmd/v1?checksum=9cc4a64fcac878174ac1ee8ae0cc924339984d38=9=search-slave-4.srv.fish=replace_catalog HTTP/1.1" 200 53 "-" "Apache-HttpAsyncClient/4.1.1 (Java/1.8.0_91)" 2017-03-14 04:31:25,009 INFO [p.p.command] [c9649961-55a7-40e8-9949-6d4851b5bf1c] [replace catalog] search-slave-4.srv.fish puppetserver.docker_default - - [14/Mar/2017:04:31:25 +] "POST /pdb/cmd/v1?checksum=2ee733a04e4a58ae49c10d8a92d680215ceb41dd=8=search-slave-4.srv.fish=store_report HTTP/1.1" 200 53 "-" "Apache-HttpAsyncClient/4.1.1
Jira (PUP-7148) acceptance: logging 'permission denied' on environmentpath; others
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-7148 acceptance: logging 'permission denied' on environmentpath; others Change By: Eric Thompson Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7327) Hiera 5 doesn't call lookup_with_segments method on hiera3_backend
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7327 Hiera 5 doesn't call lookup_with_segments method on hiera3_backend Change By: Eric Thompson Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7327) Hiera 5 doesn't call lookup_with_segments method on hiera3_backend
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7327 Hiera 5 doesn't call lookup_with_segments method on hiera3_backend Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests; custom_backend object created. dotted key sending tested. other custom backend functionality covered in existing acceptance. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7327) Hiera 5 doesn't call lookup_with_segments method on hiera3_backend
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7327 Hiera 5 doesn't call lookup_with_segments method on hiera3_backend Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7240) A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists.
Title: Message Title Eric Thompson commented on PUP-7240 Re: A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists. Thomas Hallgren does this need release notes? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7240) A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7240 A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists. Change By: Eric Thompson QA Risk Assessment Reason: covered by unit tests; cover user story with larger acceptance later when user story is defined for custom LookupAdapter Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7240) A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7240 A custom LookupAdapter provided to a Puppet::Pops::Lookup::Invocation is ignored if a parent_invocation exists. Change By: Eric Thompson QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-7204
Add support for mapped paths in hiera.yaml version 5
Change By:
Eric Thompson
Comment:
and {{mapped_paths}} overrides {{path}}?https://github.com/puppetlabs/puppet/pull/5666/files#diff-2c12cbb4931cfd2102db8d688e73049eR744
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Eric Thompson commented on PUP-7204 Re: Add support for mapped paths in hiera.yaml version 5 and mapped_paths overrides path? https://github.com/puppetlabs/puppet/pull/5666/files#diff-2c12cbb4931cfd2102db8d688e73049eR744 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-7204
Add support for mapped paths in hiera.yaml version 5
Change By:
Eric Thompson
The feature of being able to map an array variable to multiple paths in the hierarchy has been on the wish list for quite some time. This was originally requested in HI-257 (then rejected, because there was no easy way of supporting this in the old hiera 3 format).Now in hiera.yaml version 5, this is doable.Proposed design:As yet an alternative to the existing {{path}}, {{paths}} , {{glob}}, {{globs}} etc. we add a {{mapped_paths}} that operates on a fact that is a collection, and maps that into an array of paths. {code}mapped_paths: - - - {code}As an example, a fact named {{$services}} contains the array {{\["a", "b", "c"]}}, then this configuration:{code}- name: Example mapped_paths: [services, tmp, "service/%{tmp}/common.yaml"]{code}has the same results as if paths had been specified to be {{\[service/a/common.yaml, service/b/common.yaml, service/c/common.yaml]}}.The operation is basically a call to {{map}} with the following rules:* The collection is mapped and each entry is assigned in turn to the given variable name* The given (temporary) variable name is only available locally in the specific {{mapped_paths}}.* the given variable may shadow an outer variable* If the collection is a hash, each iteration produces a key-value tuple and assigns it to the named variable* If the referenced collection is not a collection is is turned into a one element array before mapping.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Eric Thompson commented on PUP-7204 Re: Add support for mapped paths in hiera.yaml version 5 from the PR: It must be a three element array of strings where the first string denotes a scope variable that should point to a collection of strings, the second string is the variable name that will be mapped to each element of the collection, and the third string is a template where that variable can be used in interpolation expressions. i'm unclear what the second argument does (it's mapped onto each element's value? why? the third is to be used in interpolation expressions? interpolations where? in the data? is this so global variables can be defined IN the config file? only used in hiera? can they be used in other parts of the config file(s)? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7204) Add support for mapped paths in hiera.yaml version 5
Title: Message Title Eric Thompson commented on PUP-7204 Re: Add support for mapped paths in hiera.yaml version 5 i don't really understand why we have path and paths let alone another called mapped_paths is there a reason hiera/puppet can't figure out what i'm doing and do the right thing? just use path and accept strings and (other) collections? Lori Landesman Lindsey Smith, thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7340) context_spec.rb fails when run in isolation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7340 context_spec.rb fails when run in isolation Change By: Josh Cooper Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted. PRs that have been updated to not use interpolation are marked as such:https://github.com/puppetlabs/puppet/pull/5559 (merged)https://github.com/puppetlabs/puppet/pull/5561 https://github.com/puppetlabs/puppet/pull/5562 (updated)https://github.com/puppetlabs/puppet/pull/5563 (updated) https://github.com/puppetlabs/puppet/pull/5564 (updated)https://github.com/puppetlabs/puppet/pull/5565 https://github.com/puppetlabs/puppet/pull/5566 (updated) https://github.com/puppetlabs/puppet/pull/5567 (updated)https://github.com/puppetlabs/puppet/pull/5568 (updated)https://github.com/puppetlabs/puppet/pull/5569 (updated)https://github.com/puppetlabs/puppet/pull/5570 (updated)https://github.com/puppetlabs/puppet/pull/5571 (updated)https://github.com/puppetlabs/puppet/pull/5572 (updated)https://github.com/puppetlabs/puppet/pull/5573 (updated)https://github.com/puppetlabs/puppet/pull/5574 (updated)https://github.com/puppetlabs/puppet/pull/5575 (updated)https://github.com/puppetlabs/puppet/pull/5576 (updated)https://github.com/puppetlabs/puppet/pull/5675 (updated)https://github.com/puppetlabs/puppet/pull/5579 (updated)https://github.com/puppetlabs/puppet/pull/5580 (updated)https://github.com/puppetlabs/puppet/pull/5581 (updated)https://github.com/puppetlabs/puppet/pull/5582 (updated)https://github.com/puppetlabs/puppet/pull/5583 (updated)https://github.com/puppetlabs/puppet/pull/5584 (updated)https://github.com/puppetlabs/puppet/pull/5585 (updated)https://github.com/puppetlabs/puppet/pull/5586 (updated)https://github.com/puppetlabs/puppet/pull/5587 (updated)https://github.com/puppetlabs/puppet/pull/5588 (updated)https://github.com/puppetlabs/puppet/pull/5589 (updated)https://github.com/puppetlabs/puppet/pull/5590 (updated)https://github.com/puppetlabs/puppet/pull/5591 (updated)https://github.com/puppetlabs/puppet/pull/5592 (updated) Add Comment
Jira (PUP-4039) package resource doesn't find new packages in yum repo
Title: Message Title
Matthew Cover commented on PUP-4039
Re: package resource doesn't find new packages in yum repo
I think I've figured out a better way to solve this than (#5699|https://github.com/puppetlabs/puppet/pull/5699). I'd still like to see (#5699|https://github.com/puppetlabs/puppet/pull/5699) get merged as it fixes this issue. Then we can work the proposal below as a separate effort.
`yum install` has 3 alternate versions which can be seen in the (rhel7 documentation|https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-Working_with_Packages.html).
yum install-n name
yum install-na name.architecture
yum install-nevra name-epoch:version-release.architecture
Unlike `yum install`, `yum install-n` will not install virtual packages ('virtual capabilities' in RPM parlance), but will install with the real package name.
[root@localhost ~]# yum install-n inetd
Loaded plugins: fastestmirror
Jira (PUP-7318) Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7318 Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10 Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7318) Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10
Title: Message Title Thomas Hallgren commented on PUP-7318 Re: Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10 Josh Cooper, the one that shouldn't have been backported is PUP-4283 . That backport should be reverted. Puppet::Interface#version exposes the SemVer as public API. SemVer should be removed in Puppet 5.0. I added ticket 7345 to track that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7212) Implement Pcore Object annotation pattern
Title: Message Title Thomas Hallgren commented on PUP-7212 Re: Implement Pcore Object annotation pattern @erict, annotations is a generic functionality in Pcore. We use it when we replace the rgen model and the intention is to use it in netconf too. Nevertheless, I think the current unit tests cover the functionality well so I don't see any real need for acceptance testing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title
Jason Nance commented on PUP-7343
Re: exec path and environment attributes do not work as documented
To make this even more interesting, if I change the exec to this:
exec { 'audit_in_grub2':
path=> [
'/usr/local/sbin',
'/usr/bin',
],
environment => 'PATH=/usr/local/sbin:/usr/sbin:/usr/bin',
command => 'update-grub2-for-audit.sh',
unless => "grep 'audit=1' /etc/sysconfig/grub", # lint:ignore:double_quoted_strings
}
...I get the following warning (yes, twice):
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title
Jason Nance updated an issue
Puppet / PUP-7343
exec path and environment attributes do not work as documented
Change By:
Jason Nance
According to https://docs.puppet.com/puppet/latest/type.html#exec-attribute-environment, the {{environment}} attribute should override the {{path}} attribute if specified. However, attempting to execute the following code:{code}exec { 'audit_in_grub2':environment => [ 'PATH= " /usr/local/sbin:/usr/sbin:/usr/bin " ' ],command => 'update-grub2-for-audit.sh',unless => "grep 'audit=1' /etc/sysconfig/grub", # lint:ignore:double_quoted_strings}{code}...results in the following error:{noformat}Error: Failed to apply catalog: Parameter unless failed on Exec[audit_in_grub2]: 'grep 'audit=1' /etc/sysconfig/grub' is not qualified and no path was specified. Please qualify the command or specify a path. at /etc/puppetlabs/code/environments/KT_tkc_holdings_pnp_production_c7stable_42/modules/audit/manifests/config.pp:13{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5058) The sshkey Type's Default Target for Mac OS X 10.11 (El Capitan) is Incorrect
Title: Message Title Kurt Wall updated an issue Puppet / PUP-5058 The sshkey Type's Default Target for Mac OS X 10.11 (El Capitan) is Incorrect Change By: Kurt Wall QA Contact: Eric Thompson Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7345) Remove deprecated SemVer implementation
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7345 Remove deprecated SemVer implementation Issue Type: Improvement Assignee: Unassigned Created: 2017/03/13 3:15 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Thomas Hallgren The old SemVer implementation is no longer used and deprecation warnings has been logged since 4.9. It should be removed in the next major release. Add Comment
Jira (PUP-7318) Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10
Title: Message Title Josh Cooper assigned an issue to Thomas Hallgren Can you confirm that the backported change to 4.10.x should be reverted, and the lib/semver question in 5.0? Puppet / PUP-7318 Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10 Change By: Josh Cooper Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7318) Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10
Title: Message Title Josh Cooper commented on PUP-7318 Re: Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10 Thomas Hallgren and Henrik Lindberg mentioned PUP-7341 should not have been backported to 4.10.x because it is an API change. We need to get confirmation what the API change is (because the ticket doesn't mention that and we'll want to release note that). Also lib/semver.rb is still in master, but Henrik Lindberg indicated it should not be (and instead puppet should be using the vendored semantic_puppet, which ideally can be removed in Puppet 5 (depending on PUP-7157 and PA-1018). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1587) Need to add more --no-custom-facts tests
Title: Message Title Eric Delaney created an issue Facter / FACT-1587 Need to add more --no-custom-facts tests Issue Type: Task Affects Versions: FACT 3.6.2 Assignee: Unassigned Created: 2017/03/13 2:38 PM Priority: Normal Reporter: Eric Delaney Need to add more tests for --no-custom-facts option TestRail: C64171 --no-custom-facts should cause facter to error if --custom-dir is specified --no-custom-facts should cause facter to error if custom-dir specified in configuration file --no-custom-facts should cause facter to not use the FACTERLIB environment variable Add Comment
Jira (PUP-7212) Implement Pcore Object annotation pattern
Title: Message Title Eric Thompson commented on PUP-7212 Re: Implement Pcore Object annotation pattern this appears to support the move from rgen to pcore in allowing for annotations on types and attributes. are there user facing changes that need testing in acceptance? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.
Title: Message Title Ethan Brown commented on PUP-6983 Re: File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0. I think PUP-7063 is the ticket to handle the console work, but I'm not 100% positive that the issues are one and the same here - I'd prefer to double check this ticket against the fix for 7063 at the time that work is done if it's OK with everyone? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7212) Implement Pcore Object annotation pattern
Title: Message Title Eric Thompson commented on PUP-7212 Re: Implement Pcore Object annotation pattern Thomas Hallgren Henrik Lindberg Lindsey Smith is there a user story from which this stems? what is the use case and/or acceptance criteria? thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1396) Replace Facter 2.x queries with WMI where applicable
Title: Message Title Ethan Brown commented on FACT-1396 Re: Replace Facter 2.x queries with WMI where applicable I think we will still need to do this when we decide to support Nano. Our initial Nano server testing will have to be spec only against Puppet repo (i.e. an install with git clone) - I'm not sure if the C++ toolchain works if we were to add it to CI to build / test Facter. To support acceptance requires that Nano Server packages are built, which involves a complete overhaul to add a new packaging format on Windows (given MSI doesn't work on Nano). So we've got a few things that we will need to do as we figure this out: Make sure Facter 2 behaves properly so that Nano specs can be run from a git install, for the sake of the Puppet repo (same would hold true for module testing I believe - which sometimes require custom facts) Figure out what to do about Facter 3: Get build toolchain working on Nano? Get binaries building once for Windows and enable testing those binaries on different Windows platforms / architectures Get Facter 3 packaged up as a gem? My statement about acceptance testing isn't strictly true - while we can't run an MSI, we can extract it like a zip / tarball. It might be too hacky to be useful, or it might be a useful stopgap solution - we'd have to spend a little time figuring that out. Add Comment
Jira (PUP-7344) acceptance: hiera5 config interpolated with various scoped and nested variables
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-7344 acceptance: hiera5 config interpolated with various scoped and nested variables Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7344) acceptance: hiera5 config interpolated with various scoped and nested variables
Title: Message Title Eric Thompson created an issue Puppet / PUP-7344 acceptance: hiera5 config interpolated with various scoped and nested variables Issue Type: Sub-task Assignee: Eric Thompson Components: QA Created: 2017/03/13 1:43 PM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title
Jason Nance updated an issue
Puppet / PUP-7343
exec path and environment attributes do not work as documented
Change By:
Jason Nance
According to https://docs.puppet.com/puppet/latest/type.html#exec-attribute-environment, the {{environment}} attribute should override the {{path}} attribute if specified. However, attempting to execute the following code:{code}exec { 'audit_in_grub2':environment => [ 'PATH="/usr/local/sbin:/usr/sbin:/usr/bin"' ],command => 'update-grub2-for-audit.sh',unless => "grep 'audit=1' /etc/sysconfig/grub", # lint:ignore:double_quoted_strings}{code}...results in the following error:{noformat}Error: Failed to apply catalog: Parameter unless failed on Exec[audit_in_grub2]: 'grep 'audit=1' /etc/sysconfig/grub' is not qualified and no path was specified. Please qualify the command or specify a path. at /etc/puppetlabs/code/environments/KT_tkc_holdings_pnp_production_c7stable_42/modules/audit/manifests/config.pp:13{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7343) exec path and environment attributes do not work as documented
Title: Message Title
Jason Nance created an issue
Puppet / PUP-7343
exec path and environment attributes do not work as documented
Issue Type:
Bug
Affects Versions:
PUP 4.9.0
Assignee:
Unassigned
Created:
2017/03/13 12:48 PM
Environment:
CentOS 7, x86_64 puppet-agent-1.9.0-1 from PC1 repo
Priority:
Normal
Reporter:
Jason Nance
According to https://docs.puppet.com/puppet/latest/type.html#exec-attribute-environment, the environment attribute should override the path attribute if specified. However, attempting to execute the following code:
exec { 'audit_in_grub2':
environment => [ 'PATH="/usr/local/sbin:/usr/sbin:/usr/bin"' ],
Jira (PUP-7338) puppet command on ciscoXR VM segfaults or core dump
Title: Message Title Scott Garman commented on PUP-7338 Re: puppet command on ciscoXR VM segfaults or core dump We can close it as a dupe so long as our QA folks are aware of the situation and can track the issue without this one. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7338) puppet command on ciscoXR VM segfaults or core dump
Title: Message Title Sean McDonald commented on PUP-7338 Re: puppet command on ciscoXR VM segfaults or core dump Scott Garman should we close this as a dup? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted. PRs that have been updated to not use interpolation are marked as such:https://github.com/puppetlabs/puppet/pull/5559 (merged)https://github.com/puppetlabs/puppet/pull/5561 https://github.com/puppetlabs/puppet/pull/5562 (updated)https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564 (updated)https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567 (updated)https://github.com/puppetlabs/puppet/pull/5568 (updated)https://github.com/puppetlabs/puppet/pull/5569 (updated)https://github.com/puppetlabs/puppet/pull/5570 (updated)https://github.com/puppetlabs/puppet/pull/5571 (updated)https://github.com/puppetlabs/puppet/pull/5572 (updated)https://github.com/puppetlabs/puppet/pull/5573 (updated)https://github.com/puppetlabs/puppet/pull/5574 (updated)https://github.com/puppetlabs/puppet/pull/5575 (updated)https://github.com/puppetlabs/puppet/pull/5576 (updated)https://github.com/puppetlabs/puppet/pull/5675 (updated)https://github.com/puppetlabs/puppet/pull/5579 (updated)https://github.com/puppetlabs/puppet/pull/5580 (updated)https://github.com/puppetlabs/puppet/pull/5581 (updated)https://github.com/puppetlabs/puppet/pull/5582 (updated)https://github.com/puppetlabs/puppet/pull/5583 (updated)https://github.com/puppetlabs/puppet/pull/5584 (updated)https://github.com/puppetlabs/puppet/pull/5585 (updated)https://github.com/puppetlabs/puppet/pull/5586 (updated)https://github.com/puppetlabs/puppet/pull/5587 (updated)https://github.com/puppetlabs/puppet/pull/5588 (updated)https://github.com/puppetlabs/puppet/pull/5589 (updated)https://github.com/puppetlabs/puppet/pull/5590 (updated)https://github.com/puppetlabs/puppet/pull/5591 (updated)https://github.com/puppetlabs/puppet/pull/5592 (updated) Add Comment
Jira (PUP-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted. PRs that have been updated to not use interpolation are marked as such:https://github.com/puppetlabs/puppet/pull/5559 (merged)https://github.com/puppetlabs/puppet/pull/5561 https://github.com/puppetlabs/puppet/pull/5562 (updated)https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564 (updated)https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567 (updated)https://github.com/puppetlabs/puppet/pull/5568 (updated)https://github.com/puppetlabs/puppet/pull/5569 (updated)https://github.com/puppetlabs/puppet/pull/5570 (updated)https://github.com/puppetlabs/puppet/pull/5571 (updated)https://github.com/puppetlabs/puppet/pull/5572 (updated)https://github.com/puppetlabs/puppet/pull/5573 (updated)https://github.com/puppetlabs/puppet/pull/5574 (updated)https://github.com/puppetlabs/puppet/pull/5575 (updated)https://github.com/puppetlabs/puppet/pull/5576 (updated)https://github.com/puppetlabs/puppet/pull/5675 (updated)https://github.com/puppetlabs/puppet/pull/5579 (updated)https://github.com/puppetlabs/puppet/pull/5580 (updated)https://github.com/puppetlabs/puppet/pull/5581 (updated)https://github.com/puppetlabs/puppet/pull/5582 (updated)https://github.com/puppetlabs/puppet/pull/5583 (updated)https://github.com/puppetlabs/puppet/pull/5584 (updated)https://github.com/puppetlabs/puppet/pull/5585 (updated)https://github.com/puppetlabs/puppet/pull/5586 (updated)https://github.com/puppetlabs/puppet/pull/5587 (updated)https://github.com/puppetlabs/puppet/pull/5588 (updated)https://github.com/puppetlabs/puppet/pull/5589 (updated)https://github.com/puppetlabs/puppet/pull/5590 (updated)https://github.com/puppetlabs/puppet/pull/5591 (updated) https://github.com/puppetlabs/puppet/pull/5592 Add Comment
Jira (PUP-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted. PRs that have been updated to not use interpolation are marked as such:https://github.com/puppetlabs/puppet/pull/5559 (merged)https://github.com/puppetlabs/puppet/pull/5561 https://github.com/puppetlabs/puppet/pull/5562 (updated)https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564 (updated)https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567 (updated)https://github.com/puppetlabs/puppet/pull/5568 (updated)https://github.com/puppetlabs/puppet/pull/5569 (updated)https://github.com/puppetlabs/puppet/pull/5570 (updated)https://github.com/puppetlabs/puppet/pull/5571 (updated)https://github.com/puppetlabs/puppet/pull/5572 (updated)https://github.com/puppetlabs/puppet/pull/5573 (updated)https://github.com/puppetlabs/puppet/pull/5574 (updated)https://github.com/puppetlabs/puppet/pull/5575 (updated)https://github.com/puppetlabs/puppet/pull/5576 (updated)https://github.com/puppetlabs/puppet/pull/5675 (updated)https://github.com/puppetlabs/puppet/pull/5579 (updated)https://github.com/puppetlabs/puppet/pull/5580 (updated)https://github.com/puppetlabs/puppet/pull/5581 (updated)https://github.com/puppetlabs/puppet/pull/5582 (updated)https://github.com/puppetlabs/puppet/pull/5583 (updated)https://github.com/puppetlabs/puppet/pull/5584 (updated)https://github.com/puppetlabs/puppet/pull/5585 (updated)https://github.com/puppetlabs/puppet/pull/5586 (updated)https://github.com/puppetlabs/puppet/pull/5587 (updated)https://github.com/puppetlabs/puppet/pull/5588 (updated)https://github.com/puppetlabs/puppet/pull/5589 (updated)https://github.com/puppetlabs/puppet/pull/5590 (updated) https://github.com/puppetlabs/puppet/pull/5591https://github.com/puppetlabs/puppet/pull/5592 Add Comment
Jira (PUP-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted. PRs that have been updated to not use interpolation are marked as such:https://github.com/puppetlabs/puppet/pull/5559 (merged)https://github.com/puppetlabs/puppet/pull/5561 https://github.com/puppetlabs/puppet/pull/5562 (updated)https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564 (updated)https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567 (updated) https://github.com/puppetlabs/puppet/pull/5568 (updated)https://github.com/puppetlabs/puppet/pull/5569 (updated)https://github.com/puppetlabs/puppet/pull/5570 (updated)https://github.com/puppetlabs/puppet/pull/5571 (updated)https://github.com/puppetlabs/puppet/pull/5572 (updated)https://github.com/puppetlabs/puppet/pull/5573 (updated)https://github.com/puppetlabs/puppet/pull/5574 (updated)https://github.com/puppetlabs/puppet/pull/5575 (updated)https://github.com/puppetlabs/puppet/pull/5576 (updated)https://github.com/puppetlabs/puppet/pull/5675 (updated)https://github.com/puppetlabs/puppet/pull/5579 (updated)https://github.com/puppetlabs/puppet/pull/5580 (updated)https://github.com/puppetlabs/puppet/pull/5581 (updated)https://github.com/puppetlabs/puppet/pull/5582 (updated)https://github.com/puppetlabs/puppet/pull/5583 (updated)https://github.com/puppetlabs/puppet/pull/5584 (updated)https://github.com/puppetlabs/puppet/pull/5585 (updated)https://github.com/puppetlabs/puppet/pull/5586 (updated)https://github.com/puppetlabs/puppet/pull/5587 (updated)https://github.com/puppetlabs/puppet/pull/5588 (updated)https://github.com/puppetlabs/puppet/pull/5589 (updated)https://github.com/puppetlabs/puppet/pull/5590https://github.com/puppetlabs/puppet/pull/5591https://github.com/puppetlabs/puppet/pull/5592 Add Comment
Jira (PUP-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted. PRs that have been updated to not use interpolation are marked as such:https://github.com/puppetlabs/puppet/pull/5559 (merged)https://github.com/puppetlabs/puppet/pull/5561 https://github.com/puppetlabs/puppet/pull/5562 (updated)https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564 (updated) https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567https://github.com/puppetlabs/puppet/pull/5568 (updated)https://github.com/puppetlabs/puppet/pull/5569 (updated)https://github.com/puppetlabs/puppet/pull/5570 (updated)https://github.com/puppetlabs/puppet/pull/5571 (updated)https://github.com/puppetlabs/puppet/pull/5572 (updated)https://github.com/puppetlabs/puppet/pull/5573 (updated)https://github.com/puppetlabs/puppet/pull/5574 (updated)https://github.com/puppetlabs/puppet/pull/5575 (updated)https://github.com/puppetlabs/puppet/pull/5576 (updated)https://github.com/puppetlabs/puppet/pull/5675 (updated)https://github.com/puppetlabs/puppet/pull/5579 (updated)https://github.com/puppetlabs/puppet/pull/5580 (updated)https://github.com/puppetlabs/puppet/pull/5581 (updated)https://github.com/puppetlabs/puppet/pull/5582 (updated)https://github.com/puppetlabs/puppet/pull/5583 (updated)https://github.com/puppetlabs/puppet/pull/5584 (updated)https://github.com/puppetlabs/puppet/pull/5585 (updated)https://github.com/puppetlabs/puppet/pull/5586 (updated)https://github.com/puppetlabs/puppet/pull/5587 (updated)https://github.com/puppetlabs/puppet/pull/5588 (updated)https://github.com/puppetlabs/puppet/pull/5589 (updated)https://github.com/puppetlabs/puppet/pull/5590https://github.com/puppetlabs/puppet/pull/5591https://github.com/puppetlabs/puppet/pull/5592 Add Comment
Jira (PUP-7144) Review error string marking and externalization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Maggie Dreyer This ticket tracks the work of reviewing a series of PRs in which user-facing error and info level strings are marked for translation in Puppet (see PUP-7042). The review is being tracked separately due to the sheer volume of work it will entail.Pull requests will be added to this list as they are posted. PRs that have been updated to not use interpolation are marked as such:https://github.com/puppetlabs/puppet/pull/5559 (merged)https://github.com/puppetlabs/puppet/pull/5561 https://github.com/puppetlabs/puppet/pull/5562 (updated)https://github.com/puppetlabs/puppet/pull/5563https://github.com/puppetlabs/puppet/pull/5564https://github.com/puppetlabs/puppet/pull/5565https://github.com/puppetlabs/puppet/pull/5566https://github.com/puppetlabs/puppet/pull/5567https://github.com/puppetlabs/puppet/pull/5568 (updated) https://github.com/puppetlabs/puppet/pull/5569 (updated)https://github.com/puppetlabs/puppet/pull/5570 (updated)https://github.com/puppetlabs/puppet/pull/5571 (updated)https://github.com/puppetlabs/puppet/pull/5572 (updated)https://github.com/puppetlabs/puppet/pull/5573 (updated)https://github.com/puppetlabs/puppet/pull/5574 (updated)https://github.com/puppetlabs/puppet/pull/5575 (updated)https://github.com/puppetlabs/puppet/pull/5576 (updated)https://github.com/puppetlabs/puppet/pull/5675 (updated)https://github.com/puppetlabs/puppet/pull/5579 (updated)https://github.com/puppetlabs/puppet/pull/5580 (updated)https://github.com/puppetlabs/puppet/pull/5581 (updated)https://github.com/puppetlabs/puppet/pull/5582 (updated)https://github.com/puppetlabs/puppet/pull/5583 (updated)https://github.com/puppetlabs/puppet/pull/5584 (updated)https://github.com/puppetlabs/puppet/pull/5585 (updated)https://github.com/puppetlabs/puppet/pull/5586 (updated)https://github.com/puppetlabs/puppet/pull/5587 (updated) https://github.com/puppetlabs/puppet/pull/5588 (updated) https://github.com/puppetlabs/puppet/pull/5589 (updated) https://github.com/puppetlabs/puppet/pull/5590https://github.com/puppetlabs/puppet/pull/5591https://github.com/puppetlabs/puppet/pull/5592 Add Comment
Jira (FACT-1493) Could not retrieve local facts: failed to parse display name of moniker
Title: Message Title Jeff Sparrow commented on FACT-1493 Re: Could not retrieve local facts: failed to parse display name of moniker Sorry. Must have missed the update on it. Have not seen it again, and the path to get there was odd (ps script, as remote user, on a windows install script, etc, etc.) Thanks and my apologies. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1500) Message catalog generation fails on Windows
Title: Message Title Andrew Henroid commented on FACT-1500 Re: Message catalog generation fails on Windows Yep, that makes sense. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1396) Replace Facter 2.x queries with WMI where applicable
Title: Message Title Branan Riley commented on FACT-1396 Re: Replace Facter 2.x queries with WMI where applicable Ethan Brown Is this still worth considering, given the EOL of Puppet 3 / Facter 2? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7342 Create acceptance test for PUP-5058 Change By: Kurt Wall QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7342 Create acceptance test for PUP-5058 Change By: Kurt Wall Sprint: Agent 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7342 Create acceptance test for PUP-5058 Change By: Kurt Wall Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7342 Create acceptance test for PUP-5058 Change By: Kurt Wall Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall updated an issue Puppet / PUP-7342 Create acceptance test for PUP-5058 Change By: Kurt Wall QA Risk Assessment Reason: Test ticket Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1574) Add acceptance tests for supported agent fact directories
Title: Message Title Maggie Dreyer commented on FACT-1574 Re: Add acceptance tests for supported agent fact directories Mergeup complete. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall created an issue Puppet / PUP-7342 Create acceptance test for PUP-5058 Issue Type: Bug Assignee: Kurt Wall Components: Types and Providers Created: 2017/03/13 9:33 AM Priority: Normal Reporter: Kurt Wall Create an acceptance test confirming that Puppet can manage SSH keys on OS X 10.9, 10.10, and 10.11 – the location of ssh_known_hosts moved from /etc/ to /etc/ssh in OS X 10.11. Add Comment This message was sent
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Geoff Nichols assigned an issue to Sean McDonald Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Geoff Nichols Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1574) Add acceptance tests for supported agent fact directories
Title: Message Title Geoff Nichols assigned an issue to Maggie Dreyer Facter / FACT-1574 Add acceptance tests for supported agent fact directories Change By: Geoff Nichols Assignee: Eric Delaney Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7335) "user" resource changes root role to root user on Solaris 11 during root password change
Title: Message Title Josh Cooper commented on PUP-7335 Re: "user" resource changes root role to root user on Solaris 11 during root password change Thanks Mike Asher, I'll close this out. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7341) Regex Lookup isn't working with Puppet 4.9
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7341 Regex Lookup isn't working with Puppet 4.9 Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7341) Regex Lookup isn't working with Puppet 4.9
Title: Message Title Moses Mendoza moved an issue Puppet / PUP-7341 Regex Lookup isn't working with Puppet 4.9 Change By: Moses Mendoza Affects Version/s: HI 3.3.1 Affects Version/s: PUP 4.9.4 Key: HI PUP - 562 7341 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7335) "user" resource changes root role to root user on Solaris 11 during root password change
Title: Message Title Mike Asher commented on PUP-7335 Re: "user" resource changes root role to root user on Solaris 11 during root password change I read the documentation for the resource this is what I needed . ensure => 'role', So this is not a bug Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6114) Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type
Title: Message Title Stefan commented on PUP-6114 Re: Add support for Artifactory checksum headers to puppet agent and enable SHA1 checksum type I'd really like to see this implemented, is it still planned to get this merged? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1062) Add virtualenv support to the pip package provider
Title: Message Title Matthias Baur commented on PUP-1062 Re: Add virtualenv support to the pip package provider Jason Antman Any update on the legal issue? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6648) Puppet 4.6.x breaks catalog.apply in unit tests
Title: Message Title David Schmitt commented on PUP-6648 Re: Puppet 4.6.x breaks catalog.apply in unit tests Thanks Henrik, created https://github.com/rodjek/rspec-puppet/issues/472 to track upstream. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7336) Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4
Title: Message Title
Linus Lotz updated an issue
Puppet / PUP-7336
Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4
Change By:
Linus Lotz
Release Notes Summary:
This is a regression from 4.9.3, but it affects a feature that hasn't previously shipped with PE.In some very rare cases, a v5 hiera.yaml file can ignore certain hierarchy levels. This only happens for hierarchy levels that interpolate a top-scope variable _whose whose value was set with a after the _first_ Hiera lookup_ (like `$attributes = lookup ('attributes')`) . Even then, it only occurs if the variable is an array or hash, the hierarchy level accesses one of its members with key.subkey notation, _and_ the variable is referenced with the top-scope namespace (`::attributes.role`).If this affects you, you can remove the top-scope namespace (`attributes.role`) to work around it until this bug is fixed. However, we strongly recommend against making your hierarchy self-configuring like this. You should only interpolate the `$facts`, `$trusted`, and `$server_facts` variables in your hierarchy.(Dirty details: In the lookup that initially sets the offending variable, that variable doesn't exist yet. Hiera remembers that it doesn't exist, so in subsequent lookups it won't use the new value. This is part of an optimization for top-scope variables that don't change, which is why removing the top namespace works around it.)
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group
Jira (PUP-7336) Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4
Title: Message Title Henrik Lindberg commented on PUP-7336 Re: Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4 Linus Lotz Yes, the manner in which the global variable is set is not important - only that there was a lookup and interpolation of that variable prior to setting it. The interpolation must then also use a sub lookup in that variable (i.e. using 'dot notation') to trigger the problem fixed in this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-562) Regex Lookup isn't working with Puppet 4.9
Title: Message Title
Matthias Baur updated an issue
Hiera / HI-562
Regex Lookup isn't working with Puppet 4.9
Change By:
Matthias Baur
``` {code:java} root@mbaur-hieradebug:/etc/puppetlabs/code/environments/production# cat hiera.yamlversion: 5defaults: datadir: hieradata data_hash: yaml_datahierarchy: - name: "Per-node data (yaml version)"path: "nodes/%{trusted.certname}.yaml" # Add file extension.# Omitting datadir and data_hash to use defaults. - name: "Other YAML hierarchy levels"paths: # Can specify an array of paths instead of one. - "location/%{facts.whereami}/%{facts.group}.yaml" - "groups/%{facts.group}.yaml" - "os/%{facts.os.family}.yaml" - "common.yaml"root@mbaur-hieradebug:/etc/puppetlabs/code/environments/production# cat hieradata/common.yaml---classes: - foobarlookup_options: "^profile::(.*)::users$": # Regexp: `$users` parameter of any profile classmerge: # Merge behavior as a hash strategy: deep merge_hash_arrays: trueroot@mbaur-hieradebug:/etc/puppetlabs/code/environments/production# puppet lookup classesError: Could not run: undefined method `[]' for nil:NilClass ``` {code} The following things has been changed compared to an pure puppet-agent installation:- /etc/puppetlabs/puppet/hiera.yaml deleted- /etc/puppetlabs/code/environments/production/hiera.yaml created with code from https://docs.puppet.com/puppet/4.9/hiera_migrate_v3_yaml.html#translating-built-in-backends . Only the datadir was changed to hieradata- /etc/puppetlabs/code/environments/production/hieradata/common.yaml was created. For code see above.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (HI-562) Regex Lookup isn't working with Puppet 4.9
Title: Message Title
Matthias Baur created an issue
Hiera / HI-562
Regex Lookup isn't working with Puppet 4.9
Issue Type:
Bug
Affects Versions:
HI 3.3.1
Assignee:
Unassigned
Created:
2017/03/13 2:39 AM
Environment:
OS: Ubuntu 14.04.5 Puppet Agent: 1.9.3/4.9.4
Priority:
Normal
Reporter:
Matthias Baur
``` root@mbaur-hieradebug:/etc/puppetlabs/code/environments/production# cat hiera.yaml version: 5 defaults: datadir: hieradata data_hash: yaml_data hierarchy:
name: "Per-node data (yaml version)" path: "nodes/% {trusted.certname}
.yaml" # Add file extension.
Omitting datadir and data_hash to use defaults.
name: "Other YAML hierarchy levels" paths: # Can specify an array
Jira (PUP-7336) Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4
Title: Message Title Linus Lotz commented on PUP-7336 Re: Interpolation behavior in hiera.yaml changed between Puppet version 4.9.3 and 4.9.4 Thanks for the quick reply and fix! Just a remark on the release note summary: From what I understood the issue is triggered when a global variable is set after the first hiera lookup and the hierachy contains an interpolation using a array (or possibly hash) access to this variable. So it does not require the global variable to be set with hiera, the global variable just has to be set after the first lookup, right? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7271) performance regression in puppet 4.9
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7271 performance regression in puppet 4.9 Change By: Henrik Lindberg Fix Version/s: PUP 4.9.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title Nacho Barrientos commented on PUP-7302 Re: Puppet HTTP Node API: make fact_merge optional Hello? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
