Bug 452213 - rpm unpack error installing the package: pvm-3.4.5-12.el4
rpm unpack error installing the package: pvm-3.4.5-12.el4
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: pvm (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Doug Ledford
Brian Brock
: Regression
Depends On:
  Show dependency treegraph
Reported: 2008-06-20 05:38 EDT by Alexander Todorov
Modified: 2008-07-24 16:00 EDT (History)
0 users

See Also:
Fixed In Version: RHBA-2008-0744
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-24 16:00:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexander Todorov 2008-06-20 05:38:19 EDT
Description of problem:
When upgrading from RHEL4.6 to RHEL4.7 unpacking of pvm package failed. This
causes the entire upgrade (up2date -fu) to exit with code of 1.
Subsequent run of up2date -fu shows other packages not upgraded.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install RHEL4.6 with pvm-3.4.4-21 (@everything)
2. Upgrade to RHEL4.7 via rhn.webqa (with up2date -fu)
Actual results:
Unpack error when installing pvm package. As a result the systems ends up with
missing pvm packages (old one removed and new one not installed due to error).

Actual error message:
 334:pvm                    ########################################### [100%]
error: unpacking of archive failed on file /usr/share/pvm3/bin/LINUXIA64: cpio:

Expected results:
pvm is upgraded to newer version

Additional info:
seeing this on ia64 and x86_64, not on ppc, s390*
Comment 5 Alexander Todorov 2008-06-20 07:41:09 EDT
Steps to Reproduce:
1. Install RHEL4.6 with pvm-3.4.4-21 (@everything)
2. Remove openmpi* and lam* packages (see bug #443795)
2. Upgrade to RHEL4.7 via rhn.webqa (with up2date -fu)
Comment 6 Doug Ledford 2008-06-20 11:53:08 EDT
OK, I can see why this is happening (and it makes me wonder how the rhel3
upgrade to pvm ever got through QA, it would have the same problem...but then
again this whole process has merely proven that the rhel3 pvm update was
partially complete at best).

I'm going to investigate an alternative fix for pvmgetarch...will update this
bug shortly.
Comment 7 Doug Ledford 2008-06-20 12:07:43 EDT
OK, I've created a patch to pvmgetarch that reverts the arch naming back to what
it was prior to this update, and I've eliminated the symlinks in the package
entirely.  The problem was that the symlinks couldn't be laid down during the
upgrade because valid directories with the same name already existed from the
package being upgraded, which happens because we install the new package
*before* we remove the old files from the old package, so those directories
where in the way.  With my new patch, it should go back to working like it did
prior to the update and use specific arch directories in all cases.
Comment 12 errata-xmlrpc 2008-07-24 16:00:33 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.