Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
I do have a resource in a group haa-group-0. When issuing 'pcs resource
group remove haa-group-0' the group is removed but the resource from this group
is not deleted and remains as ungrupped resources. This is quite unexpected.
Version-Release number of selected component (if applicable):
pcs-0.9.67-2.el6.noarch
How reproducible: always
Steps to Reproduce:
1. create a group with resources using pcs
2. issue 'pcs resource group remove <group_name>'
Actual results: resource are not removed
Expected results: resources should be removed with the group
Additional info:
It would be nice to either have parameter to force resources removal and not to
do it by default or the other way round. Current behaviour is confusing.
$ pcs status
Cluster name: STSRHTS17392
Last updated: Tue Aug 20 14:38:58 2013
Last change: Tue Aug 20 14:38:55 2013 via cibadmin on virt-061
Stack: corosync
Current DC: virt-063 (3) - partition with quorum
Version: 1.1.10-12.el7-368c726
3 Nodes configured
2 Resources configured
Online: [ virt-061 virt-062 virt-063 ]
Full list of resources:
virt-fencing (stonith:fence_xvm): Started virt-062
Resource Group: haa-group-0
apache-0 (ocf::heartbeat:apache): Stopped
PCSD Status:
virt-061: Online
virt-062: Online
virt-063: Online
Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled
# pcs resource group remove haa-group-0
# pcs status
Cluster name: STSRHTS17392
Last updated: Tue Aug 20 14:39:15 2013
Last change: Tue Aug 20 14:39:10 2013 via cibadmin on virt-063
Stack: corosync
Current DC: virt-063 (3) - partition with quorum
Version: 1.1.10-12.el7-368c726
3 Nodes configured
2 Resources configured
Online: [ virt-061 virt-062 virt-063 ]
Full list of resources:
virt-fencing (stonith:fence_xvm): Started virt-062
apache-0 (ocf::heartbeat:apache): Stopped
PCSD Status:
virt-061: Online
virt-062: Online
virt-063: Online
Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: I do have a resource in a group haa-group-0. When issuing 'pcs resource group remove haa-group-0' the group is removed but the resource from this group is not deleted and remains as ungrupped resources. This is quite unexpected. Version-Release number of selected component (if applicable): pcs-0.9.67-2.el6.noarch How reproducible: always Steps to Reproduce: 1. create a group with resources using pcs 2. issue 'pcs resource group remove <group_name>' Actual results: resource are not removed Expected results: resources should be removed with the group Additional info: It would be nice to either have parameter to force resources removal and not to do it by default or the other way round. Current behaviour is confusing. $ pcs status Cluster name: STSRHTS17392 Last updated: Tue Aug 20 14:38:58 2013 Last change: Tue Aug 20 14:38:55 2013 via cibadmin on virt-061 Stack: corosync Current DC: virt-063 (3) - partition with quorum Version: 1.1.10-12.el7-368c726 3 Nodes configured 2 Resources configured Online: [ virt-061 virt-062 virt-063 ] Full list of resources: virt-fencing (stonith:fence_xvm): Started virt-062 Resource Group: haa-group-0 apache-0 (ocf::heartbeat:apache): Stopped PCSD Status: virt-061: Online virt-062: Online virt-063: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled # pcs resource group remove haa-group-0 # pcs status Cluster name: STSRHTS17392 Last updated: Tue Aug 20 14:39:15 2013 Last change: Tue Aug 20 14:39:10 2013 via cibadmin on virt-063 Stack: corosync Current DC: virt-063 (3) - partition with quorum Version: 1.1.10-12.el7-368c726 3 Nodes configured 2 Resources configured Online: [ virt-061 virt-062 virt-063 ] Full list of resources: virt-fencing (stonith:fence_xvm): Started virt-062 apache-0 (ocf::heartbeat:apache): Stopped PCSD Status: virt-061: Online virt-062: Online virt-063: Online Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled