Back to bug 2086438
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-05-16 07:00:48 UTC | Link ID | Red Hat Issue Tracker RHCEPH-4312 | |
| Adam King | 2022-05-16 22:40:48 UTC | Status | NEW | ASSIGNED |
| Adam King | 2022-05-19 22:47:46 UTC | Status | ASSIGNED | POST |
| Ken Dreyer (Red Hat) | 2022-05-24 22:38:38 UTC | Status | POST | MODIFIED |
| Fixed In Version | ceph-16.2.8-4.el8cp | |||
| CC | kdreyer | |||
| errata-xmlrpc | 2022-05-24 23:39:53 UTC | Status | MODIFIED | ON_QA |
| Red Hat Bugzilla | 2022-05-26 08:30:32 UTC | CC | ceph-qe-bugs | |
| Ameena Suhani S H | 2022-06-01 04:41:50 UTC | QA Contact | sunnagar | mgowri |
| Manasa | 2022-06-01 12:51:57 UTC | CC | adrajiv | |
| QA Contact | mgowri | adrajiv | ||
| CC | mgowri | |||
| Red Hat Bugzilla | 2022-06-30 19:14:12 UTC | Status | ON_QA | VERIFIED |
| CC | adrajiv | |||
| QA Contact | adrajiv | mgowri | ||
| Akash Raj | 2022-07-29 06:02:14 UTC | Blocks | 2102272 | |
| Akash Raj | 2022-07-29 06:02:48 UTC | CC | adking, akraj | |
| Flags | needinfo?(adking) | |||
| Adam King | 2022-07-29 12:29:08 UTC | Flags | needinfo?(adking) | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Doc Text | Cause: cephadm would not remove the current active mgr even if it no longer matched the placement specified in the mgr service spec Consequence: if users changed the service spec to not include the host where the current active mgr is, they would end up with an extra mgr until they cause a mgr failover Fix: cephadm now fails over the mgr if a standby is avaialble and the active mgr is on a host that no longer matches the service spec. Result: cephadm will properly remove the mgr from a host no longer specified in the placement spec even if that mgr is the active one. Users should get the correct numberof mgr daemons in this scenario. |
|||
| Akash Raj | 2022-08-03 14:40:49 UTC | Flags | needinfo?(adking) | |
| Doc Text | Cause: cephadm would not remove the current active mgr even if it no longer matched the placement specified in the mgr service spec Consequence: if users changed the service spec to not include the host where the current active mgr is, they would end up with an extra mgr until they cause a mgr failover Fix: cephadm now fails over the mgr if a standby is avaialble and the active mgr is on a host that no longer matches the service spec. Result: cephadm will properly remove the mgr from a host no longer specified in the placement spec even if that mgr is the active one. Users should get the correct numberof mgr daemons in this scenario. | .The Ceph Manager daemon is removed from a host that is no longer specified in the placement specification in `cephadm` Previously, the current active manager daemon would not be removed from `cephadm` even if it no longer matched the placement specified in the manager service specification. Whenever users changed the service specification to exclude the host where the current active manager was, they would end up with an extra manager until they caused a failover. With this fix, `cephadm` fails over the manager if a standby is available and the active manager is on a host that no longer matches the service specification. Ceph Manager daemon is removed from a host that is no longer specified in the placement specification in `cephadm` even if the manager is the active one. |
||
| Adam King | 2022-08-03 17:14:30 UTC | Flags | needinfo?(adking) | |
| errata-xmlrpc | 2022-08-09 09:59:37 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:38:23 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-08-09 17:38:23 UTC | |||
| errata-xmlrpc | 2022-08-09 17:39:04 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2086438