Bug 1426608

Summary: The command "pcs resource delete" omits live cluster actions without warning when the flag "-f" is used.
Product: Red Hat Enterprise Linux 8 Reporter: Ivan Devat <idevat>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED MIGRATED QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 8.0CC: cfeist, cluster-maint, idevat, omular, tojeline
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-01 07:28:13 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: 1420298    
Bug Blocks:    

Description Ivan Devat 2017-02-24 12:46:00 UTC
Description of problem:
The command "pcs resource delete" omits live cluster actions without warning when the flag "-f" is used.

How reproducible:
always

Steps to Reproduce:
[vm-rhel72-1 ~] $ pcs resource create remote-node ocf:pacemaker:remote server="vm-rhel72-2"
[vm-rhel72-1 ~] $ pcs status |grep remote-node
RemoteOnline: [ remote-node ]
 remote-node    (ocf::pacemaker:remote):        Started vm-rhel72-1
                                                
[vm-rhel72-1 ~] $ pcs cluster cib > cib.xml
[vm-rhel72-1 ~] $ pcs resource delete -f cib.xml remote-node
Deleting Resource - remote-node

[vm-rhel72-1 ~] $ pcs cluster cib-push cib.xml && pcs status|grep remote-node
CIB updated
RemoteOnline: [ remote-node ]
 remote-node    (ocf::pacemaker:remote):         ORPHANED Started vm-rhel72-1


Actual results:
No warnings.


Expected results:
Warning that the disabling of the resource before the removing is skipped.
Warning that the removing of the node is skipped.

Comment 9 RHEL Program Management 2020-12-01 07:28:13 UTC
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.