Bug #4424
closed
ceph-mds.conf fails to upgrade from ceph 0.56.3 to 0.58-487
Added by Ken Franklin about 11 years ago.
Updated about 11 years ago.
Description
upgrading from a previous version of Ceph fails with errors when overwritting ceph-mds.conf. This occured on the system I use to test the Master branch (burnupi60). Every morning the following is executed:
sudo apt-get -y update
sudo apt-get -y upgrade
The upgrade fails with the following messages:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
ceph linux-headers-server linux-image-server linux-server
The following packages will be upgraded:
ceph-common ceph-fs-common ceph-fuse ceph-mds icedtea-6-jre-cacao icedtea-6-jre-jamvm librados2 librbd1 openjdk-6-jdk
openjdk-6-jre openjdk-6-jre-headless openjdk-6-jre-lib radosgw
13 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
25 not fully installed or removed.
Need to get 0 B/56.1 MB of archives.
After this operation, 463 kB of additional disk space will be used.
(Reading database ... 64884 files and directories currently installed.)
Preparing to replace ceph-mds 0.56.3-1precise (using .../ceph-mds_0.58-487-g34f1984-1precise_amd64.deb) ...
Unpacking replacement ceph-mds ...
dpkg: error processing /var/cache/apt/archives/ceph-mds_0.58-487-g34f1984-1precise_amd64.deb (--unpack):
trying to overwrite '/etc/init/ceph-mds.conf', which is also in package ceph 0.56.3-1precise
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for ureadahead ...
Errors were encountered while processing:
/var/cache/apt/archives/ceph-mds_0.58-487-g34f1984-1precise_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Files
- Status changed from New to In Progress
This problem is happening because /etc/init/ceph-mds.conf is in the ceph package in bobtail and in the ceph-mds package in master.
Still working on a solution.
The bigger hammer workaround is:
apt-get -o Dpkg::Options::="--force-overwrite" upgrade
Alternatively removing bobtail, then installing the newer master branch version works.
I'll continue looking for a solution that can perhaps be implemented in the packaging.
I've added a replaces/breaks ceph statement to the debian control file for the ceph-mds package. This is currently in the wip-4424 branch. This effectively causes ownership of the ceph-mds.conf file to transfer from the ceph package to the ceph-mds pacakge during the upgrade. However, because the dependencies between the packages has changed one must use "apt-get dist-upgrade" instead of "apt-get upgrade".
I've tried the wip-4424 branch and the update goes ok.
There are other issues now: ceph-mds doesn't start. I get "mds laggy or crashed" in response to ceph health. The mds log has "wrong node" messages. I've attached the ceph-mds.log file - log messages after 2013-03-13 11:05 reflect the wip-4424 bringup.
I'm confused now. My upgrade from bobtail (0.56.3) to latest master is working fine with just apt-get upgrade. Before the upgrade ceph-mon.conf is shown belonging to ceph, and after it belongs to ceph-mds, and no complaints about overwriting files.
My upgrade this morning did pick up a new version of apt:
Get:10 http://archive.ubuntu.com/ubuntu/ precise-updates/main apt amd64 0.8.16~exp12ubuntu10.9 [1,101 kB]
Get:11 http://archive.ubuntu.com/ubuntu/ precise-updates/main libapt-inst1.4 amd64 0.8.16~exp12ubuntu10.9 [99.8 kB]
Get:12 http://archive.ubuntu.com/ubuntu/ precise-updates/main apt-utils amd64 0.8.16~exp12ubuntu10.9 [190 kB]
Get:13 http://archive.ubuntu.com/ubuntu/ precise-updates/main apt-transport-https amd64 0.8.16~exp12ubuntu10.9 [16.3 kB]
There do not appear to be any commits to bobtail or master that would affect the packaging, so maybe the change in behaviour is the new apt.
after restarting I'm left with these "ceph" processes running:
0 S ubuntu 27465 26879 0 80 0 - 2026 pipe_w 13:50 pts/3 00:00:00 grep --color=auto ceph
1 S root 40490 1 0 80 0 - 42390 futex_ 11:07 ? 00:00:14 /usr/bin/ceph-mon -i a --pid-file /var/run/ceph/mon.a.pid -c /etc/ceph/ceph.conf
0 S root 40504 1 0 80 0 - 11315 poll_s 11:07 pts/0 00:00:08 /usr/bin/python /usr/sbin/ceph-create-keys -i a
1 S root 40958 1 0 80 0 - 156037 futex_ 11:07 ? 00:00:19 /usr/bin/ceph-osd -i 0 --pid-file /var/run/ceph/osd.0.pid -c /etc/ceph/ceph.conf
1 S root 41193 1 0 80 0 - 158900 futex_ 11:07 ? 00:00:19 /usr/bin/ceph-osd -i 1 --pid-file /var/run/ceph/osd.1.pid -c /etc/ceph/ceph.conf
The ceph-create-keys process is the one I don't usually see. is that a clue to what's happening?
Sam suggested this new situation is a separate bug. I'll open an different case to track.
- Status changed from In Progress to Resolved
Fixed with the following commit:
commit 6f15dba93199fe79b83c69f50faeb276059f54f2
Author: Gary Lowell <glowell@inktank.com>
Date: Tue Mar 12 16:59:42 2013 -0700
debian/control: Fix for moved file
The ceph-mds.conf file moved from the ceph package to the
ceph-mds package. Add replaces/breaks statements to the
control file to handle this on upgrade.
Signed-off-by: Gary Lowell <gary.lowell@inktank.com>
Also available in: Atom
PDF