Bug 1619824

Summary: RFE: have 'pcs resource delete' be able to act on multiple resources like enable and disable do
Product: Red Hat Enterprise Linux 7 Reporter: Corey Marthaler <cmarthal>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED DUPLICATE QA Contact: cluster-qe <cluster-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.6CC: cfeist, cluster-maint, idevat, omular, tojeline
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-22 08:06:53 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:

Description Corey Marthaler 2018-08-21 20:11:30 UTC
Description of problem:

# Two resources on same cmdline
[root@mckinley-01 ~]# pcs resource enable HA_LVM2 HA_LVM3
[root@mckinley-01 ~]# pcs status
Cluster name: MCKINLEY
Stack: corosync
Current DC: mckinley-02 (version 1.1.19-3.el7-c3c624ea3d) - partition with quorum
Last updated: Tue Aug 21 15:03:50 2018
Last change: Tue Aug 21 15:03:43 2018 by root via cibadmin on mckinley-01
 
3 nodes configured
11 resources configured
 
Online: [ mckinley-01 mckinley-02 mckinley-03 ]
 
Full list of resources:
 
 mckinley-apc   (stonith:fence_apc):    Started mckinley-01
 Clone Set: dlm_for_lvmlockd-clone [dlm_for_lvmlockd]
     Started: [ mckinley-01 mckinley-02 mckinley-03 ]
 Clone Set: lvmlockd-clone [lvmlockd]
     Started: [ mckinley-01 mckinley-02 mckinley-03 ]
 Resource Group: HA_LVM2
     lvm2       (ocf::heartbeat:LVM-activate):  Started mckinley-02
     ha2        (ocf::heartbeat:Filesystem):    Started mckinley-02
 Resource Group: HA_LVM3
     lvm3       (ocf::heartbeat:LVM-activate):  Started mckinley-03
     ha3        (ocf::heartbeat:Filesystem):    Started mckinley-03
 
Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
 
 
[root@mckinley-01 ~]# pcs resource disable HA_LVM2 HA_LVM3
[root@mckinley-01 ~]# pcs status
Cluster name: MCKINLEY
Stack: corosync
Current DC: mckinley-02 (version 1.1.19-3.el7-c3c624ea3d) - partition with quorum
Last updated: Tue Aug 21 15:04:02 2018
Last change: Tue Aug 21 15:03:59 2018 by root via cibadmin on mckinley-01
 
3 nodes configured
11 resources configured (8 DISABLED)
 
Online: [ mckinley-01 mckinley-02 mckinley-03 ]
 
Full list of resources:
 
 mckinley-apc   (stonith:fence_apc):    Started mckinley-01
 Clone Set: dlm_for_lvmlockd-clone [dlm_for_lvmlockd]
     Started: [ mckinley-01 mckinley-02 mckinley-03 ]
 Clone Set: lvmlockd-clone [lvmlockd]
     Started: [ mckinley-01 mckinley-02 mckinley-03 ]
 Resource Group: HA_LVM2
     lvm2       (ocf::heartbeat:LVM-activate):  Stopped (disabled)
     ha2        (ocf::heartbeat:Filesystem):    Stopped (disabled)
 Resource Group: HA_LVM3
     lvm3       (ocf::heartbeat:LVM-activate):  Stopped (disabled)
     ha3        (ocf::heartbeat:Filesystem):    Stopped (disabled)
 
Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
 

# Only deletes the first resource, and doesn't even let user know the other was ignored
[root@mckinley-01 ~]# pcs resource delete HA_LVM2 HA_LVM3
Removing group: HA_LVM2 (and all resources within group)
Stopping all resources in group: HA_LVM2...
Deleting Resource - lvm2
Removing Constraint - order-lvmlockd-clone-HA_LVM2-mandatory
Deleting Resource (and group) - ha2


Version-Release number of selected component (if applicable):
Name        : pcs
Version     : 0.9.165
Release     : 1.el7
Architecture: x86_64
Install Date: Thu 19 Jul 2018 02:14:30 PM CDT
Group       : System Environment/Base
Size        : 16481620
License     : GPLv2
Signature   : RSA/SHA256, Fri 22 Jun 2018 09:01:36 AM CDT, Key ID 199e2f91fd431d51
Source RPM  : pcs-0.9.165-1.el7.src.rpm
Build Date  : Fri 22 Jun 2018 06:50:37 AM CDT

Comment 3 Tomas Jelinek 2018-08-22 08:06:53 UTC

*** This bug has been marked as a duplicate of bug 1420298 ***