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.
DescriptionJan Pokorný [poki]
2015-11-11 14:26:23 UTC
We will see if there is something we can do to accommodate qdisk users
in the old cluster stack in the conversion process to the new one if
it already contains quorum device discussed in the referred bug:
+++ This bug was initially created as a clone of Bug #614122 +++
Because qdevice (at least net model) is completely different from old cman qdisk I can see only two "convertible" sections:
- logging. Subsystem name is QDEVICE. Supported options are to_stderr, to_syslog, syslog_facility, syslog_priority, logfile_priority, debug, fileline, timestamp and function_name. to_logfile and logfile are not supported
- number of qdevice votes. stored in quorum.device.votes key
I would suggest to ether let this BZ open till we get disk model which in theory may be more "compatible" with old qdisk so more options may be "convertible" or we can open new one for 7.4.
Comment 4Jan Pokorný [poki]
2016-06-17 15:37:58 UTC
Honzo, if I understand [comment 2] correctly, the two mentioned sections
are global (regardless of model) and are relatively stable.
Can you confirm, please?
Comment 7Jan Pokorný [poki]
2017-05-30 15:39:56 UTC
Likewise, pushing further to 7.5.
Comment 9Jan Pokorný [poki]
2017-11-07 15:56:39 UTC
Capacity asks for postponing for 7.6 consideration.
Comment 10Jan Pokorný [poki]
2017-11-07 17:41:15 UTC
Actually what's new for 7.5, heuristics (see recently added Depends On
bugs), will get addressed as a matter of rebase [bug 1509381], this bug
then remains a sliding tracker of the progress in other components clufter
should respond to, till the corosync quorum device support gets settled
(expected after "disk" model is present?).
Comment 15RHEL Program Management
2022-04-27 07:30:45 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.