[Ceph] Do not restart Ceph service on new Ceph OSD node deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Bogdan Dobrelya | ||
5.1.x |
Invalid
|
High
|
MOS Maintenance | ||
6.0.x |
Invalid
|
High
|
MOS Maintenance |
Bug Description
The following improvement greatly increased the OSD deployment robustness
https:/
However, there is still one issue:
https:/
`Class[
`Class ceph::osds::osd` does both for each OSD , `ceph deploy osd prepare` and `ceph deploy osd activate`.
After that, Puppet code sends notification to Service['ceph']
As a result, Service['ceph'] is being restarted, followed by all deployed OSD restart on the entire node.
This step is not necessary, since all the related Ceph OSD services has been already started by `ceph deploy osd activate`.
It only creates huge load (especially in cases when OSD is added to long-existing cluster under the load) and may lead to unstable errors when particular OSD services fail to start.
In order to remove this service restart please change the problematic code line as following:
Class['ceph::conf'] -> Class['ceph::osds'] -> Service['ceph']
Changed in fuel: | |
importance: | Undecided → High |
milestone: | none → 7.0 |
assignee: | nobody → Fuel Library Team (fuel-library) |
Changed in fuel: | |
status: | New → Triaged |
tags: | added: on-verification |
tags: | added: customer-found support |
Fix proposed to branch: master /review. openstack. org/207761
Review: https:/