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 1678273 - Moving the last resource from a group may result in an invalid CIB
Summary: Moving the last resource from a group may result in an invalid CIB
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.5
Assignee: Michal Pospisil
QA Contact: cluster-qe@redhat.com
Steven J. Levine
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-18 12:05 UTC by Tomas Jelinek
Modified: 2021-11-09 19:04 UTC (History)
9 users (show)

Fixed In Version: pcs-0.10.8-3.el8
Doc Type: Bug Fix
Doc Text:
Cause: Moving all resources from a group (or cloned group) with "pcs resource group add" deletes the group (or clone) element from CIB without deleting all references to the deleted group (or clone). Consequence: Updated configuration is invalid and rejected by pacemaker. CIB is dumped onto command line. Fix: Detect this corner-case and notify user about the issue. Result: PCS exits with an explaining error and a workaround suggestion.
Clone Of:
Environment:
Last Closed: 2021-11-09 17:33:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4142 0 None None None 2021-11-09 17:33:37 UTC

Description Tomas Jelinek 2019-02-18 12:05:49 UTC 
Description of problem:
If the last resource from a group is moved to another group by the 'pcs resource group add command', the original group is deleted. This is OK because pacemaker does not allow empty groups. However, constraints (and possibly other elements) referencing the deleted group are not dealt with which results in an invalid CIB being dumped to the terminal.


Version-Release number of selected component (if applicable):
pcs-0.10.1-4.el8


How reproducible:
always, easily


Steps to Reproduce:
Reproducer A - moving the last resource from a group:
[root@rh80-node1:~]# pcs resource create dummy1 ocf:pacemaker:Dummy --group gr1
[root@rh80-node1:~]# pcs resource create dummy2 ocf:pacemaker:Dummy
[root@rh80-node1:~]# pcs constraint order start gr1 then dummy2
Adding gr1 dummy2 (kind: Mandatory) (Options: first-action=start then-action=start)
[root@rh80-node1:~]# pcs resource group add gr2 dummy1
Error: Unable to update cib
Call cib_replace failed (-203): Update does not conform to the configured schema
{cib dump follows}

Reproducer B - moving the last resource from a cloned group:
[root@rh80-node1:~]# pcs resource create dummy1 ocf:pacemaker:Dummy --group gr1
[root@rh80-node1:~]# pcs resource create dummy2 ocf:pacemaker:Dummy
[root@rh80-node1:~]# pcs resource clone gr1
[root@rh80-node1:~]# pcs constraint order start gr1-clone then dummy2
Adding gr1-clone dummy2 (kind: Mandatory) (Options: first-action=start then-action=start)
[root@rh80-node1:~]# pcs resource group add gr2 dummy1
Error: Unable to update cib
Call cib_replace failed (-203): Update does not conform to the configured schema
{cib dump follows}


Actual results:
Invalid CIB dumped.


Expected results:
Either update the CIB so it is valid or exit gracefully with an explaining error.


Additional info:
It is not possible to move resources from clones to groups. It is however possible to move resources from cloned groups to other groups. Is this a desired behavior? Should moving resources from cloned groups be disallowed?
Comment 8 RHEL Program Management 2021-02-01 07:32:52 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.
Comment 13 Michal Pospisil 2021-06-29 09:10:09 UTC 
Fix merged into upstream master: https://github.com/ClusterLabs/pcs/commit/3f20af25aef46d3f5c00def25b3281557466c17f

ENVIRONMENT PREPARATION:
- any cluster
- at least 3 dummy resources
  pcs resource create dummy1 ocf:pacemaker:Dummy
  pcs resource create dummy2 ocf:pacemaker:Dummy
  pcs resource create dummy3 ocf:pacemaker:Dummy


To test this fix, run commands:
# pcs resource group add gr1 dummy1
# pcs constraint order start gr1 then dummy2
Adding gr1 dummy2 (kind: Mandatory) (Options: first-action=start then-action=start)
# pcs resource group add gr2 dummy1 dummy3
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue
# pcs resource group add gr2 dummy2 dummy3
# pcs resource clone gr1
# pcs resource group add gr3 dummy2 dummy1 dummy3
Error: Unable to move resources 'dummy2', 'dummy3' as it would leave group 'gr2' empty. Please, use the 'pcs resource ungroup gr2' command first.
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue
Comment 14 Miroslav Lisik 2021-07-09 07:07:35 UTC 
Test:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.8-3.el8.x86_64

A) moving last resource from a *group*
[root@r8-node-01 ~]# pcs resource
NO resources configured
[root@r8-node-01 ~]# for i in $(seq -w 01 03); do pcs resource create d-$i ocf:pacemaker:Dummy; done
[root@r8-node-01 ~]# pcs resource group add gr1 d-01
[root@r8-node-01 ~]# pcs constraint order gr1 then d-02
Adding gr1 d-02 (kind: Mandatory) (Options: first-action=start then-action=start)
[root@r8-node-01 ~]# pcs resource group add gr2 d-01 d-03
Error: Unable to move resource 'd-01' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue
[root@r8-node-01 ~]# echo $?
1
[root@r8-node-01 ~]# pcs resource
  * d-02        (ocf::pacemaker:Dummy):  Started r8-node-01
  * d-03        (ocf::pacemaker:Dummy):  Started r8-node-02
  * Resource Group: gr1:
    * d-01      (ocf::pacemaker:Dummy):  Started r8-node-03
[root@r8-node-01 ~]# pcs resource ungroup gr1
Removing Constraint - order-gr1-d-02-mandatory
[root@r8-node-01 ~]# pcs resource
  * d-02        (ocf::pacemaker:Dummy):  Started r8-node-01
  * d-03        (ocf::pacemaker:Dummy):  Started r8-node-02
  * d-01        (ocf::pacemaker:Dummy):  Started r8-node-01
[root@r8-node-01 ~]# pcs resource group add gr2 d-01 d-03
[root@r8-node-01 ~]# pcs resource
  * d-02        (ocf::pacemaker:Dummy):  Started r8-node-01
  * Resource Group: gr2:
    * d-01      (ocf::pacemaker:Dummy):  Started r8-node-01
    * d-03      (ocf::pacemaker:Dummy):  Started r8-node-01

B) moving last resource from a *cloned group*
[root@r8-node-01 ~]# pcs resource
NO resources configured
[root@r8-node-01 ~]# for i in $(seq -w 01 03); do pcs resource create d-$i ocf:pacemaker:Dummy; done
[root@r8-node-01 ~]# pcs resource group add gr1 d-01
[root@r8-node-01 ~]# pcs resource clone gr1
[root@r8-node-01 ~]# pcs constraint order gr1-clone then d-02
Adding gr1-clone d-02 (kind: Mandatory) (Options: first-action=start then-action=start)
[root@r8-node-01 ~]# pcs resource group add gr2 d-02 d-03
[root@r8-node-01 ~]# pcs resource
  * Clone Set: gr1-clone [gr1]:
    * Started: [ r8-node-01 r8-node-02 r8-node-03 ]
  * Resource Group: gr2:
    * d-02      (ocf::pacemaker:Dummy):  Started r8-node-02
    * d-03      (ocf::pacemaker:Dummy):  Started r8-node-02
[root@r8-node-01 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start gr1-clone then start d-02 (kind:Mandatory)
Colocation Constraints:
Ticket Constraints:

[root@r8-node-01 ~]# pcs resource group add gr3 d-02 d-01 d-03
Error: Unable to move resources 'd-02', 'd-03' as it would leave group 'gr2' empty. Please, use the 'pcs resource ungroup gr2' command first.
Error: Unable to move resource 'd-01' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

[root@r8-node-01 ~]# pcs resource ungroup gr2
[root@r8-node-01 ~]# pcs resource ungroup gr1
[root@r8-node-01 ~]# pcs resource
  * Clone Set: gr1-clone [d-01]:
    * Started: [ r8-node-01 r8-node-02 r8-node-03 ]
  * d-02        (ocf::pacemaker:Dummy):  Started r8-node-02
  * d-03        (ocf::pacemaker:Dummy):  Started r8-node-01
[root@r8-node-01 ~]# pcs resource group add gr3 d-02 d-01 d-03
Error: 'd-01' is a clone resource, clone resources cannot be put into a group
Error: Errors have occurred, therefore pcs is unable to continue

[root@r8-node-01 ~]# pcs resource unclone d-01
[root@r8-node-01 ~]# pcs resource group add gr3 d-02 d-01 d-03
[root@r8-node-01 ~]# pcs resource
  * Resource Group: gr3:
    * d-02      (ocf::pacemaker:Dummy):  Started r8-node-02
    * d-01      (ocf::pacemaker:Dummy):  Started r8-node-02
    * d-03      (ocf::pacemaker:Dummy):  Started r8-node-02
[root@r8-node-01 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
Colocation Constraints:
Ticket Constraints:
Comment 22 Michal Mazourek 2021-07-22 15:35:17 UTC 
BEFORE:
=======

[root@virt-267 ~]# rpm -q pcs
pcs-0.10.8-1.el8.x86_64


## Create resource dummy1 and add it to group gr1, create another resource dummy-constraint and set order constraint with the group

[root@virt-267 ~]# pcs resource create dummy1 ocf:pacemaker:Dummy
[root@virt-267 ~]# pcs resource group add gr1 dummy1
[root@virt-267 ~]# pcs resource
  * Resource Group: gr1:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-267

[root@virt-267 ~]# pcs resource create dummy-constraint ocf:pacemaker:Dummy
[root@virt-267 ~]# pcs constraint order start gr1 then dummy-constraint
Adding gr1 dummy-constraint (kind: Mandatory) (Options: first-action=start then-action=start)
[root@virt-267 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start gr1 then start dummy-constraint (kind:Mandatory)
Colocation Constraints:
Ticket Constraints:

## Moving dummy1 (as the last resource in gr1) from the group

[root@virt-267 ~]# pcs resource group add gr2 dummy1
{cib output}
[root@virt-267 ~]# echo $?
1


AFTER:
======

[root@virt-487 ~]# rpm -q pcs
pcs-0.10.8-3.el8.x86_64


## Create resource dummy1 and add it to group gr1, create another resource dummy-constraint and set order constraint with the group

[root@virt-487 ~]# pcs resource create dummy1 ocf:pacemaker:Dummy
[root@virt-487 ~]# pcs resource group add gr1 dummy1
root@virt-487 ~]# pcs resource
  * Resource Group: gr1:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487

[root@virt-487 ~]# pcs resource create dummy-constraint ocf:pacemaker:Dummy
[root@virt-487 ~]# pcs constraint order start gr1 then dummy-constraint
Adding gr1 dummy-constraint (kind: Mandatory) (Options: first-action=start then-action=start)
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start gr1 then start dummy-constraint (kind:Mandatory)
Colocation Constraints:
Ticket Constraints:

## Moving dummy1 (as the last resource in gr1) from the group

[root@virt-487 ~]# pcs resource group add gr2 dummy1
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue
[root@virt-487 ~]# echo $?
1
[root@virt-487 ~]# pcs resource
  * Resource Group: gr1:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492

> OK: Moving last resource from a group with a constraint doesn't result in an invalid CIB and convenient error message is shown instead.

## Ungrouping gr1 first, as hinted in the error message

[root@virt-487 ~]# pcs resource ungroup gr1
Removing Constraint - order-gr1-dummy-constraint-mandatory
[root@virt-487 ~]# echo $?
0
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
Colocation Constraints:
Ticket Constraints:

> OK: The ungrouping removed the constraint

[root@virt-487 ~]# pcs resource group add gr2 dummy1
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492
  * Resource Group: gr2:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487

> OK: No problem adding dummy1 to gr2 now

## Moving last resource from a group without a constraint

[root@virt-487 ~]# pcs resource group add gr1 dummy1
[root@virt-487 ~]# echo $?
0
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492
  * Resource Group: gr1:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487

> OK: gr2 is deleted and the resource is in gr1


## Cloning the group gr1 and adding a constraint

[root@virt-487 ~]# pcs resource clone gr1
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492
  * Clone Set: gr1-clone [gr1]:
    * Started: [ virt-487 virt-492 ]

[root@virt-487 ~]# pcs constraint order gr1-clone then dummy-constraint
Adding gr1-clone dummy-constraint (kind: Mandatory) (Options: first-action=start then-action=start)
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start gr1-clone then start dummy-constraint (kind:Mandatory)
Colocation Constraints:
Ticket Constraints:

root@virt-487 ~]# pcs resource group add gr2 dummy1
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue
[root@virt-487 ~]# echo $?
1
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492
  * Clone Set: gr1-clone [gr1]:
    * Started: [ virt-487 virt-492 

> OK

[root@virt-487 ~]# pcs resource ungroup gr1
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492
  * Clone Set: gr1-clone [dummy1]:
    * Started: [ virt-487 virt-492 ]
[root@virt-487 ~]# pcs resource unclone dummy1
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492
  * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
Colocation Constraints:
Ticket Constraints:


## Multiple resources in a group with a constraint

[root@virt-487 ~]# pcs resource create dummy2 ocf:pacemaker:Dummy
[root@virt-487 ~]# pcs resource create dummy3 ocf:pacemaker:Dummy

[root@virt-487 ~]# pcs resource group add gr1 dummy1 dummy2 dummy3
[root@virt-487 ~]# pcs constraint order start gr1 then dummy-constraint
Adding gr1 dummy-constraint (kind: Mandatory) (Options: first-action=start then-action=start)
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-492
  * Resource Group: gr1:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487
    * dummy2	(ocf::pacemaker:Dummy):	 Started virt-487
    * dummy3	(ocf::pacemaker:Dummy):	 Started virt-487

## removing all resources at once

[root@virt-487 ~]# pcs resource group add gr2 dummy1 dummy2 dummy3
Error: Unable to move resources 'dummy1', 'dummy2', 'dummy3' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

> OK

## removing resources one by one

[root@virt-487 ~]# pcs resource group add gr2 dummy1
[root@virt-487 ~]# pcs resource group add gr2 dummy2
[root@virt-487 ~]# pcs resource group add gr2 dummy3
Error: Unable to move resource 'dummy3' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

> OK

[root@virt-487 ~]# pcs resource ungroup gr1
Removing Constraint - order-gr1-dummy-constraint-mandatory
[root@virt-487 ~]# pcs resource ungroup gr2


## Testing various constraint types

[root@virt-487 ~]# pcs resource group add gr1 dummy1 
[root@virt-487 ~]# pcs constraint order start dummy-constraint then gr1
Adding dummy-constraint gr1 (kind: Mandatory) (Options: first-action=start then-action=start)
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  start dummy-constraint then start gr1 (kind:Mandatory)
Colocation Constraints:
Ticket Constraints:

[root@virt-487 ~]# pcs resource group add gr2 dummy1
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

> OK


[root@virt-487 ~]# pcs constraint remove order-dummy-constraint-gr1-mandatory

[root@virt-487 ~]# pcs constraint colocation add gr1 with dummy-constraint
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
Colocation Constraints:
  gr1 with dummy-constraint (score:INFINITY)
Ticket Constraints:

[root@virt-487 ~]# pcs resource group add gr2 dummy1
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

> OK


[root@virt-487 ~]# pcs constraint remove colocation-gr1-dummy-constraint-INFINITY

[root@virt-487 ~]# pcs constraint order set gr1 dummy-constraint dummy2
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
  Resource Sets:
    set gr1 dummy-constraint dummy2
Colocation Constraints:
Ticket Constraints:

[root@virt-487 ~]# pcs resource group add gr2 dummy1
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

> OK


[root@virt-487 ~]# pcs constraint remove order_set_g1dtd2

[root@virt-487 ~]# pcs constraint colocation set gr1 dummy-constraint dummy2
[root@virt-487 ~]# pcs constraint
Location Constraints:
Ordering Constraints:
Colocation Constraints:
  Resource Sets:
    set gr1 dummy-constraint dummy2 setoptions score=INFINITY
Ticket Constraints:

[root@virt-487 ~]# pcs resource group add gr2 dummy1
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

> OK


[root@virt-487 ~]# pcs constraint remove colocation_set_g1dtd2

[root@virt-487 ~]# pcs constraint location gr1 prefers virt-487
[root@virt-487 ~]# pcs constraint
Location Constraints:
  Resource: gr1
    Enabled on:
      Node: virt-487 (score:INFINITY)
Ordering Constraints:
Colocation Constraints:
Ticket Constraints:

[root@virt-487 ~]# pcs resource group add gr2 dummy1
Error: Unable to move resource 'dummy1' as it would leave group 'gr1' empty. Please, use the 'pcs resource ungroup gr1' command first.
Error: Errors have occurred, therefore pcs is unable to continue

> OK


[root@virt-487 ~]# pcs constraint remove location-gr1-virt-487-INFINITY

[root@virt-487 ~]# pcs constraint location dummy1 prefers virt-487
[root@virt-487 ~]# pcs constraint
Location Constraints:
  Resource: dummy1
    Enabled on:
      Node: virt-487 (score:INFINITY)
Ordering Constraints:
Colocation Constraints:
Ticket Constraints:
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-487
  * dummy3	(ocf::pacemaker:Dummy):	 Started virt-492
  * dummy2	(ocf::pacemaker:Dummy):	 Started virt-487
  * Resource Group: gr1:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487
[root@virt-487 ~]# pcs resource group add gr2 dummy1
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-487
  * dummy3	(ocf::pacemaker:Dummy):	 Started virt-492
  * dummy2	(ocf::pacemaker:Dummy):	 Started virt-487
  * Resource Group: gr2:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-487

> OK: The constraint on the resource itself doesn't prevent deleting the empty group


## Testing with tag: Moving last resource from a group that is in tag 

[root@virt-487 ~]# pcs constraint remove location-dummy1-virt-487-INFINITY
[root@virt-487 ~]# pcs resource group add gr1 dummy1
[root@virt-487 ~]# pcs tag create tag1 gr1
[root@virt-487 ~]# pcs tag
tag1
  gr1

[root@virt-487 ~]# pcs resource group add gr2 dummy1
[root@virt-487 ~]# pcs resource
  * dummy-constraint	(ocf::pacemaker:Dummy):	 Started virt-487
  * dummy3	(ocf::pacemaker:Dummy):	 Started virt-492
  * dummy2	(ocf::pacemaker:Dummy):	 Started virt-487
  * Resource Group: gr2:
    * dummy1	(ocf::pacemaker:Dummy):	 Started virt-492
[root@virt-487 ~]# pcs tag
tag1
  gr1

> Bug: Tag exists with non-existent group. This will be resolved once bz1420298 is done, as mentioned in comment 21.


Marking as VERIFIED in pcs-0.10.8-3.el8
Comment 24 errata-xmlrpc 2021-11-09 17:33:12 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 (Low: pcs security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:4142
Note You need to log in before you can comment on or make changes to this bug.