Bug 2290721

Summary:	[RFE] - Include the "ceph orch set-unmanaged" command to disable automatic management of daemon
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	skanta
Component:	Cephadm	Assignee:	Adam King <adking>
Status:	CLOSED ERRATA	QA Contact:	skanta
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	adking, cephqe-warriors, dwalveka, tserlin
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	6.1z9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-17.2.6-267.el9cp	Doc Type:	Enhancement
Doc Text:	”ceph orch set-unmanaged" and "ceph orch set-managed" commands are now available in Ceph 6.1z9 version Previously, moving services between managed and unmanaged states required manual modification of the specification files. With this enhancement, the ceph orch set-unmanaged and ceph orch set-managed commands are introduced. These commands allow services to transition between managed and unmanaged states without modifying the specification files. When a service is in the unmanaged state, cephadm will not automatically add or remove daemons or perform other background tasks. The primary use case for this enhancement is to move OSD services to the unmanaged state, ensuring that no new OSDs are deployed based on the OSD specification.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-04-28 05:29:46 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 skanta 2024-06-06 14:07:39 UTC

Description of problem:

Include the "ceph orch set-unmanaged" command to disable the automatic management of daemons. This option is available in reef(7.x) and not exists in the Quincy.

Quincy:
-------
[ceph: root@ceph-rados-auto-3io02f-node1-installer /]# ceph orch set-unmanaged mon
Invalid command: set-unmanaged not in start|stop|restart|redeploy|reconfig|rotate-key
orch <action:start|stop|restart|redeploy|reconfig|rotate-key> <service_name> :  Start, stop, restart, redeploy, or reconfig an entire service (i.e. all daemons)
Error EINVAL: invalid command
[ceph: root@ceph-rados-auto-3io02f-node1-installer /]#

Reef:
-----
[root@ceph-rados-tfa-vydyk9-node7 cephuser]# ceph orch set-unmanaged mgr
Set unmanaged to True for service mgr
[root@ceph-rados-tfa-vydyk9-node7 cephuser]# ceph orch set-managed mgr
Set unmanaged to False for service mgr
[root@ceph-rados-tfa-vydyk9-node7 cephuser]# ceph -v
ceph version 18.2.1-194.el9cp (04a992766839cd3207877e518a1238cdbac3787e) reef (stable)
[root@ceph-rados-tfa-vydyk9-node7 cephuser]#


Version-Release number of selected component (if applicable):
ceph version 17.2.6-216.el9cp (2787f204195806caaa97db2b363a263d5a9fa156) quincy (stable)



Additional info:

This option is available in the upstream Quincy documents.

Document link - https://docs.ceph.com/en/quincy/cephadm/services/

Comment 1 Adam King 2024-06-06 18:39:27 UTC

This has already been backported to quincy in the upstream via https://github.com/ceph/ceph/pull/50897 so it should make its way into the downstream on the next rebase we do.

Comment 2 skanta 2024-06-07 00:23:36 UTC

Hi Adam,

    Thanks for the information. The target release I assigned is 6.1z7. Please assign the correct target release if it is not 6.1z7.

Regards,
Bharath

Comment 3 Adam King 2024-06-07 13:01:51 UTC

(In reply to skanta from comment #2)
> Hi Adam,
> 
>     Thanks for the information. The target release I assigned is 6.1z7.
> Please assign the correct target release if it is not 6.1z7.
> 
> Regards,
> Bharath

setting it to 6.3 as we only rebase on point releases afaik

Comment 12 errata-xmlrpc 2025-04-28 05:29:46 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 (Important: Red Hat Ceph Storage 6.1 bug fix 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-2025:4238