Bug 605383
Summary: | Adding errata to cloned/custom channel (with pkg association unchecked) does not move all needed package arches | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Xixi <xdmoon> |
Component: | Server | Assignee: | Jan Pazdziora <jpazdziora> |
Status: | CLOSED ERRATA | QA Contact: | Šimon Lukašík <slukasik> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 530 | CC: | jhutar, msuchy, slukasik, tao, vgaikwad, xdmoon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-18 08:28:19 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: | 518253 |
Description
Xixi
2010-06-17 19:33:53 UTC
So during some testing myself, I discovered an issue with adding errata if the 'package association' checkbox is unchecked. So currently there are only two options: 1. Leave package association checked, it will handle arches correctly, but will not get all of the errata 2. Uncheck it. You will get all of the errata, but arches will not be handled correctly. Going to apply a fix to hopefully handle the arches better. -Justin commit to spacewalk master: 2d59d874019b71e66aff43e16cc28f831052d212 Hello Justin, I think I found problem with new set of packages. Can you take a look at the issue? Long story short: When added latest yum-rhn-plugin erratum which brings the new dependency on python-dmidecode. Package python-dmidecode is not added to the clone channel. But in the original channel there is erratum for it: RHEA-2009:9252 New package: python-dmidecode. Full reproducer: * sync rhel-i386-server-5 * clone rhel-i386-server-5 with all errata * remove 200 latest errata from clone * add following errata back to the clone: (with package association unchecked) RHSA-2010:0140 Moderate: pango security update RHEA-2010:9471 tzdata enhancement update RHBA-2010:9467 pam bug fix update RHSA-2010:9462 Moderate: httpd security and enhancement update RHBA-2010:9452 openmotif bug fix update RHBA-2009:9254 rhn-client-tools bug fix and enhancement update RHBA-2009:9279 iscsi-initiator-utils bug fix and enhancement update RHBA-2010:9353 Openswan bug fix update RHBA-2009:9247 NetworkManager bug fix and enhancement update RHBA-2009:1686 ksh bug fix update On the client you will get dependency problem: rhn-client-tools-0.4.20-33.el5.noarch from clone-2-rhel-i386-server-5 has depsolving problems --> Missing Dependency: python-dmidecode is needed by package rhn-client-tools-0.4.20-33.el5.noarch (clone-2-rhel-i386-server-5) 1:nfs-utils-1.0.9-42.el5.i386 from clone-2-rhel-i386-server-5 has depsolving problems --> Missing Dependency: libevent-1.1a.so.1 is needed by package 1:nfs-utils-1.0.9-42.el5.i386 (clone-2-rhel-i386-server-5) Error: Missing Dependency: libevent-1.1a.so.1 is needed by package 1:nfs-utils-1.0.9-42.el5.i386 (clone-2-rhel-i386-server-5) Error: Missing Dependency: python-dmidecode is needed by package rhn-client-tools-0.4.20-33.el5.noarch (clone-2-rhel-i386-server-5) Hey Simon, The errata add/remove tool does not do any sort of dependency checking, so it is up to the user to ensure everything is valid. Generally removing X newest errata will always be valid and adding X oldest available errata should be valid too, but picking and choosing certain errata to add will not always provide a working result. Since it looks like you are picking 'random' errata that aren't the oldest I am not surprised that there is a problem. Let me know if I've misunderstood what you are doing. Thanks! -Justin Hello Justin, I see and agree now. As this was the only problematic case I've found, moving to the verified. Thanks! Verified against: spacewalk-java-0.5.44-92 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0897.html |