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 2112767

Summary:	[cephadm] "_no_schedule" label doesn't work with explicit host placement in the service spec.
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Mohit Bisht <mobisht>
Component:	Cephadm	Assignee:	Adam King <adking>
Status:	CLOSED DUPLICATE	QA Contact:	Manasa <mgowri>
Severity:	medium	Docs Contact:	Anjana Suparna Sriram <asriram>
Priority:	unspecified
Version:	5.2	CC:	cephqe-warriors, vereddy
Target Milestone:	---
Target Release:	6.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-01 05:39:41 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 Mohit Bisht 2022-08-01 05:31:55 UTC

Description of problem:
- "_no_schedule" label doesn't work with explicit host placement in the service spec.

Version-Release number of selected component (if applicable):
- ceph version 16.2.8-82.el8cp (697566304d26433e611f76087112abfe6777ad1d) pacific (stable)

How reproducible:
Always

Steps to Reproduce:
1. Deploy ceph using cephadm
2. Add mon host explicitly in the service spec.
3. Add "_no_schedule" label to the mon host added explicitly in the service spec. 

Actual results:
Mon daemon of specific host with "_no_schedule" label not moved/removed from the cluster other than OSD.

Expected results:
All daemons except OSD must be moved/removed

Additional info:
when "mon" label used for placement in the service spec, "_no_schedule" label working as expected.

Comment 1 RHEL Program Management 2022-08-01 05:32:06 UTC

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 2 Mohit Bisht 2022-08-01 05:39:41 UTC

Duplicate bug, hence closing

*** This bug has been marked as a duplicate of bug 2112768 ***