Bug 2112767 - [cephadm] "_no_schedule" label doesn't work with explicit host placement in the service spec.
Summary: [cephadm] "_no_schedule" label doesn't work with explicit host placement in t...
Keywords:
Status: CLOSED DUPLICATE of bug 2112768
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 5.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 6.1
Assignee: Adam King
QA Contact: Manasa
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-01 05:31 UTC by Mohit Bisht
Modified: 2022-12-06 11:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-01 05:39:41 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-4973 0 None None None 2022-08-01 05:41:21 UTC

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 ***
Note You need to log in before you can comment on or make changes to this bug.