Back to bug 2112768

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2022-08-01 05:41:45 UTC Link ID Red Hat Issue Tracker RHCEPH-4974
Mohit Bisht 2022-08-02 03:38:47 UTC Severity unspecified medium
Adam King 2022-08-17 18:35:06 UTC Target Release 6.1 6.0
Veera Raghava Reddy 2022-08-23 18:07:59 UTC CC vereddy
Adam King 2022-09-08 17:24:55 UTC Status NEW POST
errata-xmlrpc 2022-09-08 20:44:24 UTC Fixed In Version ceph-17.2.3-24.el9cp
CC tserlin
Status POST MODIFIED
Status MODIFIED ON_QA
Masauso Lungu 2022-09-09 10:25:34 UTC CC adking, mlungu
Flags needinfo?(adking)
Docs Contact asriram mlungu
Adam King 2022-09-09 16:00:18 UTC Flags needinfo?(adking)
Doc Type If docs needed, set a value Bug Fix
Doc Text Cause: The way cephadm handles explicit placements and host draining did not interact together properly

Consequence: Trying to drain a host that is listed as part of an explicit placement would cause the host to not be properly drained and tracebacks would be logged until the drain was stopped or the host was removed from any explicit placement

Fix: the handling of this was fixed internally so no exception occurs and cephadm is able to figure out it needs to remove daemons from the host

Result: users can now drain hosts that are listed in explicit placements without having to first remove the host from the placement. Users will still need to remove the host from any explicit placement before removing the host fully or the spec will be unable to be applied.
Mohit Bisht 2022-09-13 11:37:00 UTC QA Contact mgowri mobisht
Mohit Bisht 2022-09-16 08:12:08 UTC Status ON_QA VERIFIED
Masauso Lungu 2022-09-21 18:25:49 UTC Blocks 2126050
Masauso Lungu 2022-09-29 15:04:24 UTC Flags needinfo?(adking)
Doc Text Cause: The way cephadm handles explicit placements and host draining did not interact together properly

Consequence: Trying to drain a host that is listed as part of an explicit placement would cause the host to not be properly drained and tracebacks would be logged until the drain was stopped or the host was removed from any explicit placement

Fix: the handling of this was fixed internally so no exception occurs and cephadm is able to figure out it needs to remove daemons from the host

Result: users can now drain hosts that are listed in explicit placements without having to first remove the host from the placement. Users will still need to remove the host from any explicit placement before removing the host fully or the spec will be unable to be applied.
.Users can now drain hosts that are listed in explicit placements

Previously, draining hosts that were listed as part of an explicit placement would cause the hosts not to be properly drained and tracebacks would be logged until the drain was stopped or hosts were removed from any explicit placement .

With this fix, the handling of explicit placements is implemented internally and `cephadm` is able to determine if it needs to remove daemons from the hosts.
Consequently, users can now drain hosts that are listed as part of an explicit placement without having to first remove the host from the placement.

However, users still need to remove the host from any explicit placement before removing the host fully or the specification cannot be applied.
Adam King 2022-09-29 15:38:49 UTC Flags needinfo?(adking)
Doc Text .Users can now drain hosts that are listed in explicit placements

Previously, draining hosts that were listed as part of an explicit placement would cause the hosts not to be properly drained and tracebacks would be logged until the drain was stopped or hosts were removed from any explicit placement .

With this fix, the handling of explicit placements is implemented internally and `cephadm` is able to determine if it needs to remove daemons from the hosts.
Consequently, users can now drain hosts that are listed as part of an explicit placement without having to first remove the host from the placement.

However, users still need to remove the host from any explicit placement before removing the host fully or the specification cannot be applied.
.Users can now drain hosts that are listed in explicit placements

Previously, draining hosts that were listed as part of an explicit placement would cause the hosts not to be properly drained and tracebacks would be logged until the drain was stopped or hosts were removed from any explicit placement .

With this fix, the handling of explicit placements is implemented internally and `cephadm` is able to determine if it needs to remove daemons from the hosts.
Consequently, users can now drain hosts that are listed as part of an explicit placement without having to first remove the host from the placement.

However, users still need to remove the host from any explicit placement before removing the host fully or specifications that explicitly list the host cannot be applied.
Eliska 2022-10-18 12:23:37 UTC CC ekristov
Red Hat Bugzilla 2022-12-31 19:21:49 UTC QA Contact mobisht msaini
Red Hat Bugzilla 2023-01-01 05:37:21 UTC Assignee adking nobody
CC adking
Red Hat Bugzilla 2023-01-01 05:39:30 UTC CC tserlin
Red Hat Bugzilla 2023-01-01 08:37:17 UTC QA Contact msaini
Red Hat Bugzilla 2023-01-01 08:47:04 UTC CC vereddy
Alasdair Kergon 2023-01-04 04:33:20 UTC Assignee nobody adking
Alasdair Kergon 2023-01-04 04:38:28 UTC CC adking
Alasdair Kergon 2023-01-04 04:42:18 UTC QA Contact mobisht
Alasdair Kergon 2023-01-04 06:59:12 UTC CC vereddy
errata-xmlrpc 2023-03-20 18:38:11 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-03-20 18:57:13 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2023-03-20 18:57:13 UTC
errata-xmlrpc 2023-03-20 18:57:56 UTC Link ID Red Hat Product Errata RHBA-2023:1360

Back to bug 2112768