Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2273066

Summary:	Return code for "ceph orch host maintenance enter <hostname>" is 0 on error
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Eric Smith <esmith>
Component:	Cephadm	Assignee:	Kushal Deb <kdeb>
Status:	CLOSED ERRATA	QA Contact:	Sayalee <saraut>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	cephqe-warriors, jcaratza, kdeb, saraut, vdas
Target Milestone:	---
Target Release:	9.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-20.1.0-13	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-01-29 06:47:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eric Smith 2024-04-03 20:50:07 UTC

Description of problem:
When rebooting a Ceph node, after setting the appropriate flags, we execute "cephadm shell -- ceph orch host maintenance enter <hostname>". If there is an problem entering maintenance mode for a specific node we would expect the cephadm call to have a return code other than 0 but it has a return code of 0 with an error in stderr.

Version-Release number of selected component (if applicable):
17.2.6-196.el9cp

How reproducible: 100%


Steps to Reproduce:
1. Set flags for reboot, "ceph osd set noout; ceph osd set norebalance"
2. Enter maintenance mode on node 1. 
3. Reboot node 1
4. Leave maintenance mode on node 1
5. Before Ceph daemons on node 1 are completely up, attempt to enter maintenance mode no node 2 with "ceph orch host maintenance enter node2"

Actual results:
Error in stderr and return code of 0

Expected results:
Error in stderr and return code other than 0

Additional info:
We're not sure if we need to wait for stderr to be empty, what errors to catch, how long to wait, etc. With a proper return code we can wait for a 0 and retry the maintenance on node2.

Comment 8 errata-xmlrpc 2026-01-29 06:47:56 UTC

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 (Moderate: Red Hat Ceph Storage 9.0 Security and Enhancement update), 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://access.redhat.com/errata/RHSA-2026:1536