Back to bug 1889976

Who When What Removed Added
Ernesto Puerta 2020-10-21 09:40:59 UTC Priority unspecified medium
Target Release 5.* 5.0
Whiteboard cephadm
Juan Miguel Olmo 2020-10-27 15:59:46 UTC CC jolmomar
Juan Miguel Olmo 2020-10-27 16:10:09 UTC Status NEW CLOSED
Resolution --- DUPLICATE
Last Closed 2020-10-27 16:10:09 UTC
Sunil Angadi 2021-07-13 10:53:10 UTC CC sangadi
QA Contact pnataraj sangadi
Sunil Angadi 2021-07-13 10:55:33 UTC Status CLOSED NEW
Target Release 5.0 5.1
Resolution DUPLICATE ---
Keywords Reopened
Sunil Angadi 2021-07-13 10:56:25 UTC Doc Type If docs needed, set a value Known Issue
Red Hat One Jira (issues.redhat.com) 2021-07-13 10:56:48 UTC Link ID Red Hat Issue Tracker RHCEPH-558
Sunil Angadi 2021-07-13 10:59:56 UTC CC epuertat
Flags needinfo?(epuertat)
Ernesto Puerta 2021-07-13 16:39:20 UTC CC athakkar
Flags needinfo?(epuertat) needinfo?(athakkar)
avan 2021-07-15 12:54:18 UTC CC nia
Flags needinfo?(athakkar) needinfo?(nia)
Nizamudeen 2021-07-15 13:07:30 UTC Doc Text Cause: If the host has any services running on it, then it is advised not to delete the host because the services won't get removed and it might lead to the buggy behaviour

Consequence: It might show the success notification the the host is removed but since some of the services in the hosts are not removed it'll still show in the list as kind of a 'dead host'

Workaround (if any): Before deleting a host you need to manually remove the services from that host. Once services are completely removed you can safely delete the host. If you removed the host without deleting the services first and you want to add the host again to the cluster, you may have to do it manually through CLI or Orch CLI.

Result: Host with services running is not safe to be removed. If removed, host will still show in the host list as a stale/dead/ghost host and can't be done any host related tasks or actions to it.
Flags needinfo?(nia) needinfo?(epuertat) needinfo?(athakkar)
avan 2021-07-15 14:03:35 UTC Flags needinfo?(athakkar)
Ernesto Puerta 2021-07-15 17:08:14 UTC Flags needinfo?(epuertat)
Sunil Angadi 2021-07-16 05:17:52 UTC Blocks 1959686
Sunil Angadi 2021-07-16 05:21:53 UTC CC rmandyam
Flags needinfo?(rmandyam)
Nizamudeen 2021-07-16 06:42:29 UTC Flags needinfo?(epuertat)
Nizamudeen 2021-07-16 06:42:49 UTC Flags needinfo?(rmandyam) needinfo?(epuertat)
Nizamudeen 2021-07-16 06:43:40 UTC Flags needinfo?(rmandyam)
Ranjini M N 2021-07-19 04:51:04 UTC Docs Contact asriram rmandyam
Ranjini M N 2021-07-19 08:45:30 UTC Doc Text Cause: If the host has any services running on it, then it is advised not to delete the host because the services won't get removed and it might lead to the buggy behaviour

Consequence: It might show the success notification the the host is removed but since some of the services in the hosts are not removed it'll still show in the list as kind of a 'dead host'

Workaround (if any): Before deleting a host you need to manually remove the services from that host. Once services are completely removed you can safely delete the host. If you removed the host without deleting the services first and you want to add the host again to the cluster, you may have to do it manually through CLI or Orch CLI.

Result: Host with services running is not safe to be removed. If removed, host will still show in the host list as a stale/dead/ghost host and can't be done any host related tasks or actions to it.
.Remove the services from the host before removing the hosts from the storage cluster on the {storage-product} Dashboard

Removing the hosts on the {storage-product} Dashboard before removing the services causes the hosts to be in a stale, dead, or a ghost state.

To workaround this issue, manually remove all the services running on the host and then remove the host from the storage cluster using the {storage-product} Dashboard.
If you remove the host without removing the services, then to add the host again, you will have to use the command-line interface.
If you remove the hosts without removing the services , you need to use the command-line interface to add the hosts again.
Flags needinfo?(rmandyam)
Ernesto Puerta 2021-11-04 09:48:27 UTC Status NEW ASSIGNED
Assignee epuertat nia
Red Hat One Jira (issues.redhat.com) 2021-11-04 09:49:08 UTC Link ID Red Hat Issue Tracker RHCSDASH-240
Ernesto Puerta 2021-11-11 11:16:13 UTC Target Release 5.1 5.2
Ernesto Puerta 2022-04-06 11:37:08 UTC Status ASSIGNED ON_QA
Sunil Angadi 2022-06-21 07:49:14 UTC CC tserlin
Fixed In Version ceph-16.2.8-30.el8cp
Status ON_QA VERIFIED
Akash Raj 2022-07-06 06:39:30 UTC CC akraj
Flags needinfo?(nia)
Akash Raj 2022-07-06 06:40:04 UTC Blocks 2102272
Nizamudeen 2022-07-06 06:54:39 UTC Doc Type Known Issue Bug Fix
Flags needinfo?(nia)
Doc Text .Remove the services from the host before removing the hosts from the storage cluster on the {storage-product} Dashboard

Removing the hosts on the {storage-product} Dashboard before removing the services causes the hosts to be in a stale, dead, or a ghost state.

To workaround this issue, manually remove all the services running on the host and then remove the host from the storage cluster using the {storage-product} Dashboard.
If you remove the host without removing the services, then to add the host again, you will have to use the command-line interface.
If you remove the hosts without removing the services , you need to use the command-line interface to add the hosts again.
Select the host to be removed and from the Edit Dropdown menu click on the Drain action. Wait until all the daemons in the host are removed safely.We can check the Daemons section in the Hosts details section to see the daemons. Once all the daemons are removed, we can proceed to remove the host by selecting the host and clicking the Remove option.
Akash Raj 2022-07-06 07:09:03 UTC Docs Contact rmandyam akraj
Nizamudeen 2022-07-12 05:37:26 UTC Doc Text Select the host to be removed and from the Edit Dropdown menu click on the Drain action. Wait until all the daemons in the host are removed safely.We can check the Daemons section in the Hosts details section to see the daemons. Once all the daemons are removed, we can proceed to remove the host by selecting the host and clicking the Remove option. Cause: Before removing a host, we need to remove the daemons manually from the host one by one.

Consequence: If you remove a host without moving out all the daemons, that host will go to an unusable state or a ghost state

Fix: A drain action is introduced in the table. Before removing the host user should do the drain and wait for all the daemons are moved out from the host

Result: Once drain is succeeded, the host can be safely removed
Akash Raj 2022-07-13 06:04:20 UTC Flags needinfo?(nia)
Doc Text Cause: Before removing a host, we need to remove the daemons manually from the host one by one.

Consequence: If you remove a host without moving out all the daemons, that host will go to an unusable state or a ghost state

Fix: A drain action is introduced in the table. Before removing the host user should do the drain and wait for all the daemons are moved out from the host

Result: Once drain is succeeded, the host can be safely removed
.Drain action on the Ceph dashboard ensures safe removal of host

Previously, whenever a user removed a host on the Ceph dashboard without moving out all the daemons, the host transitioned to an unusable state or a ghost state.

With this fix,users can use the drain action on the dashboard to move all the daemons out from the host. Upon successful completion of the drain action, the host can be safely removed.
Akash Raj 2022-07-14 03:43:19 UTC Flags needinfo?(nia)
errata-xmlrpc 2022-08-09 09:52:49 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2022-08-09 17:35:53 UTC Resolution --- ERRATA
Status RELEASE_PENDING CLOSED
Last Closed 2020-10-27 16:10:09 UTC 2022-08-09 17:35:53 UTC
errata-xmlrpc 2022-08-09 17:36:30 UTC Link ID Red Hat Product Errata RHSA-2022:5997

Back to bug 1889976