Bug 2134135 - Ceph OSDs not being restarted after configuration change [NEEDINFO]
Summary: Ceph OSDs not being restarted after configuration change
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.0
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.3z2
Assignee: Teoman ONAY
QA Contact: Vivek Das
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-12 14:56 UTC by alisci
Modified: 2024-11-14 08:07 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-02-14 14:42:51 UTC
Embargoed:
alisci: needinfo? (tonay)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-5435 0 None None None 2022-10-12 15:03:28 UTC

Description alisci 2022-10-12 14:56:21 UTC
Description of problem:
When we update the ceph-ansible configuration and run a stack update, we expect to see all the Ceph OSDs being restarted in order to pick up the new configuration. In RHOSP 16.1 this is what we always observed. However in 16.2 this does not happen, and in order for changes to be picked up we must manually restart the containers.

Version-Release number of selected component (if applicable):
OSP 16.2.3
ceph-ansible-4.0.70.3-1.el8cp.noarch
ceph containers: rhceph/rhceph-4-rhel8 4-69.1638383142 ceph-base-14.2.11-208

How reproducible:
change a osd memory config by adding a template that uses CephAnsibleExtraConfig and osd_memory_target ; then do a deployment with that

parameter_defaults:
  CephAnsibleExtraConfig:
    osd_memory_target: 6123456789


Actual results:
despite the fact that after the deployment changes ar did at /etc/ceph/ceph.conf , new values for "osd memory target" are not applied and needed osd container to restart to having effect


Expected results:
after the deployment new config for osd should be active without their container restart, or some indications in the docs are needed if this is assumed to be an expected result


Additional info:


Note You need to log in before you can comment on or make changes to this bug.