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.
Fantastic - looking forward to this, the current version of libqb in 7.2 is causing us major issues with crashing Corosync and taking nodes offline etc...
Sorry for my ignorance but is there a place to get the new libqb-1.0-1.el7 version of the package in advance of it's release so that I may test it - I can't see it in fasttrack etc...?
Thanks Christine, no worries, I've built my own package for RHEL / CentOS 7.2 from source.
I've uploaded the built packages (including the SRPM) in case anyone else wants them for any reason: https://packagecloud.io/app/mrmondo/pacemaker/search?q=libqb
FYI - after upgrading to libqb-1.0 on our 7.2 servers we have no longer experienced the problems with corosync crashing that were causing us major issues.
Comment 10Christine Caulfield
2016-06-06 07:24:43 UTC
Thanks for the feedback!
Comment 11Jan Pokorný [poki]
2016-06-06 21:53:12 UTC
(In reply to Jan Pokorný from comment #12)
> Might be worthy new respin:
> https://github.com/ClusterLabs/libqb/issues/215
I agree, the blackbox component of Pacemaker is very useful when debugging issues, I would consider this a medium severity regression if this was to be broken.
Comment 14Christine Caulfield
2016-06-20 07:17:11 UTC
That issue isn't a regression, it's an unimplemented feature. In fact it only came up because a recent patch to pacemaker used the %z modifier. As I understand it that Pacemaker patch will be removed anyway so that earlier libqb versions can be supported.
I'll put this patch into libqb, of course, but it has no impact on existing code so it will go out in the next minor release.
Pacemaker has been updated not to use %z as of commit 380c1bb, which will be part of the 1.1.15 release. No Pacemaker release, whether upstream or in RHEL, will have a problem with older versions of corosync.
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, 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://rhn.redhat.com/errata/RHBA-2016-2363.html