Bug 457891 – upgrading lam-libs from RHEL4.6 to 4.7 failed.

Bug 457891 - upgrading lam-libs from RHEL4.6 to 4.7 failed.

Summary:	upgrading lam-libs from RHEL4.6 to 4.7 failed.

Status:	CLOSED CANTFIX

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	lam (Show other bugs)
Sub Component:
Version:	4.7
Hardware:	All Linux

Priority	medium Severity low
Target Milestone:	rc
Target Release:	---
Assigned To:	Doug Ledford
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-08-05 05:14 EDT by Kazuo Moriwaka
Modified:	2011-01-24 18:12 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-08-05 09:31:24 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Kazuo Moriwaka 2008-08-05 05:14:18 EDT

Description of problem:

When my customer upgrade lam-libs, it failed with following message.

error: %preun(lam-libs-7.1.2-8.i386) scriptlet failed, exit status 2
There was a fatal RPM install error. The message was:
Failed running rpm transaction


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

7.1.2-8 and 7.1.2-15

How reproducible:

always

Steps to Reproduce:
1. install 7.1.2-8
2. rpm -U 7.1.2-15

  
Actual results:
fail with above error.

Expected results:
updated.

Additional info:
When upgrade, 
7.1.2-15's %post remove mpilibsXX alternatives, after then,
7.1.2-8's %preun try to remove mpilibsXX alternatives, and it fails.

workaround: 
"rpm -e --nopreun lam-libs-7.1.2-8" after upgrade.

Comment 1 Doug Ledford 2008-08-05 09:31:24 EDT

This is a known issue for both lam and openmpi.  There was a specific release note related to this and how to work around the issue properly.  However, as the bug existed in the packages already on the system and not in the new packages, there was little to be done to resolve the situation.

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