Jira (PUP-6165) it should not be possible to disable manifest ordering
Title: Message Title Christopher Wood commented on PUP-6165 Re: it should not be possible to disable manifest ordering As a post-hoc note, I do in fact have random ordering turned on. It is indeed an excellent fuzzer. However I think everybody at work here except for me will be delighted with this change. [root@puppetmaster1 ~]# grep ^order /etc/puppetlabs/puppet/puppet.conf ordering = random Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8224) puppet certificate find ignores requested cert name
Title: Message Title Christopher Wood commented on PUP-8224 Re: puppet certificate find ignores requested cert name Sweet, thank you! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8559) puppet-agent : Datatypes not loaded when using dependencies
Title: Message Title Christopher Wood commented on PUP-8559 Re: puppet-agent : Datatypes not loaded when using dependencies Linking PUP-6964, dependencies fix things in 5.4.0 for types as well as functions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title Christopher Wood commented on PUP-6518 Re: puppet resource package kernel reports the wrong rpm version I think if you want a report of all installed package versions, you're probably better off with a fact which does "rpm -qa" under the hood. (Or Puppet Discovery, these days?) Trying to ponder why some rpms get to have multiple base names is the path to insanity. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Christopher Wood commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency I found this ticket after running face-first into this issue yesterday. A component of the behaviour in puppet 5.4.0 is that when I copied the function-using code from a component module class into a profile module class, puppet was then able to find my function. Of course the control repo lacks a metadata.json, and now that I've added my module dependency everything works, so not chasing too hard on whether function lookup works for component modules without metadata.json. (Also interested in whether the eventual error message will provide a list of places searched for functions, as that would have shed some light at my level of puppet skill.) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2310) Puppet client does not update and does consult the crl during authentication
Title: Message Title Christopher Wood commented on PUP-2310 Re: Puppet client does not update and does consult the crl during authentication Noting these while I'm looking at my internal CRL ticket again: https://ask.puppet.com/question/3843/multiple-puppet-masters-with-single-ca-server/ https://gist.github.com/derektamsen/f986216ed10bdc66e650 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3812) puppetdb low catalog duplication page 404s
Title: Message Title Christopher Wood commented on PDB-3812 Re: puppetdb low catalog duplication page 404s It was quite a useful page, was there a substitute somewhere else in the puppetdb docs? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3263) Architecture Parameter for Package Resource
Title: Message Title
Christopher Wood commented on PUP-3263
Re: Architecture Parameter for Package Resource
I think this is the most pertinent ticket to add a CentOS oddity a colleague just found. I'm reproducing it here with the bash package but it's the same for our internal package.
It turns out that this does not produce a duplicate resource compilation failure:
package { 'bash.x86_64': ensure => latest }
package { 'bash': ensure => present }
For whatever reason, bash.x86_64 ends up being the package examined.
Info: Applying configuration version '1516217268'
Debug: Prefetching yum resources for package
Debug: Executing: '/bin/rpm --version'
Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''
Debug: Executing: '/bin/rpm -q bash.x86_64 --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''
Jira (PUP-8224) puppet certificate find ignores requested cert name
Title: Message Title Christopher Wood commented on PUP-8224 Re: puppet certificate find ignores requested cert name [cwood@myhost ~]$ rm -rf $HOME/.puppetlabs [cwood@myhost ~]$ puppet certificate generate --ca-location remote --ca_server puppetmaster2.mydomain.com cwood123 true [cwood@myhost ~]$ find $HOME/.puppetlabs -type f | sort /home/cwood/.puppetlabs/etc/puppet/ssl/certificate_requests/cwood123.pem /home/cwood/.puppetlabs/etc/puppet/ssl/private_keys/cwood123.pem /home/cwood/.puppetlabs/etc/puppet/ssl/public_keys/cwood123.pem
Jira (PUP-8224) puppet certificate find ignores requested cert name
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-8224
puppet certificate find ignores requested cert name
Change By:
Christopher Wood
Environment:
{{[cwood@myhost ~]$ facter os.name CentOS [cwood@myhost ~]$ facter os.release.full 6.9 [cwood@myhost ~]$ , puppet --version 5.3.3 }}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-8224) puppet certificate find ignores requested cert name
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-8224
puppet certificate find ignores requested cert name
Issue Type:
Bug
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Created:
2017/12/04 11:04 AM
Environment:
{{[cwood@myhost ~]$ facter os.name CentOS [cwood@myhost ~]$ facter os.release.full 6.9 [cwood@myhost ~]$ puppet --version 5.3.3 }}
Priority:
Normal
Reporter:
Christopher Wood
Using these commands, "puppet certificate find" actually appears to be trying to retrieve the fqdn certificate. The generate works as expected and the cert cn=cwood123 is available for signing at the puppet CA.
puppet certificate generate --ca-location remote --ca_server puppetmaster2.mydomain.com cwood123
puppet certificate find --ca-location remote --ca_server puppetmaster2.mydomain.com cwood123
With --debug output on the second command, I see the following right before the "does not match the agent's private key" error which seems odd.
Debug: Finishing transaction 19331580 Info: Creating a new SSL key for myhost.mydomain.com Debug: Using cached certificate for ca Debug: Creating new connection for https://puppetmaster2.mydomain.com:8140 Info: Caching
Jira (PUP-7968) group resource doesn't default to ensure=>present
Title: Message Title Christopher Wood commented on PUP-7968 Re: group resource doesn't default to ensure=>present My thinking was that for this group the numerical GID was not an issue, and like a package or file resource it would default to existing on the system. 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-7968) group resource doesn't default to ensure=>present
Title: Message Title Christopher Wood created an issue Puppet / PUP-7968 group resource doesn't default to ensure=>present Issue Type: Bug Affects Versions: PUP 5.2.0, PUP 4.10.1 Assignee: Unassigned Components: Types and Providers Created: 2017/09/20 1:23 PM Environment: [root@puppetmaster7 ~]# puppet --version 5.2.0 [root@puppetmaster7 ~]# cat /etc/redhat-release CentOS Linux release 7.4.1708 (Core) [root@puppetmaster7 ~]# uname -a Linux puppetmaster7 3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12 22:26:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Priority: Minor Reporter: Christopher Wood group
Jira (PUP-7527) Insufficient error message when erroneously passing a Collection containing non-Data values for a Data parameter
Title: Message Title
Christopher Wood commented on PUP-7527
Re: Insufficient error message when erroneously passing a Collection containing non-Data values for a Data parameter
I ran into a bit of the same thing trying to send around file resource defaults via class parameter.
https://docs.puppet.com/puppet/latest/lang_resources_advanced.html#setting-attributes-from-a-hash $file = { 'group' => 'groupname', 'mode' => '0640', 'notify' => Service[$service], 'owner' => 'root', 'require' => Package[$package], }
class { '::myclass::backend': file => $file, toggle => true, }
Part of the "Error while evaluating a Resource Statement":
parameter 'file' entry 'notify' expects a Data value, got Type
parameter 'file' entry 'require' expects a Data value, got Tuple
And the line/character is the start of the resource-style class declaration.
Add Comment
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title Christopher Wood commented on PUP-7798 Re: trouble upgrading java-1.8.0-openjdk rpm I confirm I don't see this behaviour with 71e94e3 and java-1.8.0-openjdk upgrades as expected. I completely missed PUP-7145 , thank you. For people at my level of experience following along: https://docs.puppet.com/puppetserver/latest/dev_running_from_source.html https://github.com/puppetlabs/puppet Rough notes from history: git clone https://github.com/puppetlabs/puppet cd puppet/ yum -y install make gcc g++ rpm-build /opt/puppetlabs/puppet/bin/gem install bundler /opt/puppetlabs/puppet/bin/bundle install --path .bundle/gems /opt/puppetlabs/puppet/bin/bundle exec puppet agent --test --server puppet-pm.me.com yum -y downgrade java-1.8.0-openjdk java-1.8.0-openjdk-headless /opt/puppetlabs/puppet/bin/bundle exec puppet agent --test --server puppet-pm.me.com Add Comment
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood commented on PUP-7798
Re: trouble upgrading java-1.8.0-openjdk rpm
I apologize for the bad issue formatting, apparently JIRA and I are not on speaking terms today.
[root@puppetmaster7 ~]# /bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' | egrep '^(java|bash)' | sort | column -t
bash 0 4.1.2 48.el6 x86_64
java-1.8.0-openjdk 1 1.8.0.131 0.b11.el6_9 x86_64
java-1.8.0-openjdk-headless 1 1.8.0.131 0.b11.el6_9 x86_64
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
Environment:
{ noformat code:bash }[root@puppetmaster7 ~]# uname -r 2.6.32-696.1.1.el6.x86_64 [root@puppetmaster7 ~]# cat /etc/redhat-release CentOS release 6.9 (Final) [root@puppetmaster7 ~]# rpm -q puppet-agent puppet-agent-1.10.1-1.el6.x86_64 { noformat code }
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-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)'bash-4.1.2-48.el6.x86_64java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}Then I downgrade them:{{yum -y downgrade bash java-1.8.0-openjdk java-1.8.0-openjdk-headless}}{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-15.el6_5.2.x86_64java-1.8.0-openjdk-1.8.0.131-0.b11.el6_9.x86_64java-1.8.0-openjdk-headless-1.8.0.131-0.b11.el6_9.x86_64}}Now when I have a bash-updating package resource, I see bash-upgrading lines in the debug output.puppet apply --debug /tmp/b.pp | tee /tmp/bb{{[root@puppetmaster7 ~]# cat /tmp/b.pp package { 'bash': ensure => latest,}[root@puppetmaster7 ~]# grep bash /tmp/bbDebug: Facter: root:x:0:0:root:/root:/bin/bash "bash;4.1.2;15.el6_5.2",Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Debug: Package[bash](provider=yum): Ensuring => latestDebug: Executing: '/bin/rpm -q bash --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Package[bash](provider=yum): Ensuring latest, so using updateDebug: Executing: '/usr/bin/yum -d 0 -e 0 -y update bash'Debug: /Stage[main]/Main/Package[bash]/ensure: bash "4.1.2-15.el6_5.2" is installed, latest is "0:4.1.2-48.el6"Notice: /Stage[main]/Main/Package[bash]/ensure: ensure changed '4.1.2-15.el6_5.2' to '0:4.1.2-48.el6'Debug: /Stage[main]/Main/Package[bash]: The container Class[Main] will propagate my refresh event}}However when I try the same thing with the java rpm, I do not see the same output.puppet apply --debug /tmp/h.pp | tee /tmp/yy{{[root@puppetmaster7 ~]# cat /tmp/h.pp package { 'java-1.8.0-openjdk': ensure => latest,}[root@puppetmaster7 ~]# grep java /tmp/yyDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_patch_level.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_libjvm_path.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_version.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_default_home.rbDebug: Loading facts from /etc/puppetlabs/code/environments/common_common/modules/java/lib/facter/java_major_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_patch_level.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_libjvm_path.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_version.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_default_home.rbDebug: Loading facts from /opt/puppetlabs/puppet/cache/lib/facter/java_major_version.rbDebug: Facter: searching for operatingsystem.rb in
Jira (PUP-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
Environment:
{noformat}[root@puppetmaster7 ~]# uname -r 2.6.32-696.1.1.el6.x86_64 [root@puppetmaster7 ~]# cat /etc/redhat-release CentOS release 6.9 (Final) [root@puppetmaster7 ~]# rpm -q puppet-agent puppet-agent-1.10.1-1.el6.x86_64 {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-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
Environment:
{ { noformat} [root@puppetmaster7 ~]# uname -r2.6.32-696.1.1.el6.x86_64[root@puppetmaster7 ~]# cat /etc/redhat-release CentOS release 6.9 (Final)[root@puppetmaster7 ~]# rpm -q puppet-agentpuppet-agent-1.10.1-1.el6.x86_64 {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-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Change By:
Christopher Wood
Environment:
{{ [root@puppetmaster7 ~]# uname -r2.6.32-696.1.1.el6.x86_64 [root@puppetmaster7 ~]# cat /etc/redhat-release CentOS release 6.9 (Final) [root@puppetmaster7 ~]# rpm -q puppet-agentpuppet-agent-1.10.1-1.el6.x86_64 }}
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-7798) trouble upgrading java-1.8.0-openjdk rpm
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-7798
trouble upgrading java-1.8.0-openjdk rpm
Issue Type:
Bug
Affects Versions:
PUP 4.10.1
Assignee:
Unassigned
Components:
Types and Providers
Created:
2017/07/21 3:31 PM
Environment:
[root@puppetmaster7 ~]# uname -r 2.6.32-696.1.1.el6.x86_64 [root@puppetmaster7 ~]# cat /etc/redhat-release CentOS release 6.9 (Final) [root@puppetmaster7 ~]# rpm -q puppet-agent puppet-agent-1.10.1-1.el6.x86_64
Priority:
Normal
Reporter:
Christopher Wood
To reproduce, I start out on a CentOS system and run "yum -y update". This installs the following (using bash as a baseline comparison here since it's ubiquitous):
{{[root@puppetmaster7 ~]# rpm -qa | egrep '^(bash|java)' bash-4.1.2-48.el6.x86_64 java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64 java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64}}
Then I downgrade them:
yum -y
Jira (PUP-7735) Regexp class parameter being understood as a String
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7735
Regexp class parameter being understood as a String
Change By:
Christopher Wood
When we pass a Regexp to a class, the class understands it as a String. To wit:{{class what ( Regexp[/^.$/] $param,) { notice('yes')} class { 'what': param => /^.$/,}$ puppet apply /tmp/z.pp Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Classname]: parameter 'param' expects a Regexp value, got String at /tmp/z.pp:7:1 on node cwl.hostopia.com}}https://pastebin.com/bHJ1vqub{{$regexp = /^.$/notice(type($regexp))class foo($bar) { notice(type($bar))}class { 'foo': bar => $regexp }Notice: Scope(Class[main]): Regexp[/^.$/]Notice: Scope(Class[Foo]): String}}https://gist.github.com/richardc/1380cda39d7bebca19ddc9dc06fb1a16Functions seem better though. {{ function x(Regexp $thing) { notice(type($thing)) } happily works }}
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-7735) Regexp class parameter being understood as a String
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7735
Regexp class parameter being understood as a String
Change By:
Christopher Wood
When we pass a Regexp to a class, the class understands it as a String. To wit:{{class what ( Regexp[/^.$/] $param,) { notice('yes')} class { 'what': param => /^.$/,}$ puppet apply /tmp/z.pp Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Classname]: parameter 'param' expects a Regexp value, got String at /tmp/z.pp:7:1 on node cwl.hostopia.com}}https://pastebin.com/bHJ1vqub{{$regexp = /^.$/notice(type($regexp))class foo($bar) { notice(type($bar))}class { 'foo': bar => $regexp }Notice: Scope(Class[main]): Regexp[/^.$/]Notice: Scope(Class[Foo]): String}}https://gist.github.com/richardc/1380cda39d7bebca19ddc9dc06fb1a16Functions seem better though.{ quote} { function x(Regexp $thing) { notice(type($thing)) } happily works {quote } }
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-7735) Regexp class parameter being understood as a String
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-7735
Regexp class parameter being understood as a String
Change By:
Christopher Wood
When we pass a Regexp to a class, the class understands it as a String. To wit:{{ class what ( Regexp[/^.$/] $param,) { notice('yes')} class { 'what': param => /^.$/,}$ puppet apply /tmp/z.pp Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Classname]: parameter 'param' expects a Regexp value, got String at /tmp/z.pp:7:1 on node cwl.hostopia.com }} https://pastebin.com/bHJ1vqub {{ $regexp = /^.$/notice(type($regexp))class foo($bar) { notice(type($bar))}class { 'foo': bar => $regexp }Notice: Scope(Class[main]): Regexp[/^.$/]Notice: Scope(Class[Foo]): String }} https://gist.github.com/richardc/1380cda39d7bebca19ddc9dc06fb1a16Functions seem better though.{ { quote} function x(Regexp $thing) { notice(type($thing)) } happily works {quote } }
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-7735) Regexp class parameter being understood as a String
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-7735
Regexp class parameter being understood as a String
Issue Type:
Bug
Affects Versions:
PUP 4.10.2
Assignee:
Unassigned
Components:
Language, Type System
Created:
2017/06/27 9:28 AM
Environment:
$ puppet --version 4.10.2
$ uname -a Linux cwl 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux
(Probably a bit different for other people in the #puppet discussion.)
Priority:
Normal
Reporter:
Christopher Wood
When we pass a Regexp to a class, the class understands it as a String. To wit:
{{ class what ( Regexp[/^.$/] $param, ) { notice('yes') }
class { 'what': param => /^.$/, }
$ puppet apply /tmp/z.pp Error: Evaluation Error: Error while evaluating a Resource Statement, Class[Classname]: parameter
Jira (PUP-7734) puppet.conf bad environment setting breaks ENC correct environment setting
Title: Message Title Christopher Wood created an issue Puppet / PUP-7734 puppet.conf bad environment setting breaks ENC correct environment setting Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/06/27 8:34 AM Environment: cat /etc/redhat-release CentOS release 6.9 (Final) # uname -a Linux mail10c7 2.6.32-696.3.2.el6.x86_64 #1 SMP Tue Jun 20 01:26:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux rpm -q puppet-agent puppet-agent-1.10.1-1.el6.x86_64 Priority: Minor Reporter: Christopher Wood This happens whenever the existing environment doesn't match what the ENC sets, which is fine (names in this post have been changed):
Jira (PUP-6493) Mount resource don't follow what documentation says(ensure => present is remounting)
Title: Message Title
Christopher Wood commented on PUP-6493
Re: Mount resource don't follow what documentation says(ensure => present is remounting)
I would very happily use this new nfs mount paradigm. I use a define right now anyway to create the directory, potentially run "mkdir -p" exec, and do the mount.
For my task I ended up copying the mount type+provider to another name ("cwoodmount" for the purposes of this example) and changed this line in the type:
Type.newtype(:mount, :self_refresh => true) do
To:
Type.newtype(:cwoodmount) do
Then in my nfs::mount define I toggle the provider based on the parameters.
It's klutzy but it lets me fiddle with nfs source ip addresses in fstab without puppet attempting to remount production partitions.
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-6493) Mount resource don't follow what documentation says(ensure => present is remounting)
Title: Message Title Christopher Wood commented on PUP-6493 Re: Mount resource don't follow what documentation says(ensure => present is remounting) I added 4.10.0 to the "Affects Version/s" field. I ran into this yesterday and can reproduce this behaviour on 4.4.2 and 4.10.0. My use case is that I need to change some nfs source ip addresses for some networking cleanup, and the idea was to use ensure=>present to change fstab "whenever", then have a reboot party in off hours with the new fstab, then go back to ensure=>mounted at a convenient 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-6493) Mount resource don't follow what documentation says(ensure => present is remounting)
Title: Message Title Christopher Wood updated an issue Puppet / PUP-6493 Mount resource don't follow what documentation says(ensure => present is remounting) Change By: Christopher Wood Affects Version/s: PUP 4.10.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-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title Christopher Wood commented on PUP-6518 Re: puppet resource package kernel reports the wrong rpm version For posterity, the output of the "yum install" command puppet is using, with some debug: [root@mail10c2 ~]# /usr/bin/yum -d 1 -e 1 -y install kernel Package kernel-2.6.32-642.6.2.el6.x86_64 already installed and latest version Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title
Christopher Wood commented on PUP-6518
Re: puppet resource package kernel reports the wrong rpm version
And oddly enough, now this is reporting the correct kernel version.
[root@mail10c2 rpm]# puppet resource package kernel
package { 'kernel':
ensure => '2.6.32-642.6.2.el6',
}
Still puppet 4.4.2 and so on.
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
Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title Christopher Wood commented on PUP-6518 Re: puppet resource package kernel reports the wrong rpm version Last question answered first: this is not causing a real problem. I noticed the oddity and filed the bug, little realizing the can of worms that packaging can be. At first glance I would expect puppet to report the same as the underlying utilities reported. In my case right now that would be: [root@mail10c2 ~]# rpm -q kernel kernel-2.6.32-220.23.1.el6.x86_64 kernel-2.6.32-642.1.1.el6.x86_64 kernel-2.6.32-642.3.1.el6.x86_64 kernel-2.6.32-642.6.2.el6.x86_64 Running "yum info kernel" or "yum info kernel-2.6.32" both provide the same output as each other, namely that there are four packages with "Name: kernel" installed. (It does seem like the kernel rpm is the odd one out, in that I can have only one rpm named "puppet-agent" but I can have multiple rpms named "kernel". Perhaps the underlying issue here is the assumption that in an rpm-based system there is only ever one package of a single "name"? Or maybe this is a special-case for kernel rpms on RH-family systems? My Debian laptop here has a kernel package named linux-image-3.16.0-4-amd64 and no other packages have that name.) (Mildly off topic: What happens in a multiarch situation? When I say "zlib1g" on a dpkg-based system, how does puppet know if I'm referring to "zlib1g:amd64" or "zlib1g:i386"? Separate bug though if that even ever hits me.) The updating comment refers to how
Jira (PUP-6914) ruby expand_path in file type breaks leading-tilde file resources
Title: Message Title Christopher Wood commented on PUP-6914 Re: ruby expand_path in file type breaks leading-tilde file resources Original thread: https://groups.google.com/forum/#!topic/puppet-users/vG8Wbtiwgow 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-6914) ruby expand_path in file type breaks leading-tilde file resources
Title: Message Title Christopher Wood created an issue Puppet / PUP-6914 ruby expand_path in file type breaks leading-tilde file resources Issue Type: Bug Affects Versions: PUP 4.8.0 Assignee: Unassigned Components: Types and Providers Created: 2016/11/10 2:44 PM Environment: $ uname -a Linux cwl 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux $ cat /etc/debian_version 8.6 $ puppet --version 4.8.0 $ /opt/puppetlabs/puppet/bin/ruby --version ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-linux] Priority: Minor Reporter: Christopher Wood This to reproduce: $ cat x.pp
Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-6518
puppet resource package kernel reports the wrong rpm version
Change By:
Christopher Wood
Here's an oddity I just found while doodling around with kernel version audits. It looks like 'puppet resource package kernel' hasn't figured out that I have a later version of the rpm than it reports.Before a reboot: {code} [root@mail10c2 puppet]# rpm -qa | grep ^kernel-2kernel-2.6.32-642.1.1.el6.x86_64kernel-2.6.32-642.3.1.el6.x86_64kernel-2.6.32-220.23.1.el6.x86_64[root@mail10c2 puppet]# uname -r2.6.32-642.1.1.el6.x86_64[root@mail10c2 puppet]# puppet resource package kernelpackage { 'kernel': ensure => '2.6.32-642.1.1.el6',} {code} After a reboot on that host: {code} [root@mail10c2 ~]# rpm -qa | grep ^kernel-2kernel-2.6.32-642.1.1.el6.x86_64kernel-2.6.32-642.3.1.el6.x86_64kernel-2.6.32-220.23.1.el6.x86_64[root@mail10c2 ~]# uname -r2.6.32-642.3.1.el6.x86_64[root@mail10c2 ~]# puppet resource package kernelpackage { 'kernel': ensure => '2.6.32-642.1.1.el6',} {code} I get a really odd result if I include as much of the kernel version as I can without getting a result of "purged": {code} [root@mail10c2 ~]# puppet resource package kernel-2.6.32package { 'kernel-2.6.32': ensure => '2.6.32-220.23.1.el6',} {code} Before or after the reboot, puppet seems to be fine with the set of rpms present and doesn't try to update, which is the behaviour I expect given this set of rpms and what is in the yum repo. {code} [root@mail10c2 ~]# puppet apply --verbose /tmp/p.pp Info: Loading factsNotice: Compiled catalog for mail10c2.megamailservers.com in environment production in 0.58 secondsInfo: Applying configuration version '1468852955'Notice: Applied catalog in 3.28 seconds {code} Subset of debug output: {code} Info: Applying configuration version '1468852983'Debug: Prefetching yum resources for packageDebug: Executing: '/bin/rpm --version'Debug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n''Debug: Executing: '/usr/bin/yum check-update'Debug: Finishing transaction 11823280Debug: Storing stateDebug: Stored state in 0.14 secondsNotice: Applied catalog in 1.39 seconds {code}
Add Comment
Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version
Title: Message Title Christopher Wood created an issue Puppet / PUP-6518 puppet resource package kernel reports the wrong rpm version Issue Type: Bug Affects Versions: PUP 4.4.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/07/18 7:45 AM Environment: [root@mail10c2 ~]# cat /etc/redhat-release CentOS release 6.8 (Final) [root@mail10c2 ~]# uname -r 2.6.32-642.3.1.el6.x86_64 Priority: Minor Reporter: Christopher Wood Here's an oddity I just found while doodling around with kernel version audits. It looks like 'puppet resource package kernel' hasn't figured out that I have a later version of the rpm than it reports. Before a reboot: [root@mail10c2 puppet]# rpm -qa | grep ^kernel-2 kernel-2.6.32-642.1.1.el6.x86_64 kernel-2.6.32-642.3.1.el6.x86_64 kernel-2.6.32-220.23.1.el6.x86_64 [root@mail10c2 puppet]# uname -r 2.6.32-642.1.1.el6.x86_64
Jira (PUP-5071) Problems with puppet-agent Debian uninstall
Title: Message Title Christopher Wood commented on PUP-5071 Re: Problems with puppet-agent Debian uninstall An "apt-get purge puppet-agent" works for me with puppet-agent 1.2.4-1jessie. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5050) can't remove puppet-agent 1.2.2-1jessie
Title: Message Title Christopher Wood commented on PUP-5050 Re: can't remove puppet-agent 1.2.2-1jessie To reproduce: add deb http://apt.puppetlabs.com jessie PC1 to your Debian sources apt-get update apt-get install puppet-agent dpkg -r -D113 puppet-agent Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5050) can't remove puppet-agent 1.2.2-1jessie
Title: Message Title Christopher Wood created an issue Puppet / PUP-5050 can't remove puppet-agent 1.2.2-1jessie Issue Type: Bug Affects Versions: puppet-agent 1.2.2 Assignee: Unassigned Components: Platform Created: 2015/08/18 10:01 AM Environment: root@cwl:~# uname -a Linux cwl 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux root@cwl:~# cat /etc/debian_version 8.1 Priority: Normal Reporter: Christopher Wood Fails on the pre-rm script: root@cwl:~# dpkg -r -D113 puppet-agent D01: ensure_diversions: new, (re)loading D01: process queue pkg puppet-agent:amd64 queue.len 0 progress 1, try 1 D01: deferred_remove package puppet-agent:amd64 D01: checking dependencies for remove 'puppet-agent:amd64' (Reading database ... 177012 files and directories currently installed.) Removing puppet-agent (1.2.2-1jessie) ... D02: fork/exec /var/lib/dpkg/info/puppet-agent.prerm ( remove ) Too few arguments. Too few arguments. Too few
Jira (PDB-1757) newer version check logs the wrong url
Title: Message Title Christopher Wood created an issue PuppetDB / PDB-1757 newer version check logs the wrong url Issue Type: Bug Affects Versions: PDB 2.2.2 Assignee: Unassigned Created: 2015/07/10 1:57 PM Environment: [root@puppetdb1 ~]# uname -a Linux puppetdb1.me.com 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux [root@puppetdb1 ~]# rpm -q puppetdb puppetdb-2.2.2-1.el6.noarch [root@puppetdb1 ~]# cat /etc/redhat-release CentOS release 6.2 (Final) Priority: Minor Reporter: Christopher Wood The log line which advertises the new version is pointing me to the wrong release. Shouldn't that be /3.0/ not /2.3/? 2015-07-10 01:35:07,437 INFO [c.p.p.c.services] Newer version 3.0.0 is available! Visit https://docs.puppetlabs.com/puppetdb/2.3/release_notes.html for details.
Jira (PUP-3992) yaml nulls break data binding for class params
Title: Message Title Christopher Wood commented on PUP-3992 Re: yaml nulls break data binding for class params After jcbollinger's followup in that thread, I think the problem here is not that puppet is not accepting the null as undef from hiera, but that the error message seems a bit puzzling. Instead of Must pass param1 perhaps something like Must pass a non-nil value for param1 Because the hiera key is there, it's just that the value associated with the key is unacceptable. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3992) ensure data binding for class params can produce undef
Title: Message Title
Christopher Wood commented on PUP-3992
Re: ensure data binding for class params can produce undef
I can confirm that hiera+puppet does work with {} or [] or '' in 3.7.2.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3992) yaml nulls break data binding for class params
Title: Message Title Christopher Wood commented on PUP-3992 Re: yaml nulls break data binding for class params Linking to some things also dealing with true/false/nil, it appears to my uneducated eyes that similar issues have cropped up before. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3992) yaml nulls break data binding for class params
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-3992
yaml nulls break data binding for class params
Change By:
Christopher Wood
Assumingthisclass:classtesting::cwood1($param1){#stuff}Andhavingayamlnullinmyhieradata,orakeywithnovalue,likeeitherofthese:testing::cwood1::param1:nulltesting::cwood1::param1:~testing::cwood1::param1:Igeterrorsabouthowtheclassneedsaparameter.Feb1011:14:05puppetmaster2devpuppet-master[7546]:Mustpassparam1toClass[Testing::Cwood1]at/etc/puppet/environments/production/modules/testing/manifests/init.pp:3onnodept1.me.comWithanexplicitlyemptystringIdonotseethiserror,theclassparameterisaccepted.testing::cwood1::param1:''Theproblemisthattheclassdoesn'tpickuphowI'vedefinedthehierakeytesting::cwood1::param1.NeverthelessthekeyisthereandIampassingsomething,evenifIampassingarepresentationofnothing.Iexpectedthatthismighthavethesameresultasdoing$param1=undefsincetheundefthereistheclosestthinginpuppettorubynil,yamlnull.Thatsaid,thereareanumberofinterestingticketsabouttrue/truthy/false/nilhandlingandIwilllinkthoseheresinceit'sprobablyasubsetofthoseissues.Further,astraightcommand-linehieralookupappearstorepresenttheseasnil. a [root@puppetmaster2dev~]#greptesting::cwood1::param1/etc/puppet/environments/production/hieradata/nodes/pt1.me.com.eyamltesting::cwood1::param1:null[root@puppetmaster2dev~]#hieratesting::cwood1::param1environment=productionfqdn=pt1.me.comnil[root@puppetmaster2dev~]#greptesting::cwood1::param1/etc/puppet/environments/production/hieradata/nodes/pt1.me.com.eyamltesting::cwood1::param1:~[root@puppetmaster2dev~]#hieratesting::cwood1::param1environment=productionfqdn=pt1.me.comnilAquickyamlreadpickstheseupasnil,aswell.#!/usr/bin/envrubyrequire'pp'require'yaml'data=File.read(ARGV[0])yaml=YAML.load(data)ppyamlYAMLnulls:http://yaml.org/type/null.html
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3992) yaml nulls break data binding for class params
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-3992
yaml nulls break data binding for class params
Issue Type:
Bug
Affects Versions:
PUP 3.7.2
Assignee:
Unassigned
Created:
2015/02/10 8:39 AM
Environment:
puppetmaster runs on:
[root@puppetmaster2dev ~]# cat /etc/redhat-release CentOS release 6.2 (Final) [root@puppetmaster2dev ~]# rpm -qa | egrep '^(puppet|hiera)' puppet-3.7.2-1.el6.noarch hiera-eyaml-1.3.4-1.el6.re.noarch hiera-1.3.4-1.el6.noarch puppetdb-terminus-2.2.2-1.el6.noarch
Priority:
Normal
Reporter:
Christopher Wood
Assuming this class:
class testing::cwood1 ( $param1 ) { # stuff }
And having a yaml null in my hieradata, or a key with no value, like either of these:
testing::cwood1::param1: null testing::cwood1::param1: ~ testing::cwood1::param1:
I get errors about how the class needs a parameter.
Feb 10 11:14:05 puppetmaster2dev puppet-master[7546]: Must pass param1 to Class[Testing::Cwood1] at /etc/puppet/environments/production/modules/testing/manifests/init.pp:3 on node pt1.me.com
With an
Jira (PUP-3992) yaml nulls break data binding for class params
Title: Message Title Christopher Wood commented on PUP-3992 Re: yaml nulls break data binding for class params Related thread: https://groups.google.com/forum/#!topic/puppet-users/0l3m4VCHjOg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1916) puppet cert clean cannot remove signing requests
Title: Message Title Christopher Wood commented on an issue Re: puppet cert clean cannot remove signing requests Cleaning a certificate request fails in 3.6.2 on CentOS as well. I confirm this used to work in the 2.7 series. Add Comment Puppet / PUP-1916 puppet cert clean cannot remove signing requests I have a certificate signing request that I would like to get rid of with puppet cert. However, I can only list and sign CSRs. Here's my log: [root@operations ~]# puppet --version 3.4.2 [root@operations ~]# puppet cert list | grep local localhost.localdomain (MD5) 12:5E:40:6B:79:84:6F:9C:51:7B:40:81:30:30:8B:F5 [root@operations ~]# puppet c... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3055) file type can't implicitly manage /
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-3055
file type can't implicitly manage /
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
13/Aug/14 2:06 PM
Environment:
Tested on: CentOS 6.2 Debian 7.6 (Stable)
Priority:
Trivial
Reporter:
Christopher Wood
The file type doesn't appear to understand that '/' (the root of the filesystem) is a manageable directory target, unlike the behaviour with every single other unix path I've tried this on.
If I use this, it fails:
file { '/': }
But this works:
file { '/': path = '/', }
On Debian:
root@cwl:~# cat /tmp/x.pp file { '/': # path = '/', }
root@cwl:~# puppet apply --debug /tmp/x.pp Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood commented on an issue
Re: yumrepo can create a non-idempotent repository file
This still happens in 3.6.1, by my attempt, but I get a different failure (could not prefetch provider rather than could not evaluate):
root@cwl:~# puppet --version 3.6.1 root@cwl:~# root@cwl:~# root@cwl:~# cat /etc/yum/repos.d/centos-media.repo [centos-media] name=CentOS-$releasever - Media baseurl=file:///media/CentOS/ file:///media/cdrom/ file:///media/cdrecorder/ enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 root@cwl:~# puppet --version 3.6.1 root@cwl:~# puppet apply --verbose /tmp/yr.pp Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1071:in `each') Notice: Compiled catalog for cwl.hostopia.com in environment production in 0.03 seconds Info: Applying configuration version '1401994806' Error: Could not prefetch yumrepo provider 'inifile': Can't parse line 'file:///media/cdrom/' at /etc/yum/repos.d/centos-media.repo:4 Notice: /Stage[main]/Main/Yumrepo[centos-media]/ensure: created Notice: Finished catalog run in 0.08 seconds
Add Comment
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
If I use the attached yumrepo declaration then things are fine (notice the leading spaces before the next two file urls): {noformat} [root@cwt1 ~]# puppet apply --verbose /tmp/yr.pp Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/l...
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title Christopher Wood commented on an issue Re: yumrepo can create a non-idempotent repository file The previous comment was in Debian Wheezy, I get the same results in CentOS 6: cat /etc/yum.repos.d/centos-media.repo [centos-media] baseurl=file:///media/CentOS/ file:///media/cdrom/ file:///media/cdrecorder/ enabled=0 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 name=CentOS-$releasever - Media puppet --version 3.6.1 puppet apply --verbose /tmp/yr.pp Info: Loading facts in /var/lib/puppet/lib/facter/hpsrl.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Notice: Compiled catalog for mail53c40.carrierzone.com in environment production in 0.11 seconds Info: Applying configuration version '1401995354' Error: Could not prefetch yumrepo provider 'inifile': Can't parse line 'file:///media/cdrom/' at /etc/yum.repos.d/centos-media.repo:3 Notice: /Stage[main]/Main/Yumrepo[centos-media]/ensure: created Notice: Finished catalog run in 0.22 seconds Add Comment Puppet / PUP-1741 yumrepo can create a non-idempotent repository file
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title Christopher Wood commented on an issue Re: yumrepo can create a non-idempotent repository file CentOS 6 again: puppet apply --trace /tmp/yr.pp Notice: Compiled catalog for mail53c40.carrierzone.com in environment production in 0.11 seconds Error: Could not prefetch yumrepo provider 'inifile': Can't parse line 'file:///media/cdrom/' at /etc/yum.repos.d/centos-media.repo:3 /usr/lib/ruby/site_ruby/1.8/puppet/util/inifile.rb:192:in `parse' /usr/lib/ruby/site_ruby/1.8/puppet/util/inifile.rb:159:in `each_line' /usr/lib/ruby/site_ruby/1.8/puppet/util/inifile.rb:159:in `parse' /usr/lib/ruby/site_ruby/1.8/puppet/util/inifile.rb:141:in `read' /usr/lib/ruby/site_ruby/1.8/puppet/util/inifile.rb:274:in `read' /usr/lib/ruby/site_ruby/1.8/puppet/provider/yumrepo/inifile.rb:134:in `virtual_inifile' /usr/lib/ruby/site_ruby/1.8/puppet/provider/yumrepo/inifile.rb:133:in `each' /usr/lib/ruby/site_ruby/1.8/puppet/provider/yumrepo/inifile.rb:133:in `virtual_inifile' /usr/lib/ruby/site_ruby/1.8/puppet/provider/yumrepo/inifile.rb:34:in `instances' /usr/lib/ruby/site_ruby/1.8/puppet/provider/yumrepo/inifile.rb:60:in `prefetch' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:277:in `prefetch' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:167:in `prefetch_if_necessary' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:67:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/graph/relationship_graph.rb:116:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/graph/relationship_graph.rb:116:in `traverse' /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:108:in `evaluate' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:167:in `apply' /usr/lib/ruby/site_ruby/1.8/puppet/util/log.rb:149:in `with_destination' /usr/lib/ruby/site_ruby/1.8/puppet/transaction/report.rb:112:in `as_logging_destination' /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:166:in `apply' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:117:in `apply_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:161:in `benchmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:160:in `benchmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:116:in `apply_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:191:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:288:in `apply_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:228:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/context.rb:64:in `override' /usr/lib/ruby/site_ruby/1.8/puppet.rb:234:in `override' /usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:190:in `main' /usr/lib/ruby/site_ruby/1.8/puppet/application/apply.rb:151:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:371:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:477:in `plugin_hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:371:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:479:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:371:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:137:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:91:in `execute' /usr/bin/puppet:4 Notice: /Stage[main]/Main/Yumrepo[centos-media]/ensure: created Notice: Finished catalog run in 0.24 seconds
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood commented on an issue
Re: yumrepo can create a non-idempotent repository file
That works for me, fail manifest compilation on invalid data.
Add Comment
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
If I use the attached yumrepo declaration then things are fine (notice the leading spaces before the next two file urls): {noformat} [root@cwt1 ~]# puppet apply --verbose /tmp/yr.pp Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/l...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1374) Unable to catch invalid attribute with parser validate
Title: Message Title
Christopher Wood commented on an issue
Re: Unable to catch invalid attribute with parser validate
We do the same thing and see the same results, except that --noop gives an error for me. My example:
$ cat /tmp/ft.pp file { '/tmp/file123': ensure = present, content = file123\n, enable = true, }
$ puppet --version 3.4.3 $ puppet parser validate /tmp/ft.pp $ puppet apply --noop /tmp/ft.pp Error: Invalid parameter enable at /tmp/ft.pp:5 on node cwl.hostopia.com Error: Invalid parameter enable at /tmp/ft.pp:5 on node cwl.hostopia.com
Add Comment
Puppet / PUP-1374
Unable to catch invalid attribute with parser validate
We're running parser validate in jenkins on our changes to notify the owner of the changeset if something is not cool. However last week the following code was slipping through: {code} user { 'dummy': comment = 'dummy user', ensure = present, uid = '666', groups = 'wheel', home = '/home/dummy', managehome = true, ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are
Jira (PUP-1889) emacs mode doesn't match style guide when formatting fat comma arrows
Title: Message Title Christopher Wood updated an issue Puppet / PUP-1889 emacs mode doesn't match style guide when formatting fat comma arrows Change By: Christopher Wood Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1889) emacs mode doesn't match style guide when formatting fat comma arrows
Title: Message Title Christopher Wood updated an issue Puppet / PUP-1889 emacs mode doesn't match style guide when formatting fat comma arrows Change By: Christopher Wood Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood created an issue
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
Issue Type:
Bug
Affects Versions:
3.4.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
20/Feb/14 9:56 AM
Environment:
[root@cwt1 ~]# cat /etc/redhat-release CentOS release 6.2 (Final) [root@cwt1 ~]# uname -a Linux cwt1 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux [root@cwt1 ~]# puppet --version 3.4.2
Priority:
Minor
Reporter:
Christopher Wood
If I use this yumrepo declaration:
yumrepo { 'centos-media': baseurl = file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/, #baseurl = file:///media/CentOS/\n file:///media/cdrom/\n file:///media/cdrecorder/, enabled = 0, gpgcheck = 1, gpgkey = 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6', mirrorlist = absent, descr = 'CentOS-$releasever - Media', priority = absent, }
Then things are fine (notice the leading spaces before the next two file urls):
[root@cwt1 ~]# puppet apply
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
Change By:
Christopher Wood
IfIusethisyumrepodeclaration:yumrepo{'centos-media': baseurl=file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/, #baseurl=file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/, enabled=0, gpgcheck=1, gpgkey='file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6', mirrorlist=absent, descr='CentOS-$releasever-Media', priority=absent,
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title Christopher Wood updated an issue Puppet / PUP-1741 yumrepo can create a non-idempotent repository file Since the formatting is bad in the description, I am attaching the yumrepo resource in question. Change By: Christopher Wood Attachment: yr.pp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1741) yumrepo can create a non-idempotent repository file
Title: Message Title
Christopher Wood updated an issue
Puppet / PUP-1741
yumrepo can create a non-idempotent repository file
Change By:
Christopher Wood
IfIuse this theattached yumrepodeclaration :yumrepo{'centos-media':baseurl=file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/,#baseurl=file:///media/CentOS/\nfile:///media/cdrom/\nfile:///media/cdrecorder/,enabled=0,gpgcheck=1,gpgkey='file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6',mirrorlist=absent,descr='CentOS-$releasever-Media',priority=absent,}Then then
Jira (PUP-1360) more verbosity in thing-not-found debug logs
Title: Message Title Christopher Wood updated an issue Puppet / PUP-1360 more verbosity in thing-not-found debug logs Change By: Christopher Wood Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
