Bug 1447918 - --force-start, --force-stop, --force-monitor etc. with bundles
Summary: --force-start, --force-stop, --force-monitor etc. with bundles
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: pre-dev-freeze
: ---
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-04 08:50 UTC by Tomas Jelinek
Modified: 2019-05-05 20:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Tomas Jelinek 2017-05-04 08:50:45 UTC
crm_resource --resource <bundle resource> --force-start|--force-stop|... doesn't work with bundle resources. This is expected as it doesn't work with clones, masters and groups either. For these commands to work the user must specify id of one of inner resources which pacemaker creates behind the scene. How is the user suppose to know those ids? Sure, the ids can be seen in crm_mon --xml once the bundle is started. But what about before that?


Ken:
It sounds like a bad idea to force actions on individual components of a bundle. The intent of the bundle is that they are tightly coupled. Not sure what the best approach is here. Maybe open a bz for discussion.

Comment 2 Ken Gaillot 2017-05-04 14:41:36 UTC
This will be discussed in the 7.5 timeframe.

Comment 3 Andrew Beekhof 2017-07-18 23:54:03 UTC
At best, we could consider the --force-{action} applying to the container.
However that wont bring up anything that was supposed to start inside it, or any IP that was supposed to be collocated for access.

I would be inclined to keep the existing behaviour and "just" improve the error message.

Comment 4 Andrew Beekhof 2017-08-04 01:26:13 UTC
Bumping, not a super high priority yet

Comment 5 Ken Gaillot 2017-11-01 22:39:52 UTC
This will not be addressed in the 7.5 timeframe


Note You need to log in before you can comment on or make changes to this bug.