Bug 809343

Summary: update from f16 to f17 fails
Product: [Fedora] Fedora Reporter: Matthias Runge <mrunge>
Component: openstack-swiftAssignee: Alan Pevec <apevec>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: apevec, apevec, breu, david, jonathansteffan, markmc, rbryant, silas, zaitcev
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-03 16:46:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthias Runge 2012-04-03 07:09:07 UTC
Description of problem:
when openstack-swift is installed, upgrade from f16 to f17 using networkk-install/DVD fails, leaving system in unbootable state.

last messages from upgrade log before updater exits:

error reading information on service swift-auth: No such file or directory
error: %preun(openstack-swift-auth-1.4.0-2.fc16.noarch) scriptlet failed, exit status 1

Comment 1 Alan Pevec 2012-04-03 09:40:26 UTC
(In reply to comment #0)
> error reading information on service swift-auth: No such file or directory
> error: %preun(openstack-swift-auth-1.4.0-2.fc16.noarch) scriptlet failed

Latest in f16 stable updates is openstack-swift-1.4.6-2.fc16, please update before upgrade.

Comment 2 Matthias Runge 2012-04-03 14:37:55 UTC
I might be wrong, but wouldn't preun be handled by the to be uninstalled rpm? So, this is an error in version 1.4.0-2; The error would also occur during update to 1.4.6-2, but this probably wouldn't kill the upgrade.

Sadly, I had to do a fresh install of fedora 17 on this system, I don't have the possibility to experiment with other f16 versions of openstack-swift.

Comment 3 Alan Pevec 2012-04-03 16:46:42 UTC
(In reply to comment #2)
> but this probably wouldn't kill the upgrade.

Exactly! We can't fix already published NVR.