Red Hat Bugzilla – Bug 865867
gluster-swift upgrade to 3.3.1 wipes out proxy-server config
Last modified: 2015-10-22 11:40:20 EDT
Description of problem:
Upgrading gluster-swift from 3.3.0 to 3.3.1 wipes out at least one config file, without properly saving the original copy.
Steps to Reproduce:
1. Start with working gluster-swift running 3.3.0 from kkeithley's repo.
2. Issue 'yum upgrade' to upgrade to 3.3.1.
The proxy-server.conf file is overwritten with the default. A proxy-server.conf.rpmsave file is created, but it has the same contents as the .conf file. Any local changes are simply gone.
It should have left my config alone and created .rpmnew files.
Updating : glusterfs-swift-object-3.3.1-1.fc17.noarch 13/41
warning: /etc/swift/object-server/1.conf saved as /etc/swift/object-server/1.conf.rpmsave
Updating : glusterfs-swift-plugin-3.3.1-1.fc17.noarch 14/41
Updating : glusterfs-swift-account-3.3.1-1.fc17.noarch 15/41
warning: /etc/swift/account-server/1.conf saved as /etc/swift/account-server/1.conf.rpmsave
Updating : glusterfs-swift-container-3.3.1-1.fc17.noarch 16/41
warning: /etc/swift/container-server/1.conf saved as /etc/swift/container-server/1.conf.rpmsave
Updating : glusterfs-swift-proxy-3.3.1-1.fc17.noarch 17/41
warning: /etc/swift/proxy-server.conf saved as /etc/swift/proxy-server.conf.rpmsave
Comparing the entire /etc/swift directory with that on my other UFO server, only proxy-server.conf has changes, so I do not know why the 1.conf files were replaced/rpmsaved.
I'll take this one, as I need to solve this for my own testing when building from RPMs.
Upgrading from 3.3.1-1 to 3.3.1-2 just now also wiped out my config changes. This info is probably not going to change anything, just including it for completeness.
This will be resolved by this change out for review: http://review.gluster.org/4180
The changes have been merged to GlusterFS 3.3.1, please close the bug. This bug does not affect the new Gluster-for-Swift project.
pre-release version is ambiguous and about to be removed as a choice.
If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.