Red Hat Bugzilla – Bug 1350638
[RADOS]:[UPGRADE]: Apparent data loss after upgrading from 1.3.2 to 2.0 using "setuser match path" config
Last modified: 2017-07-30 11:14:21 EDT
We think this was due to me messing up the patch removing libradosstriper for https://bugzilla.redhat.com/show_bug.cgi?id=1339870 (there is no corresponding upstream bug). The next build should have it fixed.
The upgrade process doesn't look right to me, a restart of process is not sufficient after upgrade there could be old osd process still running, also is this a reason to run everything as root/root instead of ceph/ceph? the steps mentioned here are accurate: bz 1347395 which is yet to go into docs.
(In reply to Vasu Kulkarni from comment #5) > The upgrade process doesn't look right to me, a restart of process is not > sufficient after upgrade there could be old osd process still running, also > is this a reason to run everything as root/root instead of ceph/ceph? > > the steps mentioned here are accurate: bz 1347395 which is yet to go into > docs. @Vasu, Upgrade is actually done by tejas, I think he followed the proper docs for upgrade. It might be my mistake in the description.
Thanks shylesh, the ll still shows root/root for /var/lib/ceph in your earlier comment drwxr-xr-x. 3 root root 218 Jun 27 10:48 ceph-3
(In reply to Vasu Kulkarni from comment #7) > Thanks shylesh, the ll still shows root/root for /var/lib/ceph in your > earlier comment > > drwxr-xr-x. 3 root root 218 Jun 27 10:48 ceph-3 @Vasu, Yes that's the use case for "setuser match path = /var/lib/ceph/$type/$cluster-$id". Existing root owned dirs will remain as root and processes also runs as root. Any newly added osds after upgrade will run as ceph.
Verifid on RHEL7.2 ceph-common-10.2.2-9.el7cp.x86_64 and now rados tool works fine. Hence marking it as verified
*** Bug 1355958 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1755.html