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.
Bug 1387165 - corosync logs using incorrect subsystem name on PPC64LE
Summary: corosync logs using incorrect subsystem name on PPC64LE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libqb
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: Chris Mackowski
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 09:30 UTC by Christine Caulfield
Modified: 2017-08-01 18:00 UTC (History)
5 users (show)

Fixed In Version: libqb-1.0-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 18:00:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1896 0 normal SHIPPED_LIVE libqb bug fix and enhancement update 2017-08-01 18:04:56 UTC

Description Christine Caulfield 2016-10-20 09:30:47 UTC 
Description of problem:

Corosync log messages are tagged as YKD when then should be VOTEQ or TOTEM

Version-Release number of selected component (if applicable):
7.3

How reproducible:
Always

Steps to Reproduce:
1. Enable logging for corosync & start it

Actual results:
Many log messages are logged as [YKD  ] instead of [VOTEQ] or [TOTEM]

Expected results:
Log messages should have the correct subsystem tag

Additional info:
Oct 13 14:45:07 europa qarshd[87326]: Running cmdline: /usr/tests/sts-rhel7.3/gfs/bin/checkslab
Oct 13 14:45:13 europa corosync[72227]: [TOTEM ] A new membership (10.15.104.73:1168) was formed. Members left: 1
Oct 13 14:45:13 europa corosync[72227]: [TOTEM ] Failed to receive the leave message. failed: 1
Oct 13 14:45:13 europa crmd[72249]: warning: No reason to expect node 1 to be down
Oct 13 14:45:13 europa crmd[72249]:  notice: Stonith/shutdown of io not matched
Oct 13 14:45:13 europa crmd[72249]:  notice: State transition S_IDLE -> S_POLICY_ENGINE
Oct 13 14:45:14 europa corosync[72227]: [YKD   ] Members[1]: 2
Oct 13 14:45:14 europa stonith-ng[72245]:  notice: Node io state is now lost
Oct 13 14:45:14 europa corosync[72227]: [YKD   ] Completed service synchronization, ready to provide service.
Oct 13 14:45:14 europa kernel: dlm: closing connection to node 1
Oct 13 14:45:14 europa dlm_controld[72421]: 170957 fence request 1 pid 87332 nodedown time 1476387913 fence_all dlm_stonith
Comment 1 Christine Caulfield 2016-10-20 09:33:19 UTC 
The patch for libqb is upstream

commit b40c499d7de6a9abca20aa1ad7917b5a99b0c208
Author: Christine Caulfield <ccaulfie>
Date:   Tue Oct 18 14:30:28 2016 +0100

    log: Don't overwrite valid tags
    
    If a tag of 0 is passed into the logger and an existing callsite
    is found with a non-zero tag, the don't overwrite the existing tag.
    
    Signed-off-by: Christine Caulfield <ccaulfie>

diff --git a/lib/log.c b/lib/log.c
index 5f8463a..f10321e 100644
--- a/lib/log.c
+++ b/lib/log.c
@@ -352,8 +352,10 @@ qb_log_callsite_get(const char *function,
                        _custom_filter_fn(cs);
                }
                pthread_rwlock_unlock(&_listlock);
-       } else if (cs->tags != tags) {
-               cs->tags = tags;
+       } else {
+               if (tags && cs->tags != tags) {
+                       cs->tags = tags;
+               }
                if (_custom_filter_fn) {
                        _custom_filter_fn(cs);
                }
Comment 6 errata-xmlrpc 2017-08-01 18:00:14 UTC 
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://access.redhat.com/errata/RHBA-2017:1896
Note You need to log in before you can comment on or make changes to this bug.