Jira (PUP-7169) puppet 4.9.0 breaks hiera-eyaml
Title: Message Title Thomas Hallgren commented on PUP-7169 Re: puppet 4.9.0 breaks hiera-eyaml You are most likely looking at a different problem so please open a new ticket. Please provide a log containing a debug trace (from the server log), and if possible, an example that reproduces the problem. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master No, this all work fine with 1.8.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7169) puppet 4.9.0 breaks hiera-eyaml
Title: Message Title Angel L. Mateo commented on PUP-7169 Re: puppet 4.9.0 breaks hiera-eyaml I have tried puppet-agent 1.9.1 with puppet 4.9.2, but I'm still getting the error: $ sudo puppet lookup --debug --node mus30.um.es role cluster=mus hostgroup=mus --environment production Debug: Applying settings catalog for sections main, master, ssl, metrics Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) ... Debug: hiera(): [eyaml_backend]: Looking up role in eYAML backend Debug: hiera(): [eyaml_backend]: Looking for data source mus30.um.es Debug: hiera(): [eyaml_backend]: Looking for data source cluster_mus3 Debug: hiera(): Cannot find datafile /etc/puppetlabs/code/environments/production/hieradata/cluster_mus3.eyaml, skipping
Jira (PUP-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Thomas Mueller commented on PUP-5609 Re: Puppet apply doesn't protect shared files with a lock I'm using puppet apply in parallel to manage different nfs homedirectory roots with many users. Sounds like now agent_disabled_lockfile and agent_catalog_run_lockfile need to be set to achieve a parallel run. Might be good to have release notes about this. 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-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Michael Smith commented on PUP-5609 Re: Puppet apply doesn't protect shared files with a lock Thanks Erik Dalén! I'm going to assume we cleaned up some tests that were misbehaving and that's allowed the patch to go through. 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-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Michael Smith updated an issue Puppet / PUP-5609 Puppet apply doesn't protect shared files with a lock Change By: Michael Smith Release Notes Summary: Puppet apply now creates a lock file, as puppet agent does. This prevents simultaneously writing shared state files, as could happen if a puppet agent and puppet apply run occurred simultaneously. Release Notes: Bug Fix 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-6656) ensure => latest doesn't work with enablerepo install_options for package resource
Title: Message Title
Thomas Kishel commented on PUP-6656
Re: ensure => latest doesn't work with enablerepo install_options for package resource
I have another ZenDesk ticket, that reproduces the error: it appears to be new/specific to RHEL 7.
Swapping:
args.concat(enablerepo.map { |repo| ["--enablerepo=#{repo}"] }.flatten)
args.concat(disablerepo.map { |repo| ["--disablerepo=#{repo}"] }.flatten)
... in 'def self.check_updates' in https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L69 should resolve this error.
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-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Michael Smith updated an issue Puppet / PUP-5609 Puppet apply doesn't protect shared files with a lock Change By: Michael Smith Labels: maintenance 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-7201) Additional certificate attributes should be exposed in trusted hash
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7201 Additional certificate attributes should be exposed in trusted hash Change By: Adrien Thebo Labels: ssl 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-7214) PUP-6663 causes a regression of PUP-535
Title: Message Title Dylan Cochran updated an issue Puppet / PUP-7214 PUP-6663 causes a regression of PUP-535 Change By: Dylan Cochran Summary: PUP-6663 causes a regression of PUP- 533 535 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 Moses Mendoza commented on PUP-7144 Re: Review error string marking and externalization beginning review. I anticipate this effort can be parallelized so don't consider assignee indicative that an individual is responsible for this in its entirety 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 Moses Mendoza updated an issue Puppet / PUP-7144 Review error string marking and externalization Change By: Moses Mendoza Sprint: AP 2017- 03 02 - 08 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-7144) Review error string marking and externalization
Title: Message Title Moses Mendoza assigned an issue to Moses Mendoza Puppet / PUP-7144 Review error string marking and externalization Change By: Moses Mendoza Assignee: Moses Mendoza 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza commented on PUP-7021 Re: Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module given this ticket now encompasses a generic effort for string conversion to UTF-8, raising priority to major since thss will possibly be instrumental in later i18n effort 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Moses Mendoza Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza commented on PUP-7021 Re: Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module There are three PRs up for this work now, that should probably be reviewed in this order: (1) https://github.com/puppetlabs/puppet/pull/5633 establishes a baseline 'convert string to utf-8' heuristic (2) https://github.com/puppetlabs/puppet/pull/5634 creates a wrapper around ruby's Etc module that uses (1) to return UTF-8 structs (3) https://github.com/puppetlabs/puppet/pull/5635 updates the nameservice provider to leverage (2) above 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-7159) CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures
Title: Message Title Geoff Nichols assigned an issue to Unassigned Puppet / PUP-7159 CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures Change By: Geoff Nichols 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-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Michael Smith updated an issue Puppet / PUP-5609 Puppet apply doesn't protect shared files with a lock Change By: Michael Smith Fix Version/s: PUP 5.0.0 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-7214) PUP-6663 causes a regression of PUP-533
Title: Message Title
Dylan Cochran updated an issue
Puppet / PUP-7214
PUP-6663 causes a regression of PUP-533
Change By:
Dylan Cochran
As exemplified in the output of the two beaker runs here: [https://gitlab.com/simp/pupmod-simp-rsync/pipelines/6452666], one with agent 1.7.1 and one with agent 1.9.1, when attempting to execute the following manifest:{noformat}package { 'rsyslog.x86_64': ensure => absent, provider => rpm }{noformat} when you attempt to run on a rhel7 vm: {noformat}Error: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Error: /Stage[main]/Rsyslog::Install/Package[rsyslog.x86_64]/ensure: change from 5.8.10-10.el6_6 to absent failed: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Notice: /Stage[main]/Rsyslog::Install/Package[rsyslog7.x86_64]: Dependency Package[rsyslog.x86_64] has failures: true{noformat}when running a debugging session, I can confirm the error is during the self.class.nevra_to_hash(output) on line 124:{noformat}[2] pry(#)> output=> "'rsyslog 0 7.4.7 16.el7 x86_64\n'"[3] pry(#)> self.class.nevra_to_hash(output)=> {:name=>"'rsyslog", :epoch=>"0", :version=>"7.4.7", :release=>"16.el7", :arch=>"x86_64", :provider=>:yum, :ensure=>"7.4.7-16.el7"}[4] pry(#)>{noformat} Note This seems to have been introduced in PUP-6663 where single quotes were added around the erroneous newline as well version . I'm working on a patch.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7214) PUP-6663 causes a regression of PUP-533
Title: Message Title Dylan Cochran commented on PUP-7214 Re: PUP-6663 causes a regression of PUP-533 PR submitted at: https://github.com/puppetlabs/puppet/pull/5639 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-7214) PUP-6663 causes a regression of PUP-533
Title: Message Title
Dylan Cochran updated an issue
Puppet / PUP-7214
PUP-6663 causes a regression of PUP-533
Change By:
Dylan Cochran
As exemplified in the output of the [ two beaker runs ](https://gitlab.com/simp/pupmod-simp-rsync/pipelines/6452666) , one with agent 1.7.1 and one with agent 1.9.1, when attempting to execute the following manifest:{noformat}package { 'rsyslog.x86_64': ensure => absent, provider => rpm }{noformat}{noformat}Error: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Error: /Stage[main]/Rsyslog::Install/Package[rsyslog.x86_64]/ensure: change from 5.8.10-10.el6_6 to absent failed: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Notice: /Stage[main]/Rsyslog::Install/Package[rsyslog7.x86_64]: Dependency Package[rsyslog.x86_64] has failures: true{noformat}when running a debugging session, I can confirm the error is during the self.class.nevra_to_hash(output) on line 124:{noformat}[2] pry(#)> output=> "'rsyslog 0 7.4.7 16.el7 x86_64\n'"[3] pry(#)> self.class.nevra_to_hash(output)=> {:name=>"'rsyslog", :epoch=>"0", :version=>"7.4.7", :release=>"16.el7", :arch=>"x86_64", :provider=>:yum, :ensure=>"7.4.7-16.el7"}[4] pry(#)>{noformat}Note the erroneous newline as well. I'm working on a patch.
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"
Jira (PUP-7214) PUP-6663 causes a regression of PUP-533
Title: Message Title
Dylan Cochran updated an issue
Puppet / PUP-7214
PUP-6663 causes a regression of PUP-533
Change By:
Dylan Cochran
As exemplified in the output of the two beaker run runs here: [https://gitlab.com/simp/pupmod-simp-rsync/pipelines/6452666], one with agent 1.7.1 and one with agent 1.9.1, when attempting to execute the following manifest:{noformat}package { 'rsyslog.x86_64': ensure => absent, provider => rpm }{noformat}{noformat}Error: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Error: /Stage[main]/Rsyslog::Install/Package[rsyslog.x86_64]/ensure: change from 5.8.10-10.el6_6 to absent failed: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Notice: /Stage[main]/Rsyslog::Install/Package[rsyslog7.x86_64]: Dependency Package[rsyslog.x86_64] has failures: true{noformat}when running a debugging session, I can confirm the error is during the self.class.nevra_to_hash(output) on line 124:{noformat}[2] pry(#)> output=> "'rsyslog 0 7.4.7 16.el7 x86_64\n'"[3] pry(#)> self.class.nevra_to_hash(output)=> {:name=>"'rsyslog", :epoch=>"0", :version=>"7.4.7", :release=>"16.el7", :arch=>"x86_64", :provider=>:yum, :ensure=>"7.4.7-16.el7"}[4] pry(#)>{noformat}Note the erroneous newline as well. I'm working on a patch.
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
Jira (PUP-7214) PUP-6663 causes a regression of PUP-533
Title: Message Title
Dylan Cochran updated an issue
Puppet / PUP-7214
PUP-6663 causes a regression of PUP-533
Change By:
Dylan Cochran
As exemplified in the output of the [ two beaker runs]( run [ https://gitlab.com/simp/pupmod-simp-rsync/pipelines/6452666 ) ] , one with agent 1.7.1 and one with agent 1.9.1, when attempting to execute the following manifest:{noformat}package { 'rsyslog.x86_64': ensure => absent, provider => rpm }{noformat}{noformat}Error: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Error: /Stage[main]/Rsyslog::Install/Package[rsyslog.x86_64]/ensure: change from 5.8.10-10.el6_6 to absent failed: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Notice: /Stage[main]/Rsyslog::Install/Package[rsyslog7.x86_64]: Dependency Package[rsyslog.x86_64] has failures: true{noformat}when running a debugging session, I can confirm the error is during the self.class.nevra_to_hash(output) on line 124:{noformat}[2] pry(#)> output=> "'rsyslog 0 7.4.7 16.el7 x86_64\n'"[3] pry(#)> self.class.nevra_to_hash(output)=> {:name=>"'rsyslog", :epoch=>"0", :version=>"7.4.7", :release=>"16.el7", :arch=>"x86_64", :provider=>:yum, :ensure=>"7.4.7-16.el7"}[4] pry(#)>{noformat}Note the erroneous newline as well. I'm working on a patch.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups
Jira (PUP-7214) PUP-6663 causes a regression of PUP-533
Title: Message Title
Dylan Cochran updated an issue
Puppet / PUP-7214
PUP-6663 causes a regression of PUP-533
Change By:
Dylan Cochran
As exemplified in the output of the two beaker runs, one with agent 1.7.1 and one with agent 1.9.1, when attempting to execute the following manifest:{ { noformat} package { 'rsyslog.x86_64': ensure => absent, provider => rpm } {noformat } } { { noformat} Error: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Error: /Stage[main]/Rsyslog::Install/Package[rsyslog.x86_64]/ensure: change from 5.8.10-10.el6_6 to absent failed: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Notice: /Stage[main]/Rsyslog::Install/Package[rsyslog7.x86_64]: Dependency Package[rsyslog.x86_64] has failures: true {noformat } } when running a debugging session, I can confirm the error is during the self.class.nevra_to_hash(output) on line 124:{ { noformat} [2] pry(#)> output=> "'rsyslog 0 7.4.7 16.el7 x86_64\n'"[3] pry(#)> self.class.nevra_to_hash(output)=> {:name=>"'rsyslog", :epoch=>"0", :version=>"7.4.7", :release=>"16.el7", :arch=>"x86_64", :provider=>:yum, :ensure=>"7.4.7-16.el7"}[4] pry(#)> {noformat } } Note the erroneous newline as well. I'm working on a patch.
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-7214) PUP-6663 causes a regression of PUP-533
Title: Message Title
Dylan Cochran created an issue
Puppet / PUP-7214
PUP-6663 causes a regression of PUP-533
Issue Type:
Bug
Affects Versions:
PUP 4.9.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2017/02/13 10:25 AM
Environment:
Beaker puppet-agent 1.9.1
Priority:
Normal
Reporter:
Dylan Cochran
As exemplified in the output of the two beaker runs, one with agent 1.7.1 and one with agent 1.9.1, when attempting to execute the following manifest:
{{package { 'rsyslog.x86_64': ensure => absent, provider => rpm }
}}
{{ Error: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error: package 'rsyslog-5.8.10-10.el6_6.x86_64 is not installed Error: /Stage[main]/Rsyslog::Install/Package[rsyslog.x86_64]/ensure: change from 5.8.10-10.el6_6 to absent failed: Execution of '/bin/rpm -e --nodeps 'rsyslog-5.8.10-10.el6_6.x86_64' returned 1: error:
Jira (PUP-7211) puppet ssh_authorized_key not purged as expected
Title: Message Title Michael Smith updated an issue Puppet / PUP-7211 puppet ssh_authorized_key not purged as expected Change By: Michael Smith Sprint: Puppet Triage 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-7202) excessive INFO logging when files arent found
Title: Message Title Michael Smith commented on PUP-7202 Re: excessive INFO logging when files arent found This is probably https://github.com/puppetlabs/puppet/blob/4.9.2/lib/puppet/network/http/api/indirected_routes.rb#L122. Yay indirector. Fixing this isn't as straight-forward as I'd like. It would probably need an addition to the indirector that allows for a call to fail silently. It's the metadata call, so probably https://github.com/puppetlabs/puppet/blob/4.9.2/lib/puppet/type/file/source.rb#L188 triggers it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6067) Pip3 provider does not include features from Pip
Title: Message Title Michael Smith commented on PUP-6067 Re: Pip3 provider does not include features from Pip Chris Denneen can you share the profile code triggering that? (amazon.pp:7, apparently) The note about xmlrpc/client seems out of place, as that's not present in Puppet itself. Also, you may get more responsive help on the Slack channel or IRC #puppet-dev. See https://puppet.com/community for how to access any of those. 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-1571) Add "is_virtual" fact for AIX
Title: Message Title Moses Mendoza commented on FACT-1571 Re: Add "is_virtual" fact for AIX Tim Purkerson in what scenarios would this fact return true vs false? 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-7201) Additional certificate attributes should be exposed in trusted hash
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7201 Additional certificate attributes should be exposed in trusted hash Change By: Moses Mendoza Team: Agent & Platform 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-1571) Add "is_virtual" fact for AIX
Title: Message Title Moses Mendoza updated an issue Facter / FACT-1571 Add "is_virtual" fact for AIX Change By: Moses Mendoza Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1571) Add "is_virtual" fact for AIX
Title: Message Title Moses Mendoza updated an issue Facter / FACT-1571 Add "is_virtual" fact for AIX Change By: Moses Mendoza Team: Agent & Platform 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-1571) Add "is_virtual" fact for AIX
Title: Message Title Moses Mendoza moved an issue Facter / FACT-1571 Add "is_virtual" fact for AIX Change By: Moses Mendoza Key: PUP FACT - 7200 1571 Project: Puppet Facter 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-7201) Additional certificate attributes should be exposed in trusted hash
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7201 Additional certificate attributes should be exposed in trusted hash Change By: Moses Mendoza Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7201) Additional certificate attributes should be exposed in trusted hash
Title: Message Title Moses Mendoza commented on PUP-7201 Re: Additional certificate attributes should be exposed in trusted hash ping Adrien Thebo, just for awareness 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-7202) excessive INFO logging when files arent found
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7202 excessive INFO logging when files arent found Change By: Moses Mendoza Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7202) excessive INFO logging when files arent found
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7202 excessive INFO logging when files arent found Change By: Moses Mendoza Team: Agent & Platform 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-7151) selmodule type should explicitly specify encoding when reading selmodversion_file
Title: Message Title Moses Mendoza commented on PUP-7151 Re: selmodule type should explicitly specify encoding when reading selmodversion_file merged to master at https://github.com/puppetlabs/puppet/commit/7aa53c5c7f4e48e0c9b23220d7d4e960e81a2d59 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-7151) selmodule type should explicitly specify encoding when reading selmodversion_file
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7151 selmodule type should explicitly specify encoding when reading selmodversion_file Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 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-7151) selmodule type should explicitly specify encoding when reading selmodversion_file
Title: Message Title Geoff Nichols assigned an issue to Moses Mendoza Puppet / PUP-7151 selmodule type should explicitly specify encoding when reading selmodversion_file Change By: Geoff Nichols Assignee: Moses Mendoza 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Henrik Lindberg commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master ok, so, that looks like the $data fed to create_resources either contains two entries that are the same (which IIRC is not even possible), or you have some other location that also creates the same resource - guessing some kind of title where something interpolated is missing. 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Geoff Nichols assigned an issue to Moses Mendoza Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Geoff Nichols Assignee: Moses Mendoza 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Sorry, that I have been to harsh, servers are fixed now and regular operation is verified. Now I have time to elaborate. - These is the message (retrieved from puppedb): some_module::Chroot[name_a] is already declared in file modules/some_module/manifests/conf.pp:103 cannot redeclare at modules/some_module/manifests/conf.pp:103 at modules/some_module/manifests/conf.pp:103:7 at modules/some_module/manifests/virtual.pp:5 on node some_node Which is: modules/some_module/manifests/conf.pp:103:7
Jira (PUP-7213) support to_yaml in epp
Title: Message Title Henrik Lindberg commented on PUP-7213 Re: support to_yaml in epp This has nothing to do with EPP specifically. You need a function that produces yaml given a hash. There is no such function in puppet, but there may be one in stdlib. If not there someone else must have written that function already. Your EPP code is also not correct as the logic is Puppet Language, you need to use $ in front of variable names. 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Henrik Lindberg commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Now you seem to fail on Error while evaluating a Resource Statement, Duplicate declaration:, which is probably caused by something going wrong before that. As I said earlier, it looks like you need help to figure out what is wrong. We cannot do that without something that reproduces the problem. You said But I cannot tell if this is the solution (I'm pretty sure it is not) due to a new syntax error regarding function create_resources which has been used to ensure deep in a packet that a resource is defined. It changed behavior and now it gives an error: you say you get a syntax error - what is that syntax error (the "duplicate declaration" is not a syntax error, but was it that error you were referring to) ? How is create_resource "used to ensure deep in a packet that a resource is defined" - I don't understand what you mean there. I think you are saying that your call to create_resource in one specific place does not give you the expected result. You need to check what you are feeding into that call, and then trace that backwards to where the input to that call comes from. Ultimately there is probably a call to hiera that is not producing the expected value. Then that needs to be picked apart until the actual thing that goes wrong is found (be it a bug in puppet, or something you need to change). 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-6812) Force --disable flag comment
Title: Message Title Geoff Nichols assigned an issue to Unassigned Puppet / PUP-6812 Force --disable flag comment Change By: Geoff Nichols Assignee: Geoff Nichols 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-6812) Force --disable flag comment
Title: Message Title Geoff Nichols commented on PUP-6812 Re: Force --disable flag comment Gary Camblin, thank you for submitting this feature request. Since this change would affect all users of the --disable feature to address an issue that may be specific to a single organization, we have decided not to implement this change at this time. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master OK, I didn't expected that a Debian package isn't configured to apt-get install does all required steps. So I terminated puppetserver process and started it again. (but when stepping back, puppetserver is restarted by apt-get, why this?) But I cannot tell if this is the solution (I'm pretty sure it is not) due to a new syntax error regarding function create_resources which has been used to ensure deep in a packet that a resource is defined. It changed behavior and now it gives an error: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: and more serious, it breaks now some more important services. Thus I cannot check anything any further but have to switch back immediately! To me puppet agent 1.9 is completely broken and I will not use it any more. I strongly recommend to tag puppet-agent to version 1.8.3-1 on puppet master. BTW: Consulting the doku: https://docs.puppet.com/hiera/3.2/configuring.html :deep_merge_options
Jira (PUP-7213) support to_yaml in epp
Title: Message Title
Christoph Maser created an issue
Puppet / PUP-7213
support to_yaml in epp
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2017/02/13 5:38 AM
Priority:
Normal
Reporter:
Christoph Maser
Whey trying to use Hash.to_yaml in epp
$ cat test.pp
$var = { 'key' => 'val' }
file {'/tmp/foo':
Jira (PUP-7195) on huawei: puppet lookup / hiera fails with key that contains utf-8 characters
Title: Message Title Henrik Lindberg commented on PUP-7195 Re: on huawei: puppet lookup / hiera fails with key that contains utf-8 characters Irrespective of LC settings, puppet should enforce UTF-8. While setting the correct LC values would make it work, it would only mask the underlying problem of not enforcing UTF-8. 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Henrik Lindberg commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Andreas Papst Thanks for the update. Have to ask, since it is a common mistake - did you restart the server after the upgrade? Not doing so leads to strange problems (and they appear to be different for everyone). I don't see anything immediately suspicious except possibly the use of ':' before only one of the keys for the merge options. (Ping Thomas Hallgren any thoughts?) I think you may need to hop on to slack or irc and get interactive help with pinpointing what is going wrong. What is given in the description does not make it possible to reproduce the 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-7212) Implement Pcore Object annotation pattern
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-7212
Implement Pcore Object annotation pattern
Change By:
Thomas Hallgren
Implement what's needed to enable use of adapters annotations on the adaptable annotatable parts of the Pcore {{Object}} and {{TypeSet}} types.
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 updated an issue Puppet / PUP-7212 Implement Pcore Object annotation pattern Change By: Thomas Hallgren Summary: Implement Pcore Object adapter annotation pattern 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Change By: Thomas Hallgren 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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x Change By: Thomas Hallgren Sprint: PDE 2017-02-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-7205) Backport Hiera 5 eyaml support to Puppet 4.9.x
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7205 Backport Hiera 5 eyaml support to Puppet 4.9.x 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-7212) Implement Pcore Object adapter pattern
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7212 Implement Pcore Object adapter pattern Issue Type: Improvement Assignee: Thomas Hallgren Created: 2017/02/13 12:33 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Thomas Hallgren Implement what's needed to enable use of adapters on the adaptable parts of the Pcore Object and TypeSet types. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7195) on huawei: puppet lookup / hiera fails with key that contains utf-8 characters
Title: Message Title Thomas Hallgren commented on PUP-7195 Re: on huawei: puppet lookup / hiera fails with key that contains utf-8 characters It could also be that LC_ALL or LC_LANG (or some other locale related environment variable) is incorrectly set as the message: WARN puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C seems to indicate. 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-7195) on huawei: puppet lookup / hiera fails with key that contains utf-8 characters
Title: Message Title Thomas Hallgren commented on PUP-7195 Re: on huawei: puppet lookup / hiera fails with key that contains utf-8 characters An LC_xxx setting will override any xxx locale setting and LC_ALL will, not surprisingly, override them all. My guess is that LC_ALL is set to 'C' in the described example and that it then overrides any setting of LANG. I tested the given key with puppet apply and it works OK. If I set LC_ALL=C it always fails. Sean Griffin, can you verify that LC_ALL is set to C? It should be either unset or set to en_US.UTF-8. 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-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Andreas Papst commented on PUP-7199 Re: Update to puppet-agent 1.9.0-1jessie breaks puppet master Hello, thank you for this update, but installing puppet-agent=1.9.1-1jessie doesn't solve my problem, puppet master is still broken to me. Also is still an issue! Thus I switch back to 1.8.3-1 again. Cheers Andreas 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.
