Bug 123319
Summary: | LTC8605-laus package prevents clean install of rhel3 u2 errata | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Bill Goodrich <billgo> | ||||
Component: | up2date | Assignee: | Adrian Likins <alikins> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fanny Augustin <fmoquete> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | CC: | bjohnson, borgan, ccb, dbukoske, jadb, jlaska, markwiz, shillman, tao, tos | ||||
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: | 2004-09-20 18:20:47 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: | 124236 | ||||||
Attachments: |
|
Description
Bill Goodrich
2004-05-17 01:45:39 UTC
This is a _different_ problem than in bug #123317? Is this a clean install of U2? If so, how? It looks like using NFS or FTP, not the ISOs, but I wanted to be sure. I've confirmed this behavior in our internal RHNQA environment using a fresh U2 install: > # up2date --showall | grep laus > laus-0.1-56RHEL3.s390x > laus-devel-0.1-56RHEL3.s390x > laus-libs-0.1-56RHEL3.s390 > laus-libs-0.1-56RHEL3.s390x > # The laus-0.1-56RHEL3.s390 package is missing from the above list; additionally, the downloads do not pull down the .s390 packages, just the s390x packages: > .qa.[root@byron root]# up2date -u laus laus-libs laus-devel > <...> > Name Version Rel > ---------------------------------------------------------- > laus 0.1 56RHEL3 s390x > laus-devel 0.1 56RHEL3 s390x > laus-libs 0.1 56RHEL3 s390x > > <...> > # ls /var/spool/up2date/laus-*rpm > laus-0.1-56RHEL3.s390x.rpm > laus-devel-0.1-56RHEL3.s390x.rpm > laus-libs-0.1-56RHEL3.s390x.rpm > # So there seem to be two issues in this report: 1) missing from the channel is laus-0.1-56RHEL3.s390 2) the downloads do not get the .s390 packages, just the s390x ones This is a clean install of U2 using a unified tree created from the ISOs. It was an NFS install. I was able to get past this by installing both variants of the laus- libs rpms. I had to pull the s390 rpm from RHN manually. I used rpm - U and had to specify --replacefiles to get past file conflicts with a prior version of laus. I was then able to complete the update. This workaround is not a solution. This is similar to 123317 but they are separate problems. The source of the problems is the laus-libs rpms. Created attachment 100563 [details]
shows laus issues
The problem is still present in the live RHN channel, attaching a text file
that shows the current state ...
re comment #4, what the problem in the channel? or the .s390 laus updates missing? I did a build of RHEL3 U2 GA. I registered with RHN and did an up2date -u up2date. I then tried to do an up2date -u to pull the errata from the channel. Here is the resuults. Note: I included an display of the up2date rpm level. RPM package conflict error. The message was: Test install failed because of package conflicts: The following packages were added to your selection to satisfy dependencies: Name Version Release -------------------------------------------------------------- laus-libs 0.1 56RHEL3 laus-libs 0.1 56RHEL3 file /lib/liblaus.so.1.0.0 from install of laus-libs-0.1-56RHEL3 conflicts with file from package laus-0.1-54RHEL3 file /lib/liblaussrv.so.0.0.0 from install of laus-libs-0.1-56RHEL3 conflicts with file from package laus-0.1-54RHEL3 [root@redhat4 root]# rpm -q up2date up2date-4.2.16-1 The problem is still present in the live RHN channel ... using internal test systems I am seeing the same behavior as in Bill's last comment (with the live channel) ... Updated up2date to: up2date-4.2.33-1 This did not help. Testing package set / solving RPM inter-dependencies... ######################################## RPM package conflict error. The message was: Test install failed because of package conflicts: The following packages were added to your selection to satisfy dependencies: Name Version Release -------------------------------------------------------------- laus-libs 0.1 56RHEL3 laus-libs 0.1 56RHEL3 file /lib/liblaus.so.1.0.0 from install of laus-libs-0.1-56RHEL3 conflicts with file from package laus-0.1-54RHEL3 file /lib/liblaussrv.so.0.0.0 from install of laus-libs-0.1-56RHEL3 conflicts with file from package laus-0.1-54RHEL3 Same as before. Adrian, I'm seeing this on x86_64 with up2date-4.2.33-1 as well as up2date-4.2.34-1. Appears that something doesn't realize there's a new laus available as well which resolves these conflicts. still busted on ppc (RHEL3-U2 -> up2date -fu) using up2date-4.2.33-1.ppc file /etc/init.d/audit from install of laus-0.1-62RHEL3 conflicts with file from package laus-0.1-56RHEL3 installed prior to update: laus-0.1-56RHEL3.ppc laus-0.1-56RHEL3.ppc64 laus-devel-0.1-56RHEL3.ppc laus-libs-0.1-56RHEL3.ppc laus-libs-0.1-56RHEL3.ppc64 attempting to update: laus 0.1 62RHEL3 ppc laus-devel 0.1 62RHEL3 ppc laus-libs 0.1 62RHEL3 ppc laus-libs 0.1 62RHEL3 ppc64 Looks like RHN is missing the laus.ppc64 package. Looks like we might need to add laus.pp64. I'll look at it here shortly. Crap. So, RHEA-2004:200-26 (the laus errata which went out right after U2) shipped with laus.ppc and laus.ppc64 (the only arch which shipped a multi-lib laus.) Net result is the above brokeness, and I think the best solution is going to be to just continue to ship laus.ppc64. Means that we need to update the U3 errata, as well as get the package pulled into the U3 builds. this fix is across all arches, please test with U3 gold once it goes live. This problem does not occur on RHEL3 U3 |