Bug 809343 - update from f16 to f17 fails
Summary: update from f16 to f17 fails
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: openstack-swift
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alan Pevec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-03 07:09 UTC by Matthias Runge
Modified: 2012-04-03 16:46 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-03 16:46:42 UTC
Type: Bug

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

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.
Note You need to log in before you can comment on or make changes to this bug.