Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title John Duarte updated an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: John Duarte QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title John Duarte updated an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: John Duarte QA Risk Assessment Reason: Revert of previous commit Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title John Duarte updated an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: Kylo Ginsberg Sprint: Client 2015-12-16 , Client 2015-12-30 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title
William Hopper commented on PUP-5549
Re: package version behavior for epoch versioned rpm's in centos is broken.
Eric Thompson right, that hasn't ever actually worked when specifying the epoch. Puppet has always sort of "accidentally" done the right thing when you don't include the epoch, where it grabs the version with the highest epoch. That's because of how Yum handles package versions passed in via the commandline.
Epoch handling was only attempted because of a bug report against the DNF provider, because DNF is slightly broken and requires you to specify the epoch when installing a package with an epoch, and thus puppet doesn't "accidentally" succeed to install such a package (see https://bugzilla.redhat.com/show_bug.cgi?id=1286877).
What's expected to work for the yum provider is:
puppet apply -e 'package {"mod_ssl": ensure=>"2.4.6-31.el7.centos.1"}'
RedHat is looking into the DNF bug, and when fixed the original problem should be solved. We aren't currently looking into doing epoch handling, as it hasn't been asked for specifically (it was only requested because of that bug)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title
Eric Thompson commented on PUP-5549
Re: package version behavior for epoch versioned rpm's in centos is broken.
William Hopper should specifying the epoch first: work on centos7 against master SHA: cb1e62b2d9ac2519020cb07380504cfa567c3745
[root@p9g9xqnxkx83g13 ~]# puppet apply -e 'package {"mod_ssl": ensure=>"1:2.4.6-31.el7.centos.1"}'
Notice: Compiled catalog for p9g9xqnxkx83g13.delivery.puppetlabs.net in environment production in 0.48 seconds
Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install mod_ssl-1:2.4.6-31.el7.centos.1' returned 1: Error: Nothing to do
Error: /Stage[main]/Main/Package[mod_ssl]/ensure: change from purged to 1:2.4.6-31.el7.centos.1 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install mod_ssl-1:2.4.6-31.el7.centos.1' returned 1: Error: Nothing to do
Notice: Applied catalog in 0.42 seconds
[root@p9g9xqnxkx83g13 ~]# puppet apply -e 'package {"mod_ssl": ensure=>"2.4.6-31.el7.centos.1"}'
Notice: Compiled catalog for p9g9xqnxkx83g13.delivery.puppetlabs.net in environment production in 0.44 seconds
Notice: /Stage[main]/Main/Package[mod_ssl]/ensure: created
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title William Hopper updated an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: William Hopper Release Notes Summary: The change made for PUP-5025 for installing packages versions with epochs using the DNF provider caused a regression when trying to do the same using the Yum provider. This change reverts the culprit commit. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: Michael Smith Status: Ready for CI Test Assignee: Kylo Ginsberg qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title William Hopper updated an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: William Hopper Story Points: 2 Sprint: Client 2015-12-16 Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title
William Hopper commented on PUP-5549
Re: package version behavior for epoch versioned rpm's in centos is broken.
I filed a bug against Fedora/DNF (https://bugzilla.redhat.com/show_bug.cgi?id=1286877) based on the weird behavior above. In the meantime, I again looked into what's going on under the hood that's making epochs a problem. It's pretty messy.
First of all, to clarify - the only reason we care at all about epochs is due to the issue described in
PUP-5025
, which I believe is only a problem due to the bug I filed. Since DNF forces you to include the epoch, puppet runs into trouble.
Digging into the RPM and Yum providers, it became clear that puppet is really not equipped to handle the optional epoch. We got around this historically due to the fact that Yum doesn't care if you specify the epoch or not, so users could do things like ensure => 1.2.3 for a package that really had the version 1:1.2.3. When querying for package versions (which happens in the RPM provider), we never returned the epoch (until the breaking change in
PUP-5025
):
def self.nevra_to_hash(line)
...
hash[:ensure] = "#{hash[:version]}-#{hash[:release]}"
...
end
This all means two things: first, that we've never been able to specify an epoch when using the yum provider, as we don't provide the arch field with it, so yum errors. Secondly, due to updates in DNF, you can now (and are required to) provide an epoch, but Puppet won't know about it when comparing the ensure value to the current package version. This
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title William Hopper commented on PUP-5549 Re: package version behavior for epoch versioned rpm's in centos is broken. Yep, this looks like an oversight based on the fix for PUP-5025 which was meant as an update for epoch handling using DNF, which seems to handle epochs differently when specifying versions to install. Examples: In Fedora 22, using DNF, the current version of the tomcat package is 1:7.0.59-4.fc22. When installing this specific version with DNF, you are required to provide the epoch via the commandline: root@sq9v8iq916gbork ~]# dnf install tomcat-1:7.0.59-4.fc22 Last metadata expiration check performed 1:54:33 ago on Mon Nov 30 11:40:05 2015. ... tomcat noarch 1:7.0.59-4.fc22 osmirror 91 k ... Transaction Summary = Install 31 Packages
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title William Hopper commented on PUP-5549 Re: package version behavior for epoch versioned rpm's in centos is broken. For posterity, the following are DNF commands which do and do not work when installing tomcat-1:7.0.59-4.fc22.noarch. Note that an RPM release string is represented as follows: name-[epoch:]version-release.arch tomcat-1:7.0.59-4.fc22 Thus, for tomcat we have: Name: tomcat epoch: 1 version: 7.0.59 release: 4.fc22 arch: noarch According to man DNF, the following are valid ways to install packages: · name.arch · name · name-[epoch:]version-release.arch
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title Josh Behrends commented on PUP-5549 Re: package version behavior for epoch versioned rpm's in centos is broken. Since DNF and YUM are two separate package providers shouldn't they have separate rules when it comes to package versioning for issues just like this? It feels like under the hood they are using the same code. I would think the same thing applies when we're talking YUM vs APT too. That's just my 2 cents without being knowledge about the code base. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title Kylo Ginsberg commented on PUP-5549 Re: package version behavior for epoch versioned rpm's in centos is broken. I'm +1 on reverting the epoch change for the time being, while we track down what DNF's intended behavior is. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title William Hopper commented on PUP-5549 Re: package version behavior for epoch versioned rpm's in centos is broken. Josh Behrends yum and dnf are nearly identical at this point, and both use our underlying RPM provider to work with the actual packages being moved around. At some point if things diverge, we may end up having to do some restructuring to separate the two. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title Josh Behrends created an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/11/25 10:41 AM Priority: Normal Reporter: Josh Behrends puppet-agent 1.3.0 CentOS 7 I just upgraded from puppet-agent 1.2.4 and all of a sudden I have multiple packages throwing the following notice every single puppet run: Notice: /Stage[main]/Logstash::Package/Logstash::Package::Install[logstash]/Package[logstash]/ensure: ensure changed '1:1.5.5-1' to '1.5.5-1' I'm not 100% positive, but it looks as though this change made be the culprit: https://tickets.puppetlabs.com/browse/PUP-5025 I tried adding the epoch to the begging of the version given to puppet and I get this:
