[Ceph] Fuel must update (all) ceph.conf [mons] on ceph monitor re-deploy

Bug #1479862 reported by Miroslav Anashkin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Matthew Mosesohn
5.1.x
Won't Fix
High
MOS Maintenance
6.0.x
Won't Fix
High
MOS Maintenance
6.1.x
Won't Fix
High
MOS Maintenance
7.0.x
Won't Fix
High
MOS Maintenance

Bug Description

Usual scenario:

HA + Ceph MONs either on controllers or on separate nodes

One of controllers or Ceph MON nodes has failed and need re-deployment.

Customer deploys new controller.

However - /etc/ceph/ceph.conf is created in scope of primary controller/Ceph MON deployment only and remains untouched.

As a result - Ceph continue to complain about the missing Ceph monitor, since it remains in ceph.conf
New Ceph monitor is not deployed at all - since it does not exist in ceph.conf

Changed in fuel:
milestone: none → 7.0
assignee: nobody → Fuel Library Team (fuel-library)
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Please provide release version

Revision history for this message
Miroslav Anashkin (manashkin) wrote :

We encountered this issue with 6.0 at the customer side.
However - 6.1 and 7.0 still lacks this functionality as well.

Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Miroslav, let's wait for feedback from Ceph and Fuel teams but that looks like as feature request not a bug. I am not sure we should implement this in already released versions.

Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

We don't support master node updates in 5.1/5.1.1 and 6.0 maintenance updates. Setting to Invalid for 5.1.1 and 6.0 updates.

Revision history for this message
Andrew Woodward (xarses) wrote :

We need more information about what will occur if the monitors list is partially out of date (some are correct, some are not).

Is it warnings? performance deg?

Current description doesn't justify High

summary: - [Ceph] Fuel must update ceph.conf on ceph monitor re-deploy
+ [Ceph] Fuel must update (all) ceph.conf [mons] on ceph monitor re-deploy
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Marked as Confirmed for MOS 6.1 and MOS 7.0

Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Won't Fix for 5.1.1-updates and 6.0-updates because Fuel fixes cannot be delivered in maint updates for these version

Revision history for this message
Julia Portnova (yportnova) wrote :

Won't fix for 7.0

This fix requires a lot of changes as for each adding/deleting mon we need to update ceph.conf and restart all ceph-osds and mons on each nodes.

Changed in fuel:
status: Confirmed → Won't Fix
Roman Rufanov (rrufanov)
tags: added: support
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 7.0 → 8.0
status: Won't Fix → Confirmed
no longer affects: fuel/8.0.x
Revision history for this message
Kostiantyn Danylov (kdanylov) wrote :

Before restart osd need to set noout flag

# ceph osd set noout

After osd restarted this flag need to be removed

# ceph osd unset noout

Changed in fuel:
assignee: Kostiantyn Danylov (kdanylov) → Fuel Library Team (fuel-library)
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Matthew Mosesohn (raytrac3r)
Dmitry Pyzhov (dpyzhov)
tags: added: area-library
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

We can't fix ceph osd + controller combined very easily because that has a warning already:
"Ceph data still exists on: node-12. You must manually remove the OSDs from the cluster and allow Ceph to rebalance before deleting these nodes.
Deployment has failed. Method granular_deploy. Deployment failed on nodes 13.
Inspect Astute logs for the details"

I'll try to address the controller (with ceph mon) and separate OSD scenario

Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

Ceph conf on controllers (which run ceph-mon) remove deleted nodes from mon_host config correctly when we redeploy other controllers. There are no recurring messages about any missing nodes on removal of primary controller or deployment of additional controller. This bug is invalid for 8.0.

Changed in fuel:
status: Confirmed → Invalid
tags: added: wontfix-risky
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.