Bug 1018091
| Summary: | Votequorum module logs as QUORUM instead of VOTEQ | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Christine Caulfield <ccaulfie> |
| Component: | libqb | Assignee: | David Vossel <dvossel> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | ccaulfie, cluster-maint, dvossel, fdinitto, jkortus, sdake |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | libqb-0.16.0-4.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 13:00:45 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: | |||
I have narrowed this down to what I think is a libqb bug (or maybe a feature). it seems the file matching algorithm in log.c function _cs_matches_filter_ doesn't distinguish between votequorum.c and quorum.c because the latter is contained in the former. If there are some quorum.c filters defined AFTER votequorum.c filters then they get applied and the tags get set to 1 [QUORUM] instead of 7 [VOTEQ ] Ping me on IRC if you need more information. libqb issue ref: https://github.com/ClusterLabs/libqb/issues/94 There is now an upstream patch related to this issue. https://github.com/ClusterLabs/libqb/commit/9abb68637d6d448cccfa06daa05d9c5bf59f5d3e This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |
Description of problem: If I enable votequorum logging in corosync.conf as below, the log messages come tagged as [QUORUM] instead of [VOTEQ] logging { to_syslog: yes logger_subsys { subsys: VOTEQ debug: on } } Version-Release number of selected component (if applicable): 7.0 How reproducible: Every time Steps to Reproduce: 1. Add logging stanza to corosync.conf 2. Enable debug logging in rsyslog.conf 3. read syslog file Actual results: votequorum log messages come out prefixed with [QUORUM] Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] got nodeinfo message from cluster node 4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] nodeinfo message[0]: votes: 0, expected: 0 flags: 0 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] total_votes=4, expected_votes=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 1 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 2 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 3 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 4 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] lowest node id: 1 us: 2 Expected results: Log messages should match the subsystem requested in corosync.conf. In this case [VOTEQ ] Additional info: