Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
h4. A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [*area*|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287].h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:{panel}*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from
Jira (PDB-4686) Update FOSS PDB module with recently added config settings
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4686 Update FOSS PDB module with recently added config settings Issue Type: New Feature Assignee: Unassigned Created: 2020/04/21 10:47 AM Priority: Normal Reporter: Zachary Kent We need to update the FOSS PDB module to expose config settings we've added recently. It would also be nice to address some of the outstanding community PRs that have been raised. Making a release with these new settings will require updates to our testing suite to get everything green again. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10432) RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10432 RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems Change By: Josh Cooper Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356228.1587487722000.43082.1587489540030%40Atlassian.JIRA.
Jira (PUP-10432) RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Title: Message Title
Matt Schlosser updated an issue
Puppet / PUP-10432
RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Change By:
Matt Schlosser
*Puppet Version: 5.5.x (probably 6.x as well)* *Puppet Server Version: NA, but 5.3.x* *OS Name/Version: RedHat Linux 7.8*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Yum package ensure => latest should ensure latest*Actual Behavior:*Yum package ensure => latest never finds an update. Explicit versions work OK.More details:RH added a newline character when subscription manager is enabled.yum.rb looks for first blank line: [https://github.com/puppetlabs/puppet/blob/f2709eb5b28894cf017dbe41290d3c0d168e721b/lib/puppet/provider/package/yum.rb#L123-L125] {code:java}lib/puppet/provider/package/yum.rb:123-125 def self.parse_updates(str) # Strip off all content before the first blank line body = str.partition(/^\s*\n/m).last{code} As a result, parse_updates returns {} when subscription manager is enabled.Old behavior:{code:java}# yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register.{code} New behavior:{code:java}# yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-managerThis system is not registered with an entitlement server. You can use subscription-manager to register.{code} workaround 1: disable subscription-manager workaround 2: downgrade subscription-manager Example Code: $app == 'pcmhi' $version == 'latest'{code:java} # package package { $app: ensure=> $version, provider => yum, require => Yumrepo[$app], subscribe => [ Package['nginx'], Package['python3'] ] }{code} Repo Contents:{code:java}Index of rpm/pcmhi/quality_assuranceName Last modified Size../repodata/ 20-Apr-2020 19:28-pcmhi-3.5.23-0.x86_64.rpm 20-Apr-2020 16:01 19.53 MBpcmhi-3.6.0-0.x86_64.rpm20-Apr-2020 19:28 23.33 MB{code}Manual Update Check:{code:java}# yum check-update | grep pcmhi pcmhi.x86_64 1:3.6.0-0 pcmhi{code} Puppet logs:{code:java}^[[0;36mDebug: Executing: '/bin/rpm --version'^[[0m ^[[0;36mDebug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' | sort'^[[0m ^[[0;36mDebug: Executing: '/bin/yum check-update'^[[0m{code} PoC fix debug output for yum.rb: {code:java}def self.parse_updates(str) # Strip off all content before the first blank line self.debug "parse_updates input #{str}" body = str.partition(/^\s*\n/m).last self.debug "parse_updates body #{body}" updates = Hash.new { |h, k| h[k] = [] } body.split.each_slice(3) do |tuple| self.debug "tuple #{tuple}" break if tuple[0] =~ /^(Obsoleting|Security:|Update)/ {code} Custom Debug Output (bad): {code:java}Debug: Executing:
Jira (PUP-10432) RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Title: Message Title
Matt Schlosser updated an issue
Puppet / PUP-10432
RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Change By:
Matt Schlosser
*Puppet Version: 5.5.x (probably 6.x as well)* *Puppet Server Version: NA, but 5.3.x* *OS Name/Version: RedHat Linux 7.8*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Yum package ensure => latest should ensure latest*Actual Behavior:*Yum package ensure => latest never finds an update. Explicit versions work OK.More details:RH added a newline character when subscription manager is enabled.yum.rb looks for first blank line: [https://github.com/puppetlabs/puppet/blob/f2709eb5b28894cf017dbe41290d3c0d168e721b/lib/puppet/provider/package/yum.rb#L123-L125] {code:java}lib/puppet/provider/package/yum.rb:123-125 def self.parse_updates(str) # Strip off all content before the first blank line body = str.partition(/^\s*\n/m).last{code} As a result, parse_updates returns {} when subscription manager is enabled.Old behavior:{code:java}# yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register.{code} New behavior:{code:java}# yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-managerThis system is not registered with an entitlement server. You can use subscription-manager to register.{code} workaround 1: disable subscription-manager workaround 2: downgrade subscription-manager Example Code: $app == 'pcmhi' $version == 'latest'{code:java} # package package { $app: ensure=> $version, provider => yum, require => Yumrepo[$app], subscribe => [ Package['nginx'], Package['python3'] ] }{code} Repo Contents:{code:java}Index of rpm/pcmhi/quality_assuranceName Last modified Size../repodata/ 20-Apr-2020 19:28-pcmhi-3.5.23-0.x86_64.rpm 20-Apr-2020 16:01 19.53 MBpcmhi-3.6.0-0.x86_64.rpm20-Apr-2020 19:28 23.33 MB{code}Manual Update Check:{code:java}# yum check-update | grep pcmhi pcmhi.x86_64 1:3.6.0-0 pcmhi{code} Puppet logs:{code:java}^[[0;36mDebug: Executing: '/bin/rpm --version'^[[0m ^[[0;36mDebug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' | sort'^[[0m ^[[0;36mDebug: Executing: '/bin/yum check-update'^[[0m{code} PoC fix for yum.rb: {code:java}def self.parse_updates(str) # Strip off all content before the first blank line self.debug "parse_updates input #{str}" body = str.partition(/^\s*\n/m).last self.debug "parse_updates body #{body}" updates = Hash.new { |h, k| h[k] = [] } body.split.each_slice(3) do |tuple| self.debug "tuple #{tuple}" break if tuple[0] =~ /^(Obsoleting|Security:|Update)/ {code} Custom Debug Output (bad): {code:java}Debug: Executing: '/bin/yum
Jira (PUP-10432) RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Title: Message Title
Matt Schlosser updated an issue
Puppet / PUP-10432
RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Change By:
Matt Schlosser
*Puppet Version: 5.5.x (probably 6.x as well)* *Puppet Server Version: NA, but 5.3.x* *OS Name/Version: RedHat Linux 7.8*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Yum package ensure => latest should ensure latest*Actual Behavior:*Yum package ensure => latest never finds an update. Explicit versions work OK.More details:RH added a newline character when subscription manager is enabled.yum.rb looks for first blank line: [https://github.com/puppetlabs/puppet/blob/f2709eb5b28894cf017dbe41290d3c0d168e721b/lib/puppet/provider/package/yum.rb#L123-L125] {code:java}lib/puppet/provider/package/yum.rb:123-125 def self.parse_updates(str) # Strip off all content before the first blank line body = str.partition(/^\s*\n/m).last{code} As a result, parse_updates returns {} when subscription manager is enabled.Old behavior:{code:java}# yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register.{code} New behavior:{code:java}# yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-managerThis system is not registered with an entitlement server. You can use subscription-manager to register.{code} workaround 1: disable subscription-manager workaround 2: downgrade subscription-manager Example Code: $app == 'pcmhi' $version == 'latest'{code:java} # package package { $app: ensure=> $version, provider => yum, require => Yumrepo[$app], subscribe => [ Package['nginx'], Package['python3'] ] }{code} Repo Contents:{code:java}Index of rpm/pcmhi/quality_assuranceName Last modified Size../repodata/ 20-Apr-2020 19:28-pcmhi-3.5.23-0.x86_64.rpm 20-Apr-2020 16:01 19.53 MBpcmhi-3.6.0-0.x86_64.rpm20-Apr-2020 19:28 23.33 MB{code}Manual Update Check:{code:java}# yum check-update | grep pcmhi pcmhi.x86_64 1:3.6.0-0 pcmhi{code} Puppet logs:{code:java}^[[0;36mDebug: Executing: '/bin/rpm --version'^[[0m ^[[0;36mDebug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' | sort'^[[0m ^[[0;36mDebug: Executing: '/bin/yum check-update'^[[0m{code} PoC fix for yum.rb: {code:java}def self.parse_updates(str) # Strip off all content before the first blank line self.debug "parse_updates input #{str}" body = str.partition(/^\s*\n/m).last self.debug "parse_updates body #{body}" updates = Hash.new { |h, k| h[k] = [] } body.split.each_slice(3) do |tuple| self.debug "tuple #{tuple}" break if tuple[0] =~ /^(Obsoleting|Security:|Update)/ {code} Custom Debug Output (bad): {code:java} Debug: Executing: '/bin/yum
Jira (PUP-10432) RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Title: Message Title
Matt Schlosser updated an issue
Puppet / PUP-10432
RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Change By:
Matt Schlosser
*Puppet Version: 5.5.x (probably 6.x as well)* *Puppet Server Version: NA, but 5.3.x* *OS Name/Version: RedHat Linux 7.8*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Yum package ensure => latest should ensure latest*Actual Behavior:*Yum package ensure => latest never finds an update. Explicit versions work OK.More details:RH added a newline character when subscription manager is enabled.yum.rb looks for first blank line: [https://github.com/puppetlabs/puppet/blob/f2709eb5b28894cf017dbe41290d3c0d168e721b/lib/puppet/provider/package/yum.rb#L123-L125] {code:java} lib/puppet/provider/package/yum.rb:123-125 def self.parse_updates(str) # Strip off all content before the first blank line body = str.partition(/^\s*\n/m).last{code} As a result, parse_updates returns {} when subscription manager is enabled.Old behavior:{code:java} # yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register.{code} New behavior:{code:java} # yum check-update Loaded plugins: product-id, search-disabled-repos, subscription-managerThis system is not registered with an entitlement server. You can use subscription-manager to register.{code} As a result, parse_updates returns {} when subscription manager is enabled. workaround 1: disable subscription-managerworkaround 2: downgrade subscription-manager Example Code:$app == 'pcmhi'$version == 'latest'{code:java} # package package { $app: ensure=> $version, provider => yum, require => Yumrepo[$app], subscribe => [ Package['nginx'], Package['python3'] ] }{code} Repo Contents:{code:java} Index of rpm/pcmhi/quality_assuranceName Last modified Size../repodata/ 20-Apr-2020 19:28-pcmhi-3.5.23-0.x86_64.rpm 20-Apr-2020 16:01 19.53 MBpcmhi-3.6.0-0.x86_64.rpm20-Apr-2020 19:28 23.33 MB{code}Manual Update Check:{code:java} # yum check-update | grep pcmhi pcmhi.x86_64 1:3.6.0-0 pcmhi{code} Puppet logs:{code:java} ^[[0;36mDebug: Executing: '/bin/rpm --version'^[[0m ^[[0;36mDebug: Executing '/bin/rpm -qa --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' | sort'^[[0m ^[[0;36mDebug: Executing: '/bin/yum check-update'^[[0m{code} PoC fix for yum.rb: {code:java} def self.parse_updates(str) # Strip off all content before the first blank line self.debug "parse_updates input #{str}" body = str.partition(/^\s*\n/m).last self.debug "parse_updates body #{body}" updates = Hash.new { |h, k| h[k] = [] } body.split.each_slice(3) do |tuple| self.debug "tuple #{tuple}" break if tuple[0] =~
Jira (PUP-10432) RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems
Title: Message Title Matt Schlosser created an issue Puppet / PUP-10432 RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems Issue Type: Bug Assignee: Unassigned Created: 2020/04/21 9:48 AM Priority: Normal Reporter: Matt Schlosser Puppet Version: 5.5.x (probably 6.x as well) Puppet Server Version: NA, but 5.3.x OS Name/Version: RedHat Linux 7.8 Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Yum package ensure => latest should ensure latest Actual Behavior: Yum package ensure => latest never finds an update. Explicit versions work OK. More details: RH added a newline character when subscription manager is enabled. yum.rb looks for first blank line: https://github.com/puppetlabs/puppet/blob/f2709eb5b28894cf017dbe41290d3c0d168e721b/lib/puppet/provider/package/yum.rb#L123-L125 lib/puppet/provider/package/yum.rb:123-125 def self.parse_updates(str) # Strip off all content before the first blank line body = str.partition(/^\s*\n/m).last
Jira (PUP-10426) if certname entry is not in [main] section of puppet.conf file provide a warning
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10426 if certname entry is not in [main] section of puppet.conf file provide a warning Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.355976.1587134534000.42980.1587487140084%40Atlassian.JIRA.
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
h4. A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [ * area . * |https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287] . h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:{panel}*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:{panel}*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:{panel}*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:{panel}*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:{panel}*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing: {panel} *{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \}{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'} {color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \{ 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \}{panel} Here are some debug logs which prove that the comparison happened with epoch missing: *{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version 1.10.6-4.el7
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \ { 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \ }{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \ { 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \ }{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'} {color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \ { 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \ }{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \ { 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \ }{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \ { 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \ }{panel}{panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package \ { 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum', \ }{panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'} {color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \ { 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \ } {panel} {panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'} {color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}{color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package \ { 'python-docker-pycreds': ensure => '1.10.6-4.el7', provider => 'yum', \ }{panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package \{ 'python-docker-pycreds': ensure => '1:0.3.0-7.el7', provider => 'yum',\}{panel} {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}* *{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package Unknown macro: \{ 'python-docker-pycreds' } : ensure => '1:0.3.0-7.el7', provider => 'yum', \} {panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'} {color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package Unknown macro: \{ 'python-docker-pycreds' : ensure => '1.10.6-4.el7', provider => 'yum',\ } {panel} {panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'} {color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color} {color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package Unknown macro: \{ 'python-docker-pycreds' } : ensure => '1.10.6-4.el7', provider => 'yum',\} {panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}*
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-10431
Yum package provider tries to downgrade because of faulty comparison
Change By:
Luchian Nemes
h3. *{{Description:}}* A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code [area.|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L274..L287]h3. *{{How to reproduce the issue:}}*1. Find a package that has a version higher than the other only because of epoch. Example:{panel:title=> yum list python-docker-pycreds --show-duplicates}…python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 …{panel} 2. Simply install the two versions shown above in any order to get the issue:{panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'}{color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package Unknown macro: \{ 'python-docker-pycreds' } : ensure => '1:0.3.0-7.el7', provider => 'yum',\} {panel} {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'}*{color:#de350b}Error: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}**{color:#de350b}Error: /Package[python-docker-pycreds]/ensure: change from '1:0.3.0-7.el7' to '1.10.6-4.el7' failed: Could not update: Failed to update to version 1.10.6-4.el7, got version 1:0.3.0-7.el7 instead{color}*package Unknown macro: \{ 'python-docker-pycreds'} {panel} OR {panel:title=> puppet resource package 'python-docker-pycreds' ensure='1.10.6-4.el7' provider='yum'} {color:#00875a}Notice: /Package[python-docker-pycreds]/ensure: created{color}package Unknown macro: \{ 'python-docker-pycreds'} {panel} {panel:title=> puppet resource package 'python-docker-pycreds' ensure='0.3.0-7.el7' provider='yum'} {color:#de350b}*Error: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}{color:#de350b}*Error: /Package[python-docker-pycreds]/ensure: change from '1.10.6-4.el7' to '0.3.0-7.el7' failed: Could not update: Failed to update to version 0.3.0-7.el7, got version 1.10.6-4.el7 instead*{color}package Unknown macro: \{ 'python-docker-pycreds'} {panel} Here are some debug logs which prove that the comparison happened with epoch missing:*{color:#403294}Debug:{color}* Package[python-docker-pycreds](provider=yum): Downgrading package python-docker-pycreds from version 1.10.6-4.el7 to
Jira (PUP-10431) Yum package provider tries to downgrade because of faulty comparison
Title: Message Title Luchian Nemes created an issue Puppet / PUP-10431 Yum package provider tries to downgrade because of faulty comparison Issue Type: Bug Assignee: Unassigned Created: 2020/04/21 8:55 AM Environment: RedHat 7 machine with puppet installed (tested on Puppet 6.14 but the issue seems to be way older). Priority: Normal Reporter: Luchian Nemes Description: A (yum) package with versions containing epoch can cause unwanted behaviour when trying to install another version. It tries to downgrade when it should actually upgrade. This only happens when the version installed or the version we want to install is higher than the other only because of epoch (1:2.0 vs 5:1.0; if we strip down the epoch, all comparisons will have different results: 1.0 < 2.0). Root cause found to be in this code area. How to reproduce the issue: 1. Find a package that has a version higher than the other only because of epoch. Example: > yum list python-docker-pycreds --show-duplicates … python-docker-pycreds.noarch 1.10.6-4.el7 python-docker-pycreds.noarch 1:0.3.0-7.el7 … 2. Simply install the two versions shown above in any order to get the issue:
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider So it is not a bug, just using the function newproperty in a way unexpected. This issue can be closed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42837.1587483360024%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l assigned an issue to Dan33l Puppet / PUP-10428 Puppet parser only consider first element of array for properties in custom provider Change By: Dan33l Assignee: Dan33l Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42814.1587481920032%40Atlassian.JIRA.
Jira (PUP-10430) Yum package provider update/downgrade not working correctly with epochs
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-10430
Yum package provider update/downgrade not working correctly with epochs
Change By:
Gheorghe Popescu
When installing a package using the yum package provider we can end-up in a situation where a package is installed from a distinct epoch even though we didn't specify an epoch .Trying to ensure another version, the comparison method can end-up giving the wrong result depending on package version, epoch and order of parameters.rpm comparions: [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167]usage in yum: [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L279-L284] This can be reproduced using `python-docker-pycreds` package on a redhat7 box. Example:- available versions: 1.10.6-1.el7, 1.10.6-3.el7 , 1.10.6-4.el7, 1:0.3.0-7.el7 - installed version: 1:0.3.0-7.el7running: {noformat}❯ puppet resource package python-docker-pycreds ensure='1.10.6-3.el7' provider=yum{noformat}results in trying to use `update` flag with an older version:{noformat}Debug: Package[python-docker-pycreds](provider=yum): Upgrading package python-docker-pycreds from version 1:0.3.0-11.el7 to 1.10.6-3.el7 Debug: Executing: ‘/usr/bin/yum -d 0 -e 0 -y update python-docker-pycreds-1.10.6-3.el7’ Debug: Executing: ’/usr/bin/rpm -q python-docker-pycreds --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n’ Debug: Cannot parse 1.10.6-3.el7 as a RPM version range Error: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead Error: /Stage[main]/Main/Package[python-docker-pycreds]/ensure: change from ‘1:0.3.0-11.el7’ to ‘1.10.6-3.el7’ failed: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead{noformat}
Add Comment
Jira (PUP-10430) Yum package provider update/downgrade not working correctly with epochs
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-10430
Yum package provider update/downgrade not working correctly with epochs
Change By:
Gheorghe Popescu
When installing a package using the yum package provider we can end-up in a situation where a package is installed from a distinct epoch even though we didn't specify an epoch.Trying to ensure another version, the comparison method can end-up giving the wrong result depending on package version, epoch and order of parameters.rpm comparions: [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167]usage in yum: [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L279-L284] This can be reproduces reproduced using `python-docker-pycreds` package on a redhat7 box.available versions: 1.10.6-1.el7, 1.10.6-3.el7 , 1.10.6-4.el7, 1:0.3.0-7.el7installed version: 1:0.3.0-7.el7running: {noformat}❯ puppet resource package python-docker-pycreds ensure='1.10.6-3.el7' provider=yum{noformat}results in trying to use `update` flag with an older version:{noformat}Debug: Package[python-docker-pycreds](provider=yum): Upgrading package python-docker-pycreds from version 1:0.3.0-11.el7 to 1.10.6-3.el7 Debug: Executing: ‘/usr/bin/yum -d 0 -e 0 -y update python-docker-pycreds-1.10.6-3.el7’ Debug: Executing: ’/usr/bin/rpm -q python-docker-pycreds --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n’ Debug: Cannot parse 1.10.6-3.el7 as a RPM version range Error: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead Error: /Stage[main]/Main/Package[python-docker-pycreds]/ensure: change from ‘1:0.3.0-11.el7’ to ‘1.10.6-3.el7’ failed: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead{noformat}
Add Comment
Jira (PUP-10430) Yum package provider update/downgrade not working correctly with epochs
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-10430
Yum package provider update/downgrade not working correctly with epochs
Change By:
Gheorghe Popescu
When installing a package using the yum package provider we can end-up in a situation where a package is installed from a distinct epoch even though we didn't specify an epoch.Trying to ensure another version, the comparison method can end-up giving the wrong result depending on package version, epoch and order of parameters .rpm comparions : [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167] usage in yum: [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/yum.rb#L279-L284] This can be reproduces using `python-docker-pycreds` package on a redhat7 box.available versions: 1.10.6-1.el7, 1.10.6-3.el7 , 1.10.6-4.el7, 1:0.3.0-7.el7installed version: 1:0.3.0-7.el7running: {noformat}❯ puppet resource package python-docker-pycreds ensure='1.10.6-3.el7' provider=yum{noformat}results in trying to use `update` flag with an older version:{noformat} Debug: Package[python-docker-pycreds](provider=yum): Upgrading package python-docker-pycreds from version 1:0.3.0-11.el7 to 1.10.6-3.el7 Debug: Executing: ‘/usr/bin/yum -d 0 -e 0 -y update python-docker-pycreds-1.10.6-3.el7’ Debug: Executing: ’/usr/bin/rpm -q python-docker-pycreds --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n’ Debug: Cannot parse 1.10.6-3.el7 as a RPM version range Error: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead Error: /Stage[main]/Main/Package[python-docker-pycreds]/ensure: change from ‘1:0.3.0-11.el7’ to ‘1.10.6-3.el7’ failed: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead{noformat}
Add Comment
Jira (PUP-10430) Yum package provider update/downgrade not working correctly with epochs
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-10430
Yum package provider update/downgrade not working correctly with epochs
Change By:
Gheorghe Popescu
When installing a package using the yum package provider we can end-up in a situation where a package is installed from a distinct epoch even though we didn't specify an epoch.Trying to ensure another version, the comparison method can end-up giving the wrong result depending on package version, epoch and order of parameters: [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167] This can be reproduces using `python-docker-pycreds` package on a redhat7 box.available versions: 1.10.6-1.el7, 1.10.6-3.el7 , 1.10.6-4.el7, 1:0.3.0-7.el7installed version: 1:0.3.0-7.el7running: {noformat}❯ puppet resource package python-docker-pycreds ensure='1.10.6-3.el7' provider=yum{noformat}results in trying to use `update` flag with an older version:{noformat} Debug: Package[python-docker-pycreds](provider=yum): Upgrading package python-docker-pycreds from version 1:0.3.0-11.el7 to 1.10.6-3.el7Debug: Executing: ‘/usr/bin/yum -d 0 -e 0 -y update python-docker-pycreds-1.10.6-3.el7’Debug: Executing: ’/usr/bin/rpm -q python-docker-pycreds --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n’Debug: Cannot parse 1.10.6-3.el7 as a RPM version rangeError: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 insteadError: /Stage[main]/Main/Package[python-docker-pycreds]/ensure: change from ‘1:0.3.0-11.el7’ to ‘1.10.6-3.el7’ failed: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead{noformat}
Add Comment
Jira (PUP-10430) Yum package provider update/downgrade not working correctly with epochs
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-10430
Yum package provider update/downgrade not working correctly with epochs
Change By:
Gheorghe Popescu
When installing a package using the yum package provider we can end-up in a situation where a package is installed from a distinct epoch even though we didn't specify an epoch.Trying to ensure another version, the comparison method can end-up giving the wrong result depending on package version, epoch and order of parameters: [ https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167] This can be reproduces using `python-docker-pycreds` package on a redhat7 box.available versions: 1.10.6-1.el7, 1.10.6-3.el7 , 1.10.6-4.el7, 1:0.3.0-7.el7installed version: 1:0.3.0-7.el7running: {noformat} ❯ puppet resource package python-docker-pycreds ensure='1.10.6-3.el7' provider=yum{noformat}results in trying to use `update` flag with an older version:{noformat} Debug: Package[python-docker-pycreds](provider=yum): Upgrading package python-docker-pycreds from version 1:0.3.0-11.el7 to 1.10.6-3.el7 Debug: Executing: ‘/usr/bin/yum -d 0 -e 0 -y update python-docker-pycreds-1.10.6-3.el7’ Debug: Executing: ’/usr/bin/rpm -q python-docker-pycreds --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n’ Debug: Cannot parse 1.10.6-3.el7 as a RPM version range Error: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead Error: /Stage[main]/Main/Package[python-docker-pycreds]/ensure: change from ‘1:0.3.0-11.el7’ to ‘1.10.6-3.el7’ failed: Could not update: Failed to update to version 1.10.6-3.el7, got version 1:0.3.0-11.el7 instead{noformat}
Add Comment
Jira (PUP-10430) Yum package provider update/downgrade not working correctly with epochs
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-10430 Yum package provider update/downgrade not working correctly with epochs Issue Type: Bug Affects Versions: PUP 6.14.0, PUP 5.5.19 Assignee: Unassigned Components: Types and Providers Created: 2020/04/21 7:35 AM Priority: Normal Reporter: Gheorghe Popescu When installing a package using the yum package provider we can end-up in a situation where a package is installed from a distinct epoch even though we didn't specify an epoch. Trying to ensure another version, the comparison method can end-up giving the wrong result depending on package version, epoch and order of parameters: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/rpm_compare.rb#L167 This can be reproduces using `python-docker-pycreds` package on a redhat7 box. available versions: 1.10.6-1.el7, 1.10.6-3.el7 , 1.10.6-4.el7, 1:0.3.0-7.el7 installed version: 1:0.3.0-7.el7 running: ❯ puppet resource package python-docker-pycreds ensure='1.10.6-3.el7' provider=yum results in trying to use `update` flag with an older version:
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title David Schmitt commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider To answer the question for the Resource API side, I've enhanced the tests in https://github.com/puppetlabs/puppet-resource_api/pull/269 to show that even with an Any-typed attribute, the handling of array-valued arguments works. Given the complexity of interactions between Resource API and the low-level APIs, I can't say that the behaviour shown in the tests gives any indication for what should or would be happening in a manual implementation of the low-level API. Dan33l as I already said on slack yesterday, I'm happy to answer specific questions there, and if they're recurring question I'll also make sure the answers get integrated into the existing docs, and that's all I can currently promise given staffing levels and company priorities. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42793.1587479580140%40Atlassian.JIRA.
Jira (PUP-10422) CentOS 8: group resource not able to handle group members
Title: Message Title Stephan Schultchen commented on PUP-10422 Re: CentOS 8: group resource not able to handle group members this bug can be closes. it is an issue in "sssd": https://bugzilla.redhat.com/show_bug.cgi?id=1794607 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.354501.1586253837000.42768.1587477540026%40Atlassian.JIRA.
Jira (PUP-10378) 'puppet resource service' does not return all active services on Ubuntu
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10378 'puppet resource service' does not return all active services on Ubuntu Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Consistency fix in puppet's behaviour when listing information about a single specific service and all available ones by showing services in a 'bad' state in both cases. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.350662.1584659329000.42762.1587476760029%40Atlassian.JIRA.
Jira (PUP-10422) CentOS 8: group resource not able to handle group members
Title: Message Title Stephan Schultchen commented on PUP-10422 Re: CentOS 8: group resource not able to handle group members sure: getent group puppetcerts puppetcerts:x:10053: but your question pointed me to another direction. our systems are enrolled to RedHat IdM/FreeIPA. so "sssd" is configured, and our /etc/nsswitch.conf is modifed. for some reason, CentOS 8 uses a different backend order, compared to CentOS7, in this file. CentOS 8 preferes sssd, not the local files. i will investigate, if something is wrong there. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.354501.1586253837000.42754.1587474900058%40Atlassian.JIRA.
Jira (PUP-8937) AIX package installation is not checking state of the package
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-8937 AIX package installation is not checking state of the package Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.259518.1528341085000.42753.1587474180284%40Atlassian.JIRA.
Jira (PUP-10422) CentOS 8: group resource not able to handle group members
Title: Message Title
Gabriel Nagy commented on PUP-10422
Re: CentOS 8: group resource not able to handle group members
Hi, Can you paste the output of getent group puppetcerts? This is what Puppet uses internally to get group information. If the group members aren't present in the output, it's possible that something takes precedence over files in /etc/nsswitch.conf. The implementation for this functionality is the same regardless of CentOS version. Attempting to reproduce on a CentOS 8 machine:
[root@payable-avocado puppet]# getent group wheel
wheel:x:10:root
[root@payable-avocado puppet]# bundle exec puppet resource group wheel
group { 'wheel':
ensure => 'present',
gid => 10,
members => ['root'],
provider => 'groupadd',
}
[root@payable-avocado puppet]# cat /etc/centos-release
Jira (PUP-10422) CentOS 8: group resource not able to handle group members
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-10422 CentOS 8: group resource not able to handle group members Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.354501.1586253837000.42741.1587473100031%40Atlassian.JIRA.
Jira (PUP-10352) Puppet agent total run time reported doesn't match time elapsed between Start and End event logs in Windows
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10352 Puppet agent total run time reported doesn't match time elapsed between Start and End event logs in Windows Change By: Mihai Buzgau Sprint: NW - 2020-03-17 , NW - 2020-04-29 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.347072.158219188.42655.1587463140034%40Atlassian.JIRA.
Jira (PUP-10378) 'puppet resource service' does not return all active services on Ubuntu
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10378 'puppet resource service' does not return all active services on Ubuntu Change By: Gabriel Nagy Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.350662.1584659329000.42620.1587458040124%40Atlassian.JIRA.
Jira (PUP-10408) Puppet .dmg packages fail on macOS 10.15
Title: Message Title Gheorghe Popescu commented on PUP-10408 Re: Puppet .dmg packages fail on macOS 10.15 Added release notes and moved this to resolved. Thank you Chris Miconi! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.354076.1585870709000.42609.1587456240081%40Atlassian.JIRA.
Jira (PUP-10408) Puppet .dmg packages fail on macOS 10.15
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10408 Puppet .dmg packages fail on macOS 10.15 Change By: Gheorghe Popescu Release Notes: Bug Fix Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.354076.1585870709000.42606.1587456180043%40Atlassian.JIRA.
Jira (PUP-10408) Puppet .dmg packages fail on macOS 10.15
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10408 Puppet .dmg packages fail on macOS 10.15 Change By: Gheorghe Popescu Release Notes Summary: Removed the '-noidme' flag with hdiutil when using pkgdmg package provider. In macOS 10.15 the '-noidme' flag causes hdiutil to output a deprecation warning, which then causes pkgdmg to fail to parse the plist xml that hdiutil generates, which then causes the package installation to fail in puppet. The '-noidme' flag is unnecessary for older versions of macOS as hdiutil does not perform idme actions by default. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.354076.1585870709000.42607.1587456180099%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356068.158739506.42581.1587454680143%40Atlassian.JIRA.
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title Dan33l commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider Question : Is it possible to forge a generic property with resource API ? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42545.1587452280029%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10351 Puppet Agent fails to self-restart on config change or update Change By: Mihai Buzgau Sprint: NW - 2020-04-01, NW - 2020-04-15 , NW - 2020-04-29 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.348520.1583329295000.42534.1587450300117%40Atlassian.JIRA.
Jira (FACT-2564) Facter 4 ZFS facts should match Facter 3 ZFS facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2564 Facter 4 ZFS facts should match Facter 3 ZFS facts Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356033.1587258664000.42532.1587450241768%40Atlassian.JIRA.
Jira (FACT-2564) Facter 4 ZFS facts should match Facter 3 ZFS facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2564 Facter 4 ZFS facts should match Facter 3 ZFS facts Change By: Mihai Buzgau Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356033.1587258664000.42533.1587450241823%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Change By: Mihai Buzgau Component/s: Facter 4 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356068.158739506.42529.1587449762521%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Change By: Mihai Buzgau Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356068.158739506.42531.1587449762620%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356068.158739506.42530.1587449762575%40Atlassian.JIRA.
