Bug 1251496 - pcs resource disable should act on the clone/master of the resource if it is a clone or master
pcs resource disable should act on the clone/master of the resource if it is ...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs (Show other bugs)
7.3
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Chris Feist
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-07 09:53 EDT by Chris Feist
Modified: 2016-02-03 10:43 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-03 10:25:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Feist 2015-08-07 09:53:55 EDT
If a resource is a master or clone, issuing pcs resource disable/enable on the actual resource should cause the clone or master to be disabled.

When we're doing a resource enable we should make sure the enable the resource and the parent clone or master.

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