Red Hat Bugzilla – Bug 1299968
Rebase libqb to 1.0 for RHEL7.3
Last modified: 2016-11-04 00:40:41 EDT
libqb 1.0 contains several small fixes and also the split-logging facility needed for later versions of pacemaker.
*** Bug 1308505 has been marked as a duplicate of this bug. ***
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...?
I don't think I can add a related bug in BugZilla here, but this libqb upgrade will also apparently fix: https://bugzilla.redhat.com/show_bug.cgi?id=1114852#c64
Sam, there's no externally visible RHEL7.3 version of libqb yet, but there is a Fedora version and, of course, the source code is on github.
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.
Thanks for the feedback!
Sam, FYI, if you followed the right channels, you would be aware of
COPR builds I keep updated on regular basis (shortly after new release):
Might be worthy new respin:
(In reply to Jan Pokorný from comment #12)
> Might be worthy new respin:
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.
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.