Back to bug 1371576
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2016-08-30 16:10:33 UTC | Keywords | FutureFeature | |
| Sridhar | 2016-09-06 16:56:36 UTC | CC | ssundarr | |
| Jan Pokorný [poki] | 2016-09-12 16:21:31 UTC | CC | jpokorny | |
| Ken Gaillot | 2016-10-05 20:34:17 UTC | Target Release | --- | 7.4 |
| John Ruemker | 2016-10-12 15:25:04 UTC | CC | jruemker | |
| Robert Scheck | 2016-12-22 16:09:02 UTC | CC | redhat-bugzilla, robert.scheck | |
| John Ruemker | 2017-01-05 23:32:28 UTC | Blocks | 1394959 | |
| michal novacek | 2017-01-31 14:43:11 UTC | CC | mnovacek | |
| Rob Young | 2017-02-06 18:12:16 UTC | CC | royoung | |
| Ken Gaillot | 2017-03-15 17:20:30 UTC | Status | NEW | ASSIGNED |
| Target Release | 7.4 | 7.5 | ||
| Version | 7.4 | 7.3 | ||
| Chris Feist | 2017-04-03 20:05:21 UTC | CC | cfeist | |
| Blocks | 1394959 | |||
| Luc de Louw | 2017-04-11 12:50:09 UTC | CC | ldelouw | |
| John Ruemker | 2017-07-12 22:10:10 UTC | Blocks | 1466531 | |
| Steven J. Levine | 2017-08-17 18:15:33 UTC | Blocks | 1482621 | |
| Cole Towsley | 2017-08-24 13:18:17 UTC | CC | ctowsley | |
| Chris Williams | 2017-09-18 15:54:35 UTC | Blocks | 1420851 | |
| Ken Gaillot | 2017-10-09 17:13:31 UTC | Target Release | 7.5 | 7.6 |
| Chris Feist | 2017-10-19 22:13:29 UTC | Blocks | 1466531 | |
| Lenka Špačková | 2017-11-13 10:38:18 UTC | Docs Contact | slevine | |
| PnT Account Manager | 2017-12-12 19:49:51 UTC | CC | ssundarr | |
| John Ruemker | 2018-03-20 18:15:29 UTC | Blocks | 1554536 | |
| Chris Williams | 2018-04-17 13:51:14 UTC | Blocks | 1546815 | |
| Ken Gaillot | 2018-06-08 17:33:52 UTC | Target Release | 7.6 | 7.7 |
| Chris Feist | 2018-06-08 18:43:20 UTC | Blocks | 1554536 | |
| Josef Zimek | 2018-07-25 12:50:35 UTC | CC | christianelwin.romein | |
| Link ID | Red Hat Knowledge Base (Solution) 3543701 | |||
| Ken Gaillot | 2018-11-19 19:19:51 UTC | Priority | unspecified | medium |
| Target Release | 7.7 | 8.1 | ||
| Version | 7.3 | 8.0 | ||
| Component | pacemaker | pacemaker | ||
| Target Milestone | rc | pre-dev-freeze | ||
| Product | Red Hat Enterprise Linux 7 | Red Hat Enterprise Linux 8 | ||
| Severity | unspecified | medium | ||
| Steven J. Levine | 2019-02-05 18:49:42 UTC | Blocks | 1672748 | |
| John Ruemker | 2019-02-21 22:33:44 UTC | Blocks | 1679810 | |
| Ken Gaillot | 2019-03-27 17:06:35 UTC | Priority | medium | high |
| Type | Bug | Feature Request | ||
| Ken Gaillot | 2019-06-18 14:54:26 UTC | Target Release | 8.1 | 8.2 |
| Ken Gaillot | 2019-09-30 14:43:41 UTC | Target Release | 8.2 | 8.3 |
| Andrew Beekhof | 2020-01-16 22:26:54 UTC | CC | abeekhof | |
| PnT Account Manager | 2020-04-30 22:17:45 UTC | CC | jpokorny | |
| Ken Gaillot | 2020-05-06 13:36:11 UTC | Target Release | 8.3 | 8.4 |
| Chris Feist | 2020-06-17 15:01:18 UTC | Summary | RFE: Add equivalent functionality of __independent_subtree="2" and __max_restarts="n" to pacemaker | RFE: Add equivalent functionality of __independent_subtree="2" and __max_restarts="n" to pacemaker (Critical Resources) |
| Red Hat One Jira (issues.redhat.com) | 2020-10-12 20:24:27 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-28924 | |
| Markéta Smazová | 2020-10-20 16:43:59 UTC | CC | msmazova | |
| Red Hat One Jira (issues.redhat.com) | 2020-10-30 17:09:28 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-13141 | |
| Libor Miksik | 2020-11-04 14:37:02 UTC | Blocks | 1894575 | |
| RHEL Program Management | 2020-11-13 16:07:06 UTC | Keywords | Triaged | |
| PnT Account Manager | 2021-01-05 05:42:40 UTC | CC | royoung | |
| Ken Gaillot | 2021-01-14 22:10:23 UTC | Status | ASSIGNED | POST |
| Ken Gaillot | 2021-01-15 22:52:57 UTC | Status | POST | MODIFIED |
| Fixed In Version | pacemaker-2.0.5-5.el8 | |||
| Doc Text | Pacemaker now supports noncritical resources and colocation constraints. Colocation constraints now have a true/false "influence" option, and resources now have a true/false "critical" meta-attribute. "critical" serves as a default for "influence" for all colocation constraints involving the resource as the dependent resource. The default of "true" for both "influence" and "critical" preserves the previous behavior, where Pacemaker will try its best to keep both resources active. If the dependent resource reaches its migration-threshold for failures, both resources will move to another node if possible. With a value of "false", Pacemaker will avoid moving the primary resource due to the dependent resource. In this case, if the dependent resource reaches its migration-threshold for failures, it will stop if the primary resource is active and can remain on its current node. | |||
| Doc Type | If docs needed, set a value | Release Note | ||
| errata-xmlrpc | 2021-01-21 21:25:05 UTC | Status | MODIFIED | ON_QA |
| Tomas Jelinek | 2021-01-22 08:12:03 UTC | Blocks | 1916011 | |
| Lucie Vařáková | 2021-01-25 15:07:34 UTC | Doc Type | Release Note | Enhancement |
| Steven J. Levine | 2021-02-08 14:57:58 UTC | CC | kgaillot | |
| Flags | needinfo?(kgaillot) | |||
| Steven J. Levine | 2021-02-08 15:22:45 UTC | Flags | needinfo?(kgaillot) | |
| Ken Gaillot | 2021-02-08 15:40:43 UTC | Flags | needinfo?(kgaillot) needinfo?(kgaillot) | |
| Markéta Smazová | 2021-02-15 18:32:12 UTC | Status | ON_QA | VERIFIED |
| Steven J. Levine | 2021-02-19 19:41:22 UTC | Flags | needinfo?(kgaillot) | |
| Ken Gaillot | 2021-02-19 20:51:12 UTC | Flags | needinfo?(kgaillot) | |
| Steven J. Levine | 2021-02-19 20:56:51 UTC | Doc Text | Pacemaker now supports noncritical resources and colocation constraints. Colocation constraints now have a true/false "influence" option, and resources now have a true/false "critical" meta-attribute. "critical" serves as a default for "influence" for all colocation constraints involving the resource as the dependent resource. The default of "true" for both "influence" and "critical" preserves the previous behavior, where Pacemaker will try its best to keep both resources active. If the dependent resource reaches its migration-threshold for failures, both resources will move to another node if possible. With a value of "false", Pacemaker will avoid moving the primary resource due to the dependent resource. In this case, if the dependent resource reaches its migration-threshold for failures, it will stop if the primary resource is active and can remain on its current node. | .Noncritical resources and colocation constraints You can now configure a colocation constraint such that if the dependent resource of the constraint reaches its migration threshold for failure, Pacemaker will leave that resource offline and keep the primary resource on its current node rather than attempting to move both resources to another node. To support this behavior, colocation constraints now have an `influence` option, which can be set to `true` or `false`, and resources have a `critical` meta-attribute, which can also be set to `true` or `false`. The value of the `critical` resource meta option determines the default value of the `influence` option for all colocation constraints involving the resource as a dependent resource. When the `influence` colocation constraint option has a value of `true` Pacemaker will attempt to keep both the primary and dependent resource active. If the dependent resource reaches its migration threshold for failures, both resources will move to another node if possible. When the `influence` colocation option has a value of `false`, Pacemaker will avoid moving the primary resource as a result of the status of the dependent resource. In this case, if the dependent resource reaches its migration threshold for failures, it will stop if the primary resource is active and can remain on its current node. By default, the value of the `critical` resource meta option is set to `true`, which in turn determines that the default value of the `influence` option is `true`. This preserves the previous behavior where Pacemaker attempted to keep both resources active. |
| Steven J. Levine | 2021-03-11 18:14:51 UTC | Doc Text | .Noncritical resources and colocation constraints You can now configure a colocation constraint such that if the dependent resource of the constraint reaches its migration threshold for failure, Pacemaker will leave that resource offline and keep the primary resource on its current node rather than attempting to move both resources to another node. To support this behavior, colocation constraints now have an `influence` option, which can be set to `true` or `false`, and resources have a `critical` meta-attribute, which can also be set to `true` or `false`. The value of the `critical` resource meta option determines the default value of the `influence` option for all colocation constraints involving the resource as a dependent resource. When the `influence` colocation constraint option has a value of `true` Pacemaker will attempt to keep both the primary and dependent resource active. If the dependent resource reaches its migration threshold for failures, both resources will move to another node if possible. When the `influence` colocation option has a value of `false`, Pacemaker will avoid moving the primary resource as a result of the status of the dependent resource. In this case, if the dependent resource reaches its migration threshold for failures, it will stop if the primary resource is active and can remain on its current node. By default, the value of the `critical` resource meta option is set to `true`, which in turn determines that the default value of the `influence` option is `true`. This preserves the previous behavior where Pacemaker attempted to keep both resources active. | .Noncritical resources in colocation constraints are now supported With this enhancement, you can configure a colocation constraint such that if the dependent resource of the constraint reaches its migration threshold for failure, Pacemaker will leave that resource offline and keep the primary resource on its current node rather than attempting to move both resources to another node. To support this behavior, colocation constraints now have an `influence` option, which can be set to `true` or `false`, and resources have a `critical` meta-attribute, which can also be set to `true` or `false`. The value of the `critical` resource meta option determines the default value of the `influence` option for all colocation constraints involving the resource as a dependent resource. When the `influence` colocation constraint option has a value of `true` Pacemaker will attempt to keep both the primary and dependent resource active. If the dependent resource reaches its migration threshold for failures, both resources will move to another node if possible. When the `influence` colocation option has a value of `false`, Pacemaker will avoid moving the primary resource as a result of the status of the dependent resource. In this case, if the dependent resource reaches its migration threshold for failures, it will stop if the primary resource is active and can remain on its current node. By default, the value of the `critical` resource meta option is set to `true`, which in turn determines that the default value of the `influence` option is `true`. This preserves the previous behavior where Pacemaker attempted to keep both resources active. |
| Steven J. Levine | 2021-03-11 18:17:17 UTC | Doc Text | .Noncritical resources in colocation constraints are now supported With this enhancement, you can configure a colocation constraint such that if the dependent resource of the constraint reaches its migration threshold for failure, Pacemaker will leave that resource offline and keep the primary resource on its current node rather than attempting to move both resources to another node. To support this behavior, colocation constraints now have an `influence` option, which can be set to `true` or `false`, and resources have a `critical` meta-attribute, which can also be set to `true` or `false`. The value of the `critical` resource meta option determines the default value of the `influence` option for all colocation constraints involving the resource as a dependent resource. When the `influence` colocation constraint option has a value of `true` Pacemaker will attempt to keep both the primary and dependent resource active. If the dependent resource reaches its migration threshold for failures, both resources will move to another node if possible. When the `influence` colocation option has a value of `false`, Pacemaker will avoid moving the primary resource as a result of the status of the dependent resource. In this case, if the dependent resource reaches its migration threshold for failures, it will stop if the primary resource is active and can remain on its current node. By default, the value of the `critical` resource meta option is set to `true`, which in turn determines that the default value of the `influence` option is `true`. This preserves the previous behavior where Pacemaker attempted to keep both resources active. | .Noncritical resources in colocation constraints are now supported With this enhancement, you can configure a colocation constraint such that if the dependent resource of the constraint reaches its migration threshold for failure, Pacemaker will leave that resource offline and keep the primary resource on its current node rather than attempting to move both resources to another node. To support this behavior, colocation constraints now have an `influence` option, which can be set to `true` or `false`, and resources have a `critical` meta-attribute, which can also be set to `true` or `false`. The value of the `critical` resource meta option determines the default value of the `influence` option for all colocation constraints involving the resource as a dependent resource. When the `influence` colocation constraint option has a value of `true` Pacemaker will attempt to keep both the primary and dependent resource active. If the dependent resource reaches its migration threshold for failures, both resources will move to another node, if possible. When the `influence` colocation option has a value of `false`, Pacemaker will avoid moving the primary resource as a result of the status of the dependent resource. In this case, if the dependent resource reaches its migration threshold for failures, it will stop if the primary resource is active and can remain on its current node. By default, the value of the `critical` resource meta option is set to `true`, which in turn determines that the default value of the `influence` option is `true`. This preserves the previous behavior where Pacemaker attempted to keep both resources active. |
| errata-xmlrpc | 2021-05-18 00:39:52 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2021-05-18 15:26:41 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2021-05-18 15:26:41 UTC |
Back to bug 1371576