Back to bug 1931023
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2021-02-20 06:28:54 UTC | Pool ID | sst_high_availability_rhel_8 | |
| Red Hat One Jira (issues.redhat.com) | 2021-02-20 06:32:03 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-68134 | |
| Reid Wahl | 2021-02-20 07:08:42 UTC | CC | amemon | |
| Reid Wahl | 2021-02-26 09:07:19 UTC | Link ID | Github ClusterLabs/pacemaker/pull/2313 | |
| Ken Gaillot | 2021-03-09 18:25:05 UTC | Status | NEW | ASSIGNED |
| RHEL Program Management | 2021-03-09 18:25:12 UTC | Keywords | Triaged | |
| Ken Gaillot | 2021-06-30 22:36:46 UTC | Target Release | 8.5 | 8.6 |
| Patrik Hagara | 2021-07-01 10:04:38 UTC | CC | phagara | |
| Ken Gaillot | 2021-10-04 17:11:37 UTC | Target Release | 8.6 | --- |
| Status | ASSIGNED | NEW | ||
| Chris Lumens | 2022-08-31 16:19:30 UTC | Status | NEW | ASSIGNED |
| Ken Gaillot | 2022-11-14 15:55:36 UTC | Target Release | --- | 8.8 |
| Ken Gaillot | 2022-11-22 17:44:29 UTC | Target Release | 8.8 | 8.9 |
| Chris Feist | 2023-04-17 13:43:24 UTC | CC | cfeist | |
| Markéta Smazová | 2023-05-16 12:35:58 UTC | CC | msmazova | |
| Dean Jansa | 2023-05-16 13:11:12 UTC | Link ID | Red Hat Issue Tracker CLUSTERQE-6691 | |
| Ken Gaillot | 2023-06-22 19:24:56 UTC | Assignee | kgaillot | nwahl |
| Steven J. Levine | 2023-06-29 15:19:23 UTC | Flags | needinfo?(nwahl) | |
| CC | slevine | |||
| Reid Wahl | 2023-06-29 18:13:32 UTC | Flags | needinfo?(nwahl) | |
| Chris Lumens | 2023-07-11 17:22:05 UTC | Blocks | 2222055 | |
| Ken Gaillot | 2023-07-12 14:15:16 UTC | Doc Text | Cause: Promotable clone instances were assigned in numerical order with promoted instances first. Consequence: If a promoted instance needed to start, an unpromoted instance could be unnecessarily restarted, since the instance numbers could change. Fix: Roles are considered when assigning instance numbers to nodes. Result: There are no unnecessary restarts. | |
| CC | kgaillot | |||
| Status | ASSIGNED | POST | ||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Steven J. Levine | 2023-07-12 19:05:47 UTC | Flags | needinfo?(kgaillot) | |
| Doc Text | Cause: Promotable clone instances were assigned in numerical order with promoted instances first. Consequence: If a promoted instance needed to start, an unpromoted instance could be unnecessarily restarted, since the instance numbers could change. Fix: Roles are considered when assigning instance numbers to nodes. Result: There are no unnecessary restarts. | .Unpromoted clone instances no longer restart unnecessarily Previously, promotable clone instances were assigned in numerical order with promoted instances first. As a consequence, if a promoted clone instance needed to start, an unpromoted instance could be restarted, since the instance numbers could change. With this fix, roles are considered when assigned instance numbers to nodes and there are no unnecessary restarts. |
||
| Ken Gaillot | 2023-07-12 20:14:54 UTC | Flags | needinfo?(kgaillot) | |
| Steven J. Levine | 2023-07-12 20:25:08 UTC | Doc Text | .Unpromoted clone instances no longer restart unnecessarily Previously, promotable clone instances were assigned in numerical order with promoted instances first. As a consequence, if a promoted clone instance needed to start, an unpromoted instance could be restarted, since the instance numbers could change. With this fix, roles are considered when assigned instance numbers to nodes and there are no unnecessary restarts. | .Unpromoted clone instances no longer restart unnecessarily Previously, promotable clone instances were assigned in numerical order with promoted instances first. As a consequence, if a promoted clone instance needed to start, an unpromoted instance could be restarted, since the instance numbers could change. With this fix, roles are considered when assigning instance numbers to nodes and there are no unnecessary restarts. |
| Chris Lumens | 2023-07-20 00:19:40 UTC | Fixed In Version | pacemaker-2.1.6-4.el8 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-07-20 00:24:10 UTC | Status | MODIFIED | ON_QA |
| Steven J. Levine | 2023-07-27 14:48:43 UTC | Docs Contact | slevine | |
| Red Hat Bugzilla | 2023-08-10 15:40:52 UTC | QA Contact | cluster-qe | cluster-qe |
| Steven J. Levine | 2023-08-10 15:56:04 UTC | Doc Text | .Unpromoted clone instances no longer restart unnecessarily Previously, promotable clone instances were assigned in numerical order with promoted instances first. As a consequence, if a promoted clone instance needed to start, an unpromoted instance could be restarted, since the instance numbers could change. With this fix, roles are considered when assigning instance numbers to nodes and there are no unnecessary restarts. | .Unpromoted clone instances no longer restart unnecessarily Previously, promotable clone instances were assigned in numerical order, with promoted instances first. As a result, if a promoted clone instance needed to start, an unpromoted instance in some cases restarted unexpectedly, because the instance numbers changed. With this fix, roles are considered when assigning instance numbers to nodes and as a result no unnecessary restarts occur. |
| Markéta Smazová | 2023-08-11 13:59:27 UTC | Status | ON_QA | VERIFIED |
Back to bug 1931023