Back to bug 1876173
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2020-09-06 02:48:24 UTC | Pool ID | sst_high_availability_rhel_8 | |
| Reid Wahl | 2020-09-06 03:17:02 UTC | Link ID | Red Hat Knowledge Base (Solution) 5374451 | |
| Red Hat One Jira (issues.redhat.com) | 2020-10-30 18:53:31 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-53181 | |
| RHEL Program Management | 2020-11-13 16:46:51 UTC | Keywords | Triaged | |
| Ken Gaillot | 2021-01-29 23:59:01 UTC | Target Release | 8.4 | 8.5 |
| Ken Gaillot | 2021-03-09 18:42:00 UTC | Status | NEW | ASSIGNED |
| Reid Wahl | 2021-03-26 07:09:04 UTC | Group | redhat | |
| Markéta Smazová | 2021-04-30 13:18:51 UTC | CC | msmazova | |
| Ken Gaillot | 2021-07-16 19:20:31 UTC | Target Release | 8.5 | 8.6 |
| Ken Gaillot | 2021-10-04 17:03:35 UTC | OS | Linux | All |
| Ken Gaillot | 2021-10-04 17:16:27 UTC | Target Release | 8.6 | --- |
| Status | ASSIGNED | NEW | ||
| Ken Gaillot | 2021-10-04 17:18:05 UTC | Status | NEW | ASSIGNED |
| Target Release | --- | 8.6 | ||
| Ken Gaillot | 2021-10-20 18:24:56 UTC | Target Release | 8.6 | 8.7 |
| Ken Gaillot | 2022-03-01 15:48:54 UTC | Target Release | 8.7 | --- |
| RHEL Program Management | 2022-03-01 15:49:01 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2022-03-01 15:49:01 UTC | |||
| Ken Gaillot | 2022-03-01 17:28:25 UTC | Status | CLOSED | ASSIGNED |
| Resolution | WONTFIX | --- | ||
| Keywords | Reopened | |||
| Chris Lumens | 2022-08-31 17:03:53 UTC | Priority | medium | high |
| Ken Gaillot | 2022-11-14 15:54:30 UTC | Target Release | --- | 8.8 |
| Ken Gaillot | 2022-12-08 16:57:51 UTC | Target Release | 8.8 | 8.9 |
| Chris Feist | 2023-04-17 13:45:00 UTC | CC | cfeist | |
| Ken Gaillot | 2023-05-02 21:04:15 UTC | Target Upstream Version | 2.1.6 | |
| Status | ASSIGNED | POST | ||
| Chris Lumens | 2023-05-26 13:33:08 UTC | CC | jrehova | |
| Fixed In Version | pacemaker-2.1.6-1.el8 | |||
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-05-26 13:39:49 UTC | Status | MODIFIED | ON_QA |
| Steven J. Levine | 2023-06-29 15:23:15 UTC | Flags | needinfo?(kgaillot) | |
| CC | kgaillot, slevine | |||
| Ken Gaillot | 2023-06-29 16:18:50 UTC | Flags | needinfo?(kgaillot) | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Doc Text | Feature: Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints (including the implicit constraints between group members) before trying to satisfy optional colocation constraints. Reason: Previously, colocation constraints were considered one by one regardless of whether they were mandatory or optional. This meant that certain resources could be unable to run even though a node assignment was possible. Result: Resources with a mix of optional and mandatory colocation constraints are now more likely to be able to run. |
|||
| Steven J. Levine | 2023-07-07 18:47:11 UTC | Doc Text | Feature: Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints (including the implicit constraints between group members) before trying to satisfy optional colocation constraints. Reason: Previously, colocation constraints were considered one by one regardless of whether they were mandatory or optional. This meant that certain resources could be unable to run even though a node assignment was possible. Result: Resources with a mix of optional and mandatory colocation constraints are now more likely to be able to run. | .Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints before trying to satisfy optional colocation constraints. Previously, colocation constraints were considered one by one regardless of whether they were mandatory or optional. This meant that certain resources could be unable to run even though a node assignment was possible. Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints, including the implicit constraints between group members, before trying to satisfy optional colocation constraints. As a result, resources with a mix of optional and mandatory colocation constraints are now more likely to be able to run. |
| Steven J. Levine | 2023-07-14 15:48:54 UTC | Status | ON_QA | VERIFIED |
| Doc Text | .Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints before trying to satisfy optional colocation constraints. Previously, colocation constraints were considered one by one regardless of whether they were mandatory or optional. This meant that certain resources could be unable to run even though a node assignment was possible. Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints, including the implicit constraints between group members, before trying to satisfy optional colocation constraints. As a result, resources with a mix of optional and mandatory colocation constraints are now more likely to be able to run. | .Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints before trying to satisfy optional colocation constraints Previously, colocation constraints were considered one by one regardless of whether they were mandatory or optional. This meant that certain resources could be unable to run even though a node assignment was possible. Pacemaker's scheduler now tries to satisfy all mandatory colocation constraints, including the implicit constraints between group members, before trying to satisfy optional colocation constraints. As a result, resources with a mix of optional and mandatory colocation constraints are now more likely to be able to run. |
||
| Steven J. Levine | 2023-07-27 14:43:28 UTC | Docs Contact | slevine | |
| Red Hat Bugzilla | 2023-08-10 15:41:37 UTC | QA Contact | cluster-qe | cluster-qe |
Back to bug 1876173