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.

Bug 2095695

Summary: Cannot remove a quorum device
Product: Red Hat Enterprise Linux 9 Reporter: Nina Hostakova <nhostako>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: high Docs Contact:
Priority: high    
Version: 9.1CC: cluster-maint, idevat, mlisik, mmazoure, mpospisi, omular, tojeline
Target Milestone: rcKeywords: EasyFix, Regression, Triaged
Target Release: 9.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.11.3-1.el9 Doc Type: No Doc Update
Doc Text:
The affected packages have never been released.
Story Points: ---
Clone Of:
: 2115326 (view as bug list) Environment:
Last Closed: 2022-11-15 09:49:30 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:

Description Nina Hostakova 2022-06-10 09:14:43 UTC
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 2 Tomas Jelinek 2022-06-14 08:52:50 UTC
Upstream patch: https://github.com/ClusterLabs/pcs/commit/0608c99c32a495522fd00dae20c45db5d9e52f91

Reproducer / test in comment 0

Comment 3 Miroslav Lisik 2022-06-24 13:10:56 UTC
DevTestResults:

[root@r91-1 pcs]# rpm -q pcs
pcs-0.11.3-1.el9.x86_64

Setup quorum device on some other node:

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

Add quorum device to the cluster:

[root@r91-1 pcs]# pcs quorum device add model net host=r91-3 algorithm=lms
Setting up qdevice certificates on nodes...
r91-1: Succeeded
r91-2: Succeeded
Enabling corosync-qdevice...
r91-2: not enabling corosync-qdevice: corosync is not enabled
r91-1: not enabling corosync-qdevice: corosync is not enabled
Sending updated corosync.conf to nodes...
r91-1: Succeeded
r91-2: Succeeded
r91-1: Corosync configuration reloaded
Starting corosync-qdevice...
r91-2: corosync-qdevice started
r91-1: corosync-qdevice started

Remove quorum device:

[root@r91-1 pcs]# pcs quorum device remove
Disabling corosync-qdevice...
r91-1: corosync-qdevice disabled
r91-2: corosync-qdevice disabled
Stopping corosync-qdevice...
r91-2: corosync-qdevice stopped
r91-1: corosync-qdevice stopped
Removing qdevice certificates from nodes...
r91-2: Succeeded
r91-1: Succeeded
Sending updated corosync.conf to nodes...
r91-1: Succeeded
r91-2: Succeeded
r91-1: Corosync configuration reloaded

Comment 9 errata-xmlrpc 2022-11-15 09:49:30 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:7935