Backport "firefly" compatible ceph-deploy from 5.1+

Bug #1412827 reported by Denis Klepikov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
Undecided
Unassigned
4.1.x
Won't Fix
Low
MOS Linux
5.0.x
Won't Fix
Undecided
Unassigned
6.1.x
Invalid
Undecided
Unassigned

Bug Description

We need backport ceph 0.80.X "firefly" from fuel-repository.mirantis.com/fwm/6.0/ to fuel-repository.mirantis.com/fwm/4.X

If we use ceph 0.80.X "firefly" from fuel-repository.mirantis.com/fwm/6.0/ for updating ceph, deployed via fuel 4.0 we reach an error about OrderedDict

Temporary solution -
edit /usr/lib/python2.6/site-packages/ceph_deploy/conf/ceph.py
find
from collections import OrderedDict
and replace with
from ordereddict import OrderedDict
save /usr/lib/python2.6/site-packages/ceph_deploy/conf/ceph.py

Packets list to backport:
ceph-0.80.7
ceph-deploy-1.5.9
ceph-radosgw-0.80.7
libcephfs1-0.80.7
python-ceph-0.80.7
librbd1-0.80.7
librados2-0.80.7
ceph-common-0.80.7

Changed in mos:
milestone: none → 4.1.2
tags: added: customer-found
Changed in mos:
assignee: nobody → MOS Linux (mos-linux)
importance: Undecided → High
Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

4.x.x series has old Ceph 0.67.x branch. Are we going to introduce a major version update of Ceph in minor MOS release?

Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

Also, this seems to be related to ceph-deploy only, not the ceph itself?

Changed in mos:
status: New → Opinion
Revision history for this message
Denis Klepikov (dklepikov) wrote :

Yes, I edit just /usr/lib/python2.6/site-packages/ceph_deploy/conf/ceph.py related to ceph_deploy.
If backporting ceph_deploy will resolve an issue, then we can copy another RPMs from list above into 4.X repository.

Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

Then this is about ceph-deploy only, no need to fix something in ceph itself.

summary: - Backport ceph 0.80.X "firefly" from 6.0 to 4.X repository
+ Backport ceph-deploy 0.80.X "firefly" from 6.0 to 4.X repository
Changed in mos:
milestone: 4.1.2 → none
assignee: MOS Linux (mos-linux) → nobody
importance: High → Undecided
Changed in mos:
status: Opinion → Invalid
milestone: none → 6.1
summary: - Backport ceph-deploy 0.80.X "firefly" from 6.0 to 4.X repository
+ Backport "firefly" compatible ceph-deploy from 5.1+
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Backporting ceph-deploy from 5.1.x or later to MOS 4.1.x is risky and can introduce regressions for other users of 4.1.x who do not plan to upgrade their Ceph to 0.80.x. At the same time, as Alexander said, backporting Ceph 0.80.x itself to 4.1.x is definitely too intrusive a change to be considered for a backport at all.

All that being said, if the workaround described in bug description is sufficient to move forward with manual Ceph upgrade, I recommend closing this bug as Won't Fix for 4.1.x, it doesn't seem worth the risk and effort.

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Change abandoned on packages/centos6/ceph-deploy (4.1.2)

Change abandoned by Aleksandr Mogylchenko <email address hidden> on branch: 4.1.2
Review: https://review.fuel-infra.org/3932

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.