RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1183752 - Unable to delete VirtualDomain resource remote-node when it has configured some constraints
Summary: Unable to delete VirtualDomain resource remote-node when it has configured so...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-19 16:49 UTC by Miroslav Lisik
Modified: 2015-11-19 09:34 UTC (History)
3 users (show)

Fixed In Version: pcs-0.9.140-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: User tries to delete a remote node resource which is referenced in constraints. Consequence: The resource is not deleted and an error message is displayed stating the resource can not be deleted as it is referenced in constraints. Fix: When deleting a resource, remove constraints referencing the resource properly. Result: The remote node resource is deleted.
Clone Of:
Environment:
Last Closed: 2015-11-19 09:34:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix (2.94 KB, patch)
2015-05-28 08:42 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2290 0 normal SHIPPED_LIVE Moderate: pcs security, bug fix, and enhancement update 2015-11-19 09:43:53 UTC

Description Miroslav Lisik 2015-01-19 16:49:17 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0
Build Identifier: 

I'm unable delete resource with pcs when I configure constrained VirtualDomain resource follows:

[root@reno-01 x86_64]# pcs resource create vm-guest01 VirtualDomain hypervisor=lxc:/// config=/root/lxc/lxc-01.xml force_stop=true meta remote-node=lxc-01

[root@reno-01 x86_64]# pcs constraint location vm-guest01 prefers reno-01

[root@reno-01 x86_64]# pcs constraint show --full
Location Constraints:
  Resource: vm-guest01
    Enabled on: reno-01 (score:INFINITY) (id:location-vm-guest01-reno-01-INFINITY)
Ordering Constraints:
Colocation Constraints:

Trying to delete the resource:

[root@reno-01 x86_64]# pcs resource delete vm-guest01
Attempting to stop: vm-guest01...Stopped
Removing Constraint - location-vm-guest01-reno-01-INFINITY
Deleting Resource - vm-guest01
Error: unable to remove resource: vm-guest01, it may still be referenced in constraints.



Reproducible: Always

Steps to Reproduce:
1. setup cluster
2. setup VirtualDomain resource configured as remote-node
pcs resource create vm-guest01 VirtualDomain hypervisor=lxc:/// config=/root/lxc/lxc-01.xml force_stop=true meta remote-node=lxc-01

3. put some constraint e.g. location constraint:
pcs constraint location vm-guest01 prefers reno-01

4. Try to delete VirtualDomain resource
pcs resource delete vm-guest01

5. See error message

Actual Results:  
pcs unable to delete the resource

Expected Results:  
pcs delete the resource

It happens always when parameter 'meta remote-node=<hostname>' is configured.
In configuration without this parameter are resource and its constraint(s) deleted successfully.
Comment 1 Miroslav Lisik 2015-01-19 16:51:18 UTC 
pcs version: pcs-0.9.137-12.el7.x86_64
Comment 4 Tomas Jelinek 2015-05-28 08:42:35 UTC 
Created attachment 1031070 [details]
proposed fix
Comment 5 Tomas Jelinek 2015-06-04 14:39:06 UTC 
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.137-13.el7_1.2.x86_64
[root@rh71-node1:~]# pcs resource create vm-guest01 VirtualDomain hypervisor=lxc:/// config=/root/lxc/lxc-01.xml force_stop=true meta remote-node=lxc-01
[root@rh71-node1:~]# pcs constraint location vm-guest01 prefers reno-01
[root@rh71-node1:~]# pcs resource delete vm-guest01
Removing Constraint - location-vm-guest01-reno-01-INFINITY
Deleting Resource - vm-guest01
Error: unable to remove resource: vm-guest01, it may still be referenced in constraints.
[root@rh71-node1:~]# pcs resource
 vm-guest01     (ocf::heartbeat:VirtualDomain): Stopped



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.140-1.el6.x86_64
[root@rh71-node1:~]# pcs resource create vm-guest01 VirtualDomain hypervisor=lxc:/// config=/root/lxc/lxc-01.xml force_stop=true meta remote-node=lxc-01
[root@rh71-node1:~]# pcs constraint location vm-guest01 prefers reno-01
[root@rh71-node1:~]# pcs resource delete vm-guest01
Removing Constraint - location-vm-guest01-reno-01-INFINITY
Deleting Resource - vm-guest01
[root@rh71-node1:~]# pcs resource
NO resources configured
Comment 10 errata-xmlrpc 2015-11-19 09:34:18 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2290.html
Note You need to log in before you can comment on or make changes to this bug.