-
Story
-
Resolution: Unresolved
-
Major
-
rhel-10.0.beta
-
pacemaker-3.0.0-2.el10
-
rhel-sst-high-availability
-
ssg_filesystems_storage_and_HA
-
13
-
20
-
1
-
Dev ack
-
False
-
-
Yes
-
Red Hat Enterprise Linux
-
None
-
Enhancement
-
-
Proposed
-
None
Goal
- As a user, if I configure clone-node-max > 1, I clearly want the clone to be globally unique, and do not want to have to remember to configure a separate setting
Acceptance Criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- Verify that if a clone is configured with globally-unique="false", that only one instance can run on a node even if clone-node-max > 1
- Verify that if a clone if configured without setting globally-unique, but clone-node-max > 1, then more than one instance can run on a node
- links to
-
RHBA-2024:141766 pacemaker bug fix and enhancement update