Back to bug 1578820
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Chris Feist | 2018-08-23 20:11:06 UTC | Blocks | 1621899 | |
| Ken Gaillot | 2019-03-27 21:00:58 UTC | Priority | unspecified | low |
| Target Milestone | rc | pre-dev-freeze | ||
| Severity | unspecified | medium | ||
| Andrew Beekhof | 2020-01-16 22:23:26 UTC | CC | abeekhof | |
| Ken Gaillot | 2020-05-06 00:26:53 UTC | Pool ID | sst_high_availability_rhel_7 | sst_high_availability_rhel_8 |
| Component | pacemaker | pacemaker | ||
| Version | 7.5 | 8.3 | ||
| Product | Red Hat Enterprise Linux 7 | Red Hat Enterprise Linux 8 | ||
| Target Milestone | pre-dev-freeze | rc | ||
| Red Hat One Jira (issues.redhat.com) | 2020-12-02 13:42:30 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-42515 | |
| RHEL Program Management | 2021-01-08 07:29:26 UTC | Status | NEW | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2021-01-08 07:29:26 UTC | |||
| Tomas Jelinek | 2023-01-23 16:08:47 UTC | Status | CLOSED | NEW |
| Resolution | WONTFIX | --- | ||
| Keywords | Reopened | |||
| Ken Gaillot | 2023-02-07 23:29:57 UTC | Target Release | --- | 8.9 |
| Status | NEW | ASSIGNED | ||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Doc Text | Cause: When checking where a bundle with a single replica was active, crm_resource would count both the node where the container was active, and the guest node created for the container itself. Consequence: crm_resource would refuse to ban or move a bundle with a single active replica. Fix: crm_resource now only counts where a bundle's containers are active. Result: crm_resource allows banning or moving a bundle with only a single active replica. | |||
| Target Upstream Version | 2.1.6 | |||
| RHEL Program Management | 2023-02-07 23:30:07 UTC | Keywords | Triaged | |
| Ken Gaillot | 2023-05-02 21:49:25 UTC | Status | ASSIGNED | POST |
| Markéta Smazová | 2023-05-16 12:37:36 UTC | CC | msmazova | |
| Dean Jansa | 2023-05-16 13:11:21 UTC | Link ID | Red Hat Issue Tracker CLUSTERQE-6690 | |
| Chris Lumens | 2023-05-26 13:32:49 UTC | Fixed In Version | pacemaker-2.1.6-1.el8 | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2023-05-26 13:39:48 UTC | Status | MODIFIED | ON_QA |
| RESHMA K VIJAYAN | 2023-06-06 14:21:28 UTC | Link ID | Red Hat Knowledge Base (Solution) 6972370 | |
| CC | revijaya | |||
| Markéta Smazová | 2023-06-20 12:12:55 UTC | Status | ON_QA | VERIFIED |
| Steven J. Levine | 2023-06-29 16:26:33 UTC | Flags | needinfo?(kgaillot) | |
| CC | kgaillot, slevine | |||
| Ken Gaillot | 2023-06-29 16:56:51 UTC | Flags | needinfo?(kgaillot) | |
| Steven J. Levine | 2023-07-07 18:56:16 UTC | Doc Text | Cause: When checking where a bundle with a single replica was active, crm_resource would count both the node where the container was active, and the guest node created for the container itself. Consequence: crm_resource would refuse to ban or move a bundle with a single active replica. Fix: crm_resource now only counts where a bundle's containers are active. Result: crm_resource allows banning or moving a bundle with only a single active replica. | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it would count both the node where the container was active and the guest node created for the container itself. As a consequence, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts where a bundle's containers are active. |
| Steven J. Levine | 2023-07-27 14:48:09 UTC | Docs Contact | slevine | |
| Steven J. Levine | 2023-08-10 15:22:31 UTC | Doc Text | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it would count both the node where the container was active and the guest node created for the container itself. As a consequence, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts where a bundle's containers are active. | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it counted both the node where the container was active and the guest node that was created for the container itself. As a result, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts where a bundle's containers are active. |
| Flags | needinfo?(kgaillot) | |||
| Ken Gaillot | 2023-08-10 15:36:38 UTC | Flags | needinfo?(kgaillot) | |
| Red Hat Bugzilla | 2023-08-10 15:41:37 UTC | QA Contact | cluster-qe | cluster-qe |
| Steven J. Levine | 2023-08-10 16:33:18 UTC | Doc Text | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it counted both the node where the container was active and the guest node that was created for the container itself. As a result, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts where a bundle's containers are active. | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it counted both the node where the container was active and the guest node that was created for the container itself. As a result, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts where a bundle's containers are active when determining the number of active replicas. |
| Steven J. Levine | 2023-08-11 14:42:57 UTC | Doc Text | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it counted both the node where the container was active and the guest node that was created for the container itself. As a result, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts where a bundle's containers are active when determining the number of active replicas. | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it counted both the node where the container was active and the guest node that was created for the container itself. As a result, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts nodes where a bundle's containers are active when determining the number of active replicas. |
| Steven J. Levine | 2023-08-11 14:46:32 UTC | Doc Text | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, it counted both the node where the container was active and the guest node that was created for the container itself. As a result, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts nodes where a bundle's containers are active when determining the number of active replicas. | .The `crm_resource` command now allows banning or moving a bundle with only a single active replica Previously, when the `crm_resource` command checked where a bundle with a single replica was active, the command counted both the node where the container was active and the guest node that was created for the container itself. As a result, the `crm_resource` command would not ban or move a bundle with a single active replica. With this fix, the `crm_resource` command now only counts nodes where a bundle's containers are active when determining the number of active replicas. |
Back to bug 1578820