Back to bug 2024301
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2021-11-17 18:42:03 UTC | Link ID | Red Hat Issue Tracker RHCEPH-2368 | |
| Vikhyat Umrao | 2021-11-17 19:08:52 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Vikhyat Umrao | 2021-11-17 19:09:25 UTC | CC | adking | |
| Flags | needinfo?(adking) | |||
| Sunil Angadi | 2021-11-18 11:07:55 UTC | CC | sangadi | |
| Red Hat Bugzilla | 2022-01-31 23:32:04 UTC | Assignee | sewagner | adking |
| Ranjini M N | 2022-03-14 12:30:35 UTC | CC | rmandyam | |
| Flags | needinfo?(adking) | |||
| Karen Norteman | 2022-03-14 13:40:49 UTC | Docs Contact | knortema | asriram |
| Gaurav Sitlani | 2022-04-13 13:22:28 UTC | CC | gsitlani | |
| Sourav Jyoti Das | 2022-04-13 14:15:57 UTC | CC | sourdas | |
| Flags | needinfo?(adking) needinfo?(vumrao) | |||
| Vikhyat Umrao | 2022-04-13 16:05:30 UTC | Flags | needinfo?(vumrao) | |
| Sourav Jyoti Das | 2022-04-21 13:20:28 UTC | Flags | needinfo?(adking) | |
| Adam King | 2022-04-21 13:24:08 UTC | Flags | needinfo?(adking) needinfo?(adking) needinfo?(adking) needinfo?(adking) | |
| Adam King | 2022-05-11 14:09:16 UTC | Target Release | 5.2 | 6.1 |
| Sourav Jyoti Das | 2022-05-12 11:25:53 UTC | Flags | needinfo?(adking) | |
| Adam King | 2022-05-12 12:05:45 UTC | Flags | needinfo?(adking) | |
| Sourav Jyoti Das | 2022-05-12 15:10:17 UTC | Flags | needinfo?(adking) | |
| Adam King | 2022-05-12 15:37:57 UTC | Flags | needinfo?(adking) | needinfo?(sourdas) |
| Sourav Jyoti Das | 2022-05-12 15:53:06 UTC | Flags | needinfo?(sourdas) | |
| Sourav Jyoti Das | 2022-05-13 12:33:09 UTC | Flags | needinfo?(rmandyam) | |
| Ranjini M N | 2022-05-16 10:05:34 UTC | Flags | needinfo?(rmandyam) | |
| Sourav Jyoti Das | 2022-05-16 12:39:05 UTC | Blocks | 2086612 | |
| Red Hat Bugzilla | 2022-05-18 11:11:27 UTC | CC | gsitlani | |
| Adam King | 2022-05-19 22:51:55 UTC | Status | NEW | POST |
| Doc Text | Cause: There was a podman bug where adding the host with the active mgr to the cluster would cause the ip to resolve to a loopback address which would break things like the dashboard. Our initial response was to block adding the host with the active mgr without providing an explicit IP. That caused this bug where re-adding the active mgr host causes an error without an explicit IP being provided Consequence: If yo utry to add the host with the active mgr to the cluster without providing an explicit IP it will fail Workaround (if any): Provide an explicit IP when adding the host with the active mgr Result: If an explicit IP is provided adding/re-adding the host works fine. | |||
| Target Release | 6.1 | 5.2 | ||
| Veera Raghava Reddy | 2022-05-20 08:22:10 UTC | CC | vereddy | |
| Mary Frances Hull | 2022-05-23 11:33:16 UTC | Blocks | 2085458 | |
| Mary Frances Hull | 2022-05-23 11:58:08 UTC | CC | mhull | |
| Doc Text | Cause: There was a podman bug where adding the host with the active mgr to the cluster would cause the ip to resolve to a loopback address which would break things like the dashboard. Our initial response was to block adding the host with the active mgr without providing an explicit IP. That caused this bug where re-adding the active mgr host causes an error without an explicit IP being provided Consequence: If yo utry to add the host with the active mgr to the cluster without providing an explicit IP it will fail Workaround (if any): Provide an explicit IP when adding the host with the active mgr Result: If an explicit IP is provided adding/re-adding the host works fine. | .A bug in `podman` breaks components such as the dashboard while adding a host with an active Ceph Manager Due to a bug in `podman`, while adding a host with an active Ceph Manager to the storage cluster, the IP would resolve to a loopback address and would break components such as the dashboard. The workaround for this issue is to provide an explicit IP address when adding the host and it works as expected. |
||
| Ken Dreyer (Red Hat) | 2022-05-24 20:10:22 UTC | Fixed In Version | ceph-16.2.8-4.el8cp | |
| Status | POST | MODIFIED | ||
| CC | kdreyer | |||
| errata-xmlrpc | 2022-05-24 23:38:11 UTC | Status | MODIFIED | ON_QA |
| Ameena Suhani S H | 2022-06-01 04:41:50 UTC | QA Contact | sunnagar | mgowri |
| Pranav Prakash | 2022-06-01 05:28:57 UTC | CC | prprakas | |
| QA Contact | mgowri | prprakas | ||
| Manasa | 2022-06-01 12:49:14 UTC | CC | mgowri | |
| Pranav Prakash | 2022-06-20 06:13:51 UTC | Flags | needinfo?(adking) | |
| Adam King | 2022-06-20 15:14:24 UTC | Flags | needinfo?(adking) | |
| Pranav Prakash | 2022-06-21 08:41:14 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2022-07-06 07:19:23 UTC | Flags | needinfo?(adking) | |
| Docs Contact | asriram | akraj | ||
| CC | akraj | |||
| Blocks | 2102272 | |||
| Adam King | 2022-07-06 22:21:34 UTC | Flags | needinfo?(adking) | |
| Doc Text | .A bug in `podman` breaks components such as the dashboard while adding a host with an active Ceph Manager Due to a bug in `podman`, while adding a host with an active Ceph Manager to the storage cluster, the IP would resolve to a loopback address and would break components such as the dashboard. The workaround for this issue is to provide an explicit IP address when adding the host and it works as expected. | Cause: in an attempt to avoid an issue where if attempting to resolve the ip address of the host you are on from within a container would result in a loopback address, an explicit ip was required if re-adding the host with the active mgr. Consequence: users would receive an error message if trying to re-add the host containing the active mgr Fix: cephadm will now try to re-use the old ip when re-adding the host if it is not explicitly provided and name resolution returns a loopback address Result: users should now generally be able to re-add the host with the active mgr without needing to explicitly provide the ip. | ||
| Doc Type | Known Issue | Bug Fix | ||
| Akash Raj | 2022-07-13 06:14:32 UTC | Doc Text | Cause: in an attempt to avoid an issue where if attempting to resolve the ip address of the host you are on from within a container would result in a loopback address, an explicit ip was required if re-adding the host with the active mgr. Consequence: users would receive an error message if trying to re-add the host containing the active mgr Fix: cephadm will now try to re-use the old ip when re-adding the host if it is not explicitly provided and name resolution returns a loopback address Result: users should now generally be able to re-add the host with the active mgr without needing to explicitly provide the ip. | .Users can re-add host with an active manager without an explicit IP Previously, whenever a user attempted to resolve the IP address of the current host from within a container, it caused a loopback address. An explicit IP was required if the user wished to re-add the host with the active manager, resulting in users receiving an error message. With the current fix, `cephadm` reuses the old IP when re-adding the host if it is not explicitly provided and name resolution returns a loopback address. Users can now re-add the host with the active manager. |
| Flags | needinfo?(adking) | |||
| Adam King | 2022-07-13 12:40:09 UTC | Flags | needinfo?(adking) | |
| Doc Text | .Users can re-add host with an active manager without an explicit IP Previously, whenever a user attempted to resolve the IP address of the current host from within a container, it caused a loopback address. An explicit IP was required if the user wished to re-add the host with the active manager, resulting in users receiving an error message. With the current fix, `cephadm` reuses the old IP when re-adding the host if it is not explicitly provided and name resolution returns a loopback address. Users can now re-add the host with the active manager. | .Users can re-add host with an active manager without an explicit IP Previously, whenever cephadm attempted to resolve the IP address of the current host from within a container, there was a chance of it resolving to a loopback address. An explicit IP was required if the user wished to re-add the host with the active manager, and users would receive an error message if they did not provide it. With the current fix, `cephadm` reuses the old IP when re-adding the host if it is not explicitly provided and name resolution returns a loopback address. Users can now re-add the host with the active manager without an explicit IP. |
||
| Red Hat Bugzilla | 2022-07-15 19:04:47 UTC | CC | sourdas | |
| errata-xmlrpc | 2022-08-09 09:54:54 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-08-09 17:36:41 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2022-08-09 17:36:41 UTC | |||
| errata-xmlrpc | 2022-08-09 17:37:12 UTC | Link ID | Red Hat Product Errata RHSA-2022:5997 |
Back to bug 2024301