Bug 736194
Summary: | Upgrading dhcp, dhclient separately causes rpm file conflicts | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Garrett Holmstrom <gholms> |
Component: | dhcp | Assignee: | Jiri Popelka <jpopelka> |
Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | mganisin, ovasik |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | dhcp-4.1.1-23.P1.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 12:01:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 743047 |
Description
Garrett Holmstrom
2011-09-06 23:54:35 UTC
(In reply to comment #0) > F15 solved this by putting the shared files in a dhcp-common package > that both dhcp and dhclient Require with a full e-n-v-r. Right, the Fedora version of this problem was bug #634673. > Steps to Reproduce: > 1. Install a 6.1 system with dhclient-12:4.1.1-19.P1.el6 > 2. Run ``yum install dhcp'', then confirm the transaction Well, yes, it could be a problem. But it can't happen if the system is updated because then the installed dhclient is the same n-v-r as the installing dhcp. I'm not sure the fix (i.e. creating of new dhcp-common subpackage in the middle of RHEL-6 lifecycle) is better than this possible problem. New dhcp-common subpackage seems to me like a quite big change as a fix for problem that a user with updated system has no chance to see. But I have no other idea how to fix this (see bug #634673). I'll think about it a little but I see it as WONTFIX at the moment. (In reply to comment #2) > (In reply to comment #0) > > Steps to Reproduce: > > 1. Install a 6.1 system with dhclient-12:4.1.1-19.P1.el6 > > 2. Run ``yum install dhcp'', then confirm the transaction > > Well, yes, it could be a problem. > But it can't happen if the system is updated because then the installed > dhclient is the same n-v-r as the installing dhcp. I'm not sure the fix (i.e. > creating of new dhcp-common subpackage in the middle of RHEL-6 lifecycle) is > better than this possible problem. > New dhcp-common subpackage seems to me like a quite big change as a fix for > problem that a user with updated system has no chance to see. Since an update to either one would pull in the new dhcp-common subpackage, upgrades "just work" without changes to scripts or package lists. Likewise, it would have no effect on yum groups and kickstarts. Of course, if adding a new package is a problem in itself then that doesn't really help much. Just my two cents. ;) > But I have no other idea how to fix this (see bug #634673). Another possibility could be making dhcp Require dhclient with a full e-n-v-r, though I suspect that is not what you're after. If you can't do either of those, I suggest adding Conflicts entries to both packages as shown in comment 1 of bug #634673. This would have no effect on the normal case where versions match, but it would give yum the info it needs to reject such a transaction *before* it attempts to execute it rather than after it downloads everything and tries to change the system. (In reply to comment #3) > Since an update to either one would pull in the new dhcp-common subpackage, > upgrades "just work" without changes to scripts or package lists. Likewise, it > would have no effect on yum groups and kickstarts. Of course, if adding a new > package is a problem in itself then that doesn't really help much. Just my two > cents. ;) Well, it shouldn't actually be a problem. We'll consider this to include in 6.3 (it's quite late for 6.2). > Another possibility could be making dhcp Require dhclient with a full e-n-v-r, > though I suspect that is not what you're after. Definitely not. dhcp doesn't require dhclient. > If you can't do either of those, I suggest adding Conflicts entries to both > packages as shown in comment 1 of bug #634673. This would have no effect on > the normal case where versions match, but it would give yum the info it needs > to reject such a transaction *before* it attempts to execute it rather than > after it downloads everything and tries to change the system. Yes, but I'm not sure it's better because the error message is maybe more cryptic than what we have now. I'll be probably doing a re-spin because of another bug so I'll take this one in. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1597.html |