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.
I have just filed several RFEs for diagnostic capabilities in pcs:
[Support RFE] pcs stonith kdump setup
https://bugzilla.redhat.com/show_bug.cgi?id=1774117
[Support RFE] pcs set up pcp collection
https://bugzilla.redhat.com/show_bug.cgi?id=1774132
[Support RFE] Make it easier to raise corosync totem token
https://bugzilla.redhat.com/show_bug.cgi?id=1774143
It would be great if all three of these (and any future diagnostic capabilities) could be deployed with a single command, such as:
# pcs diagnostics setup
# pcs cluster setup --with-diagnostics
The Red Hat Support team has long dealt with a high volume of customers asking for root-cause analysis of fence events or node-reboots, but in a standard configuration there is typically not enough information available to diagnose the cause, at least in the most common scenarios we see. Even when customers are actively interested in identifying the cause of their issues, they often struggle with all of the instructions they have to follow to roll out a diagnostic configuration. Or even more troubling and more frequent is that we recommend these steps but many customers just don't do it, and their support cases close without resolution.
We need to make it easier for customers to get the data that is needed to explain what's going wrong in their cluster and/or take the immediately useful steps that could help stabilize the cluster.
Comment 3RHEL Program Management
2021-05-19 07:30:22 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.