Bug 1782887
Summary: | invalid transition produced in crm_simulate with "start A then stop B" constraint | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Tomas Jelinek <tojeline> | ||||||||
Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | cluster-qe <cluster-qe> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 8.2 | CC: | cluster-maint, msmazova | ||||||||
Target Milestone: | rc | Keywords: | Triaged | ||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | |||||||||||
: | 1787532 (view as bug list) | Environment: | |||||||||
Last Closed: | 2021-12-13 07:27:06 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 1787532 | ||||||||||
Attachments: |
|
Description
Tomas Jelinek
2019-12-12 15:05:40 UTC
Created attachment 1644455 [details]
the original cib
this is the configuration of a cluster before disabling a resource
Created attachment 1644456 [details]
the updated cib
this cib contains the change to be simulated against the running cluster - d1 is disabled
Created attachment 1644457 [details]
crm_simulate output
This issue has been discovered when testing the safe-disable feature in pcs, see bz1631519#c17 and following comments there for more details. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. This is still a priority and will be reopened when developer time becomes available to address it |