Back to bug 2121265
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Prashant Dhange | 2022-08-25 02:51:38 UTC | Assignee | nojha | pdhange |
| Status | NEW | ASSIGNED | ||
| Red Hat One Jira (issues.redhat.com) | 2022-08-25 02:54:56 UTC | Link ID | Red Hat Issue Tracker RHCEPH-5144 | |
| Prashant Dhange | 2022-09-08 05:19:12 UTC | Status | ASSIGNED | POST |
| Prashant Dhange | 2022-09-08 05:54:05 UTC | Flags | needinfo?(pdhange) | |
| Flags | needinfo?(pdhange) | |||
| Pawan | 2022-09-09 03:55:16 UTC | Fixed In Version | ceph-17.2.3-22.el9cp | |
| Status | POST | MODIFIED | ||
| Flags | needinfo?(pdhiran) | |||
| Flags | needinfo?(vereddy) | |||
| Flags | needinfo?(pdhiran) | |||
| Pawan | 2022-09-09 03:55:41 UTC | Flags | needinfo?(vereddy) | |
| errata-xmlrpc | 2022-09-09 05:14:33 UTC | Status | MODIFIED | ON_QA |
| Masauso Lungu | 2022-09-09 10:23:42 UTC | Docs Contact | mlungu | |
| CC | mlungu | |||
| Flags | needinfo?(pdhange) | |||
| Prashant Dhange | 2022-09-14 06:15:19 UTC | Flags | needinfo?(pdhange) | needinfo?(mlungu) |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Doc Text | Cause: The prometheus metrics fails to report correct ceph version for MON if MON has been upgraded. Consequence: The active MGR daemon needs to be restarted to resolve this inconsistency. Fix: The mgr updates mon metadata through handle_mon_map which gets triggered when MONs were removed/added from/to cluster or the active mgr is restarted or mgr failsover. Instead of relying on fetching mon metadata using 'ceph mon metadata ' command, explicitly send metadata update request with mon metadata to mgr. Result: The prometheus metrics reflects the correct ceph version for all MONs whenever requested. |
|||
| Masauso Lungu | 2022-09-21 18:25:49 UTC | QA Contact | pdhiran | skanta |
| Blocks | 2126050 | |||
| Masauso Lungu | 2022-09-27 08:58:24 UTC | Status | ON_QA | VERIFIED |
| Doc Text | Cause: The prometheus metrics fails to report correct ceph version for MON if MON has been upgraded. Consequence: The active MGR daemon needs to be restarted to resolve this inconsistency. Fix: The mgr updates mon metadata through handle_mon_map which gets triggered when MONs were removed/added from/to cluster or the active mgr is restarted or mgr failsover. Instead of relying on fetching mon metadata using 'ceph mon metadata ' command, explicitly send metadata update request with mon metadata to mgr. Result: The prometheus metrics reflects the correct ceph version for all MONs whenever requested. | .The Prometheus metrics now reflect the correct Ceph version for all Ceph Monitors whenever requested Previously, the Prometheus metrics reported mismatched Ceph versions for Ceph Monitors when the monitor was upgraded. As a result, the active Ceph Manager daemon needed to be restarted to resolve this inconsistency. With this fix, the Ceph Manager updates the monitor metadata through `handle_mon_map` parameter, which gets triggered when the monitors are removed or added from the cluster or the active `mgr` is restarted or `mgr` failsover. Instead of relying on fetching `mon` metadata using `ceph mon metadata` command, you can explicitly send metadata update requests with `mon` metadata to `mgr`. | ||
| Flags | needinfo?(mlungu) | needinfo?(pdhange) | ||
| Prashant Dhange | 2022-10-10 05:00:19 UTC | Flags | needinfo?(pdhange) | needinfo?(mlungu) |
| Doc Text | .The Prometheus metrics now reflect the correct Ceph version for all Ceph Monitors whenever requested Previously, the Prometheus metrics reported mismatched Ceph versions for Ceph Monitors when the monitor was upgraded. As a result, the active Ceph Manager daemon needed to be restarted to resolve this inconsistency. With this fix, the Ceph Manager updates the monitor metadata through `handle_mon_map` parameter, which gets triggered when the monitors are removed or added from the cluster or the active `mgr` is restarted or `mgr` failsover. Instead of relying on fetching `mon` metadata using `ceph mon metadata` command, you can explicitly send metadata update requests with `mon` metadata to `mgr`. | .The Prometheus metrics now reflect the correct Ceph version for all Ceph Monitors whenever requested Previously, the Prometheus metrics reported mismatched Ceph versions for Ceph Monitors when the monitor was upgraded. As a result, the active Ceph Manager daemon needed to be restarted to resolve this inconsistency. The Ceph Manager used to update the monitor metadata through `handle_mon_map` parameter, which gets triggered when the monitors are removed or added from the cluster or the active `mgr` is restarted or `mgr` failsover. With this fix, Instead of relying on fetching `mon` metadata using `ceph mon metadata` command, MON now explicitly send metadata update requests with `mon` metadata to `mgr`. |
||
| Masauso Lungu | 2022-10-11 11:18:01 UTC | Flags | needinfo?(mlungu) | |
| Masauso Lungu | 2022-10-13 13:30:03 UTC | Flags | needinfo?(pdhange) | |
| Doc Text | .The Prometheus metrics now reflect the correct Ceph version for all Ceph Monitors whenever requested Previously, the Prometheus metrics reported mismatched Ceph versions for Ceph Monitors when the monitor was upgraded. As a result, the active Ceph Manager daemon needed to be restarted to resolve this inconsistency. The Ceph Manager used to update the monitor metadata through `handle_mon_map` parameter, which gets triggered when the monitors are removed or added from the cluster or the active `mgr` is restarted or `mgr` failsover. With this fix, Instead of relying on fetching `mon` metadata using `ceph mon metadata` command, MON now explicitly send metadata update requests with `mon` metadata to `mgr`. | .The Prometheus metrics now reflect the correct Ceph version for all Ceph Monitors whenever requested Previously, the Prometheus metrics reported mismatched Ceph versions for Ceph Monitors when the monitor was upgraded. As a result, the active Ceph Manager daemon needed to be restarted to resolve this inconsistency. Additionally, the Ceph manager used to update the monitor metadata through the `handle_mon_map` parameter, which gets triggered when the monitors are removed or added from the cluster or the active `mgr` is restarted or `mgr` failsover. |
||
| Prashant Dhange | 2022-10-13 13:59:28 UTC | Flags | needinfo?(pdhange) | |
| Red Hat Bugzilla | 2022-12-31 19:09:47 UTC | CC | skanta | |
| QA Contact | skanta | pdhiran | ||
| Red Hat Bugzilla | 2022-12-31 19:13:25 UTC | CC | amathuri | |
| Red Hat Bugzilla | 2022-12-31 19:32:32 UTC | CC | pdhiran | |
| QA Contact | pdhiran | |||
| Red Hat Bugzilla | 2022-12-31 19:59:56 UTC | CC | sseshasa | |
| Red Hat Bugzilla | 2022-12-31 22:43:28 UTC | CC | rfriedma | |
| Red Hat Bugzilla | 2022-12-31 23:43:30 UTC | CC | rzarzyns | |
| Red Hat Bugzilla | 2022-12-31 23:45:50 UTC | CC | akupczyk | |
| Red Hat Bugzilla | 2023-01-01 05:35:17 UTC | CC | ksirivad | |
| Red Hat Bugzilla | 2023-01-01 05:39:34 UTC | CC | tserlin | |
| Red Hat Bugzilla | 2023-01-01 06:01:51 UTC | CC | bniver | |
| Red Hat Bugzilla | 2023-01-01 06:03:26 UTC | CC | kdreyer | |
| Red Hat Bugzilla | 2023-01-01 06:27:06 UTC | CC | lflores | |
| Red Hat Bugzilla | 2023-01-01 06:28:59 UTC | CC | choffman | |
| Red Hat Bugzilla | 2023-01-01 08:38:27 UTC | CC | nojha | |
| Red Hat Bugzilla | 2023-01-01 08:39:28 UTC | CC | pdhange | |
| Assignee | pdhange | nobody | ||
| Red Hat Bugzilla | 2023-01-01 08:40:50 UTC | CC | sangadi | |
| Red Hat Bugzilla | 2023-01-01 08:42:34 UTC | CC | sostapov | |
| Red Hat Bugzilla | 2023-01-01 08:47:11 UTC | CC | vereddy | |
| Red Hat Bugzilla | 2023-01-01 08:49:49 UTC | CC | vumrao | |
| Alasdair Kergon | 2023-01-04 04:40:45 UTC | CC | akupczyk | |
| Alasdair Kergon | 2023-01-04 04:43:34 UTC | CC | amathuri | |
| Alasdair Kergon | 2023-01-04 04:49:11 UTC | Assignee | nobody | pdhange |
| Alasdair Kergon | 2023-01-04 04:55:59 UTC | QA Contact | skanta | |
| Alasdair Kergon | 2023-01-04 05:03:42 UTC | CC | kdreyer | |
| Alasdair Kergon | 2023-01-04 05:08:58 UTC | CC | ksirivad | |
| Alasdair Kergon | 2023-01-04 05:10:58 UTC | CC | lflores | |
| Alasdair Kergon | 2023-01-04 05:21:38 UTC | CC | nojha | |
| Alasdair Kergon | 2023-01-04 05:28:18 UTC | CC | pdhange | |
| Alasdair Kergon | 2023-01-04 05:30:13 UTC | CC | pdhiran | |
| Alasdair Kergon | 2023-01-04 05:34:52 UTC | CC | rfriedma | |
| Alasdair Kergon | 2023-01-04 05:37:37 UTC | CC | rzarzyns | |
| Alasdair Kergon | 2023-01-04 05:39:59 UTC | CC | sangadi | |
| Alasdair Kergon | 2023-01-04 05:41:45 UTC | CC | skanta | |
| Alasdair Kergon | 2023-01-04 05:43:50 UTC | CC | sostapov | |
| Alasdair Kergon | 2023-01-04 05:59:30 UTC | CC | vumrao | |
| Alasdair Kergon | 2023-01-04 06:11:25 UTC | CC | bniver | |
| Alasdair Kergon | 2023-01-04 06:13:47 UTC | CC | choffman | |
| Alasdair Kergon | 2023-01-04 06:56:31 UTC | CC | sseshasa | |
| Alasdair Kergon | 2023-01-04 06:59:12 UTC | CC | vereddy | |
| Red Hat Bugzilla | 2023-01-09 08:28:04 UTC | CC | ceph-eng-bugs | |
| Alasdair Kergon | 2023-01-09 19:43:36 UTC | CC | ceph-eng-bugs | |
| Red Hat Bugzilla | 2023-01-31 23:37:08 UTC | CC | madam | |
| Red Hat Bugzilla | 2023-02-28 18:56:25 UTC | CC | ngangadh | |
| errata-xmlrpc | 2023-03-20 18:38:25 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-03-20 18:57:23 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-03-20 18:57:23 UTC | |||
| errata-xmlrpc | 2023-03-20 18:58:05 UTC | Link ID | Red Hat Product Errata RHBA-2023:1360 |
Back to bug 2121265