Project

General

Profile

Actions

Bug #56972

closed

cephadm: _no_schedule label doesn't work with explicit host placements

Added by Adam King over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

if you have a service spec that does placement by explicit hosts such as

service_type: mon
service_name: mon
placement:
  hosts:
  - vm-00
  - vm-01
  - vm-02

and then you add the _no_schedule label to a host specified in the spec, the daemon won't be removed from the host. Instead you'll end up hitting

2022-07-29T18:32:23.854135+0000 mgr.vm-00.aezdbv [ERR] Failed to apply mon spec ServiceSpec.from_json(yaml.safe_load('''service_type: mon
service_name: mon
placement:
  hosts:
  - vm-00
  - vm-01
  - vm-02
''')): Cannot place <ServiceSpec for service_name=mon> on vm-02: Unknown hosts

I think the expected behavior here should be to remove the daemon from the host and the "Unknown hosts" error should be only for cases where the user specifies a host in their spec that is not managed by cephadm.


Related issues 2 (0 open2 closed)

Copied to Orchestrator - Backport #57150: pacific: cephadm: _no_schedule label doesn't work with explicit host placementsRejectedAdam KingActions
Copied to Orchestrator - Backport #57151: quincy: cephadm: _no_schedule label doesn't work with explicit host placementsResolvedAdam KingActions
Actions #1

Updated by Adam King over 1 year ago

  • Pull request ID set to 47365
Actions #2

Updated by Adam King over 1 year ago

  • Status changed from In Progress to Pending Backport
Actions #3

Updated by Backport Bot over 1 year ago

  • Copied to Backport #57150: pacific: cephadm: _no_schedule label doesn't work with explicit host placements added
Actions #4

Updated by Backport Bot over 1 year ago

  • Copied to Backport #57151: quincy: cephadm: _no_schedule label doesn't work with explicit host placements added
Actions #5

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions #6

Updated by Adam King over 1 year ago

  • Backport changed from quincy, pacific to quincy
Actions #7

Updated by Adam King over 1 year ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF