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 2115326 - Cannot remove a quorum device
Summary: Cannot remove a quorum device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.7
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-04 12:28 UTC by Nina Hostakova
Modified: 2022-11-08 09:26 UTC (History)
9 users (show)

Fixed In Version: pcs-0.10.14-3.el8
Doc Type: No Doc Update
Doc Text:
The affected packages have never been released.
Clone Of: 2095695
Environment:
Last Closed: 2022-11-08 09:14:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-130301 0 None None None 2022-08-04 12:35:38 UTC
Red Hat Product Errata RHSA-2022:7447 0 None None None 2022-11-08 09:14:07 UTC

Description Nina Hostakova 2022-08-04 12:28:50 UTC 
+++ This bug was initially created as a clone of Bug #2095695 +++

Description of problem:
Having a quorum device configured, its removal ends up with an error

Version-Release number of selected component (if applicable):
pcs-0.11.2-1.el9

How reproducible:
always

Steps to Reproduce:
1.# pcs quorum device remove 
Disabling corosync-qdevice...
virt-004: corosync-qdevice disabled
virt-019: corosync-qdevice disabled
virt-003: corosync-qdevice disabled
Stopping corosync-qdevice...
virt-003: corosync-qdevice stopped
virt-004: corosync-qdevice stopped
virt-019: corosync-qdevice stopped
Removing qdevice certificates from nodes...
Error: virt-003: Error: option --qdevice not recognized

Usage: pcs [-f file] [-h] [commands]...
Control and configure pacemaker and corosync.

Options:
{...}
Comment 5 Tomas Jelinek 2022-08-08 07:41:06 UTC 
Upstream patch: https://github.com/ClusterLabs/pcs/commit/27d0993cea9615899ec4a6541c7e8c2997ed6b89

Reproducer / test in comment 0
Comment 6 Miroslav Lisik 2022-08-08 14:42:32 UTC 
DevTestResults:

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


### Setup qdevice on a node not in the cluster:

[root@r8-node-03 ~]# rpm -q pcs corosync-qnetd
pcs-0.10.14-3.el8.x86_64
corosync-qnetd-3.0.1-1.el8.x86_64

[root@r8-node-03 ~]# pcs qdevice setup model net --enable --start
Quorum device 'net' initialized
quorum device enabled
Starting quorum device...
quorum device started

[root@r8-node-03 ~]# pcs qdevice status net
QNetd address:                  *:5403
TLS:                            Supported (client certificate required)
Connected clients:              0
Connected clusters:             0

### Add qdevice to the cluster:

[root@r8-node-01 ~]# rpm -q pcs corosync-qdevice
pcs-0.10.14-3.el8.x86_64
corosync-qdevice-3.0.1-1.el8.x86_64

[root@r8-node-01 ~]# pcs quorum device add model net algorithm=ffsplit host=r8-node-03
Setting up qdevice certificates on nodes...
r8-node-01: Succeeded
r8-node-02: Succeeded
Enabling corosync-qdevice...
r8-node-01: not enabling corosync-qdevice: corosync is not enabled
r8-node-02: not enabling corosync-qdevice: corosync is not enabled
Sending updated corosync.conf to nodes...
r8-node-01: Succeeded
r8-node-02: Succeeded
r8-node-01: Corosync configuration reloaded
Starting corosync-qdevice...
r8-node-01: corosync-qdevice started
r8-node-02: corosync-qdevice started
[root@r8-node-01 ~]# pcs quorum device status
Qdevice information
-------------------
Model:                  Net
Node ID:                1
Configured node list:
    0   Node ID = 1
    1   Node ID = 2
Membership node list:   1, 2

Qdevice-net information
----------------------
Cluster name:           HACluster
QNetd host:             r8-node-03:5403
Algorithm:              Fifty-Fifty split
Tie-breaker:            Node with lowest node ID
State:                  Connected


### Remove qdevice from the cluster:

[root@r8-node-01 ~]# pcs quorum device remove
Disabling corosync-qdevice...
r8-node-01: corosync-qdevice disabled
r8-node-02: corosync-qdevice disabled
Stopping corosync-qdevice...
r8-node-01: corosync-qdevice stopped
r8-node-02: corosync-qdevice stopped
Removing qdevice certificates from nodes...
r8-node-02: Succeeded
r8-node-01: Succeeded
Sending updated corosync.conf to nodes...
r8-node-01: Succeeded
r8-node-02: Succeeded
r8-node-01: Corosync configuration reloaded
Comment 12 errata-xmlrpc 2022-11-08 09:14:01 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 (Moderate: 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-2022:7447
Note You need to log in before you can comment on or make changes to this bug.