Back to bug 2187258
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-04-17 09:24:31 UTC | Link ID | Red Hat Issue Tracker RHCEPH-6469 | |
| Sayalee | 2023-04-17 09:24:59 UTC | Summary | [Dashboard] Standby MGR daemon not listed | Standby MGR daemon not listed in ceph -s command output |
| Sayalee | 2023-04-17 14:48:53 UTC | Target Release | 6.1z1 | 6.1 |
| Neha Ojha | 2023-05-01 21:08:08 UTC | Target Release | 6.1 | 6.1z1 |
| Pawan | 2023-07-10 03:04:03 UTC | CC | rzarzyns | |
| Flags | needinfo?(rzarzyns) | |||
| Radoslaw Zarzynski | 2023-07-10 07:28:58 UTC | Flags | needinfo?(rzarzyns) | |
| Radoslaw Zarzynski | 2023-07-11 19:55:38 UTC | Status | NEW | POST |
| Ken Dreyer (Red Hat) | 2023-07-20 18:46:03 UTC | CC | kdreyer | |
| Link ID | Github ceph/ceph/pull/51424 Ceph Project Bug Tracker 58379 | |||
| Fixed In Version | ceph-17.2.6-86 | |||
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-07-20 20:13:42 UTC | Status | MODIFIED | ON_QA |
| Akash Raj | 2023-07-25 04:53:09 UTC | Blocks | 2221020 | |
| Docs Contact | akraj | |||
| Flags | needinfo?(rzarzyns) | |||
| CC | akraj | |||
| Radoslaw Zarzynski | 2023-07-25 11:49:03 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Flags | needinfo?(rzarzyns) | |||
| Doc Text | Cause: If MonClient fails to authenticate with EAGAIN, there is a possibility it will reach prohibited state in which it does not have an active connection to ceph-mon neither tries further to acquire one. Consequence: Although technically still alive, ceph-mgr becomes invisible to monitors in the cluster. Fix: the EAGAIN during authentication is being handled properly now. |
|||
| Harsh Kumar | 2023-07-28 05:08:43 UTC | CC | hakumar | |
| Status | ON_QA | VERIFIED | ||
| Akash Raj | 2023-07-31 07:43:13 UTC | Doc Text | Cause: If MonClient fails to authenticate with EAGAIN, there is a possibility it will reach prohibited state in which it does not have an active connection to ceph-mon neither tries further to acquire one. Consequence: Although technically still alive, ceph-mgr becomes invisible to monitors in the cluster. Fix: the EAGAIN during authentication is being handled properly now. | .`MonClient` no longer fails to authenticate with `EAGAIN` Previously, if `MonClient` failed to authenticate with `EAGAIN`, there was a possibility that it would reach a prohibited state in which it did not have an active connection to `ceph-mon` and did not try further to acquire one. Due to this, even though the Ceph manager daemon is technically alive, it becomes invisible to monitors in the cluster. With this fix, the authentication with `EAGAIN` is handled properly and it works as expected. |
| Akash Raj | 2023-07-31 07:44:41 UTC | Doc Text | .`MonClient` no longer fails to authenticate with `EAGAIN` Previously, if `MonClient` failed to authenticate with `EAGAIN`, there was a possibility that it would reach a prohibited state in which it did not have an active connection to `ceph-mon` and did not try further to acquire one. Due to this, even though the Ceph manager daemon is technically alive, it becomes invisible to monitors in the cluster. With this fix, the authentication with `EAGAIN` is handled properly and it works as expected. | .`MonClient` no longer fails to authenticate with `EAGAIN` Previously, if `MonClient` failed to authenticate with `EAGAIN`, there was a possibility that it would reach a prohibited state in which it did not have an active connection to Ceph manager daemon and did not try further to acquire one. Due to this, even though the Ceph manager daemon is technically alive, it becomes invisible to monitors in the cluster. With this fix, the authentication with `EAGAIN` is handled properly and it works as expected. |
| Akash Raj | 2023-07-31 11:30:36 UTC | Doc Text | .`MonClient` no longer fails to authenticate with `EAGAIN` Previously, if `MonClient` failed to authenticate with `EAGAIN`, there was a possibility that it would reach a prohibited state in which it did not have an active connection to Ceph manager daemon and did not try further to acquire one. Due to this, even though the Ceph manager daemon is technically alive, it becomes invisible to monitors in the cluster. With this fix, the authentication with `EAGAIN` is handled properly and it works as expected. | .`MonClient` no longer fails to authenticate with `EAGAIN` Previously, if `MonClient` failed to authenticate with `EAGAIN`, there was a possibility that it would reach a prohibited state in which it would not have an active connection to `ceph-mon` and would not try further to acquire one. Due to this, even though the Ceph Manager daemon was technically alive, it became invisible to monitors in the cluster. With this fix, the authentication with `EAGAIN` is handled properly and it works as expected. |
| errata-xmlrpc | 2023-08-03 16:32:26 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-03 16:45:09 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-08-03 16:45:09 UTC | |||
| errata-xmlrpc | 2023-08-03 16:46:18 UTC | Link ID | Red Hat Product Errata RHBA-2023:4473 |
Back to bug 2187258