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 1525348 - multipath: "spurious uevent, path already in pathvec" errors
Summary: multipath: "spurious uevent, path already in pathvec" errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: device-mapper-multipath
Version: 7.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ben Marzinski
QA Contact: Lin Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-13 06:19 UTC by Vansen Ng
Modified: 2023-09-15 00:05 UTC (History)
9 users (show)

Fixed In Version: device-mapper-multipath-0.4.9-119.el7
Doc Type: Bug Fix
Doc Text:
Cause: multipathd was logging a notification message at the error severity level. Consequence: Customers logging for error messages n the logs could think that something was wrong with multipathd Fix: The message severity level has been moved down to notice. Result: Customers will no longer see these messages when scanning the logs for error severity messages.
Clone Of:
Environment:
Last Closed: 2018-04-10 16:13:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0884 0 None None None 2018-04-10 16:14:06 UTC

Description Vansen Ng 2017-12-13 06:19:07 UTC 
Description of problem:

The following messages appear in /var/log/messages, when server is booting up.


---
[rhel7u4]$ cat var/log/messages|grep "spurious uevent"
Dec  7 18:27:33 <daemon.err> rhel7u4 multipathd:sde: spurious uevent, path already in pathvec
Dec  7 18:27:33 <daemon.err> rhel7u4 multipathd:sdb: spurious uevent, path already in pathvec
Dec  7 18:27:33 <daemon.err> rhel7u4 multipathd:sdc: spurious uevent, path already in pathvec
Dec  7 18:27:33 <daemon.err> rhel7u4 multipathd:sdd: spurious uevent, path already in pathvec
---

Per the confirmation with other senior engineer, it mentioned that these are informational only, it is harmless and could be ignored safely. 
Could you please advise why such messages are classified as "daemon.err" in /var/log/messages? Is it possible to make it shown as "daemon.info" or "daemon.notice" in /var/log/messages?  Please advise. thank you


Version-Release number of selected component (if applicable):
rhel7u4 with kernel-3.10.0-693.2.2.el7.x86_64
device-mapper-multipath-0.4.9-111.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Could you please advise why such messages are classified as "daemon.err" in /var/log/messages, if they are harmless? Is it possible to make it shown as "daemon.info" or "daemon.notice" in /var/log/messages?


Additional info:
Comment 2 Vansen Ng 2017-12-13 06:33:39 UTC 
Since Customer have a batch of server which would be online(production) soon, their monitoring system are sensitive to such "daemon.err" messages. 

So, I will put this BZ severity as high, please kindly let me know, if you have any concerns. 

Thank you

Vansen Ng
Comment 4 Ben Marzinski 2017-12-13 18:16:09 UTC 
There is no good reason for them to have that severity. I'm fine with moving them down to a Notice. I'm not sure that there is time for this to make RHEL-7.5, not that I have any objection to it going in.  If the bug gets all its ACKs, I'd have no worries about making this change.
Comment 5 Vansen Ng 2017-12-14 06:09:14 UTC 
Thanks for the clarification.  Please kindly check if we have any plan to fix it in coming version or we have any other reason to keep the current severity of such messages.  

Thank you
Customer Experience and Engagement, Red Hat
Comment 9 Ben Marzinski 2018-01-31 19:49:12 UTC 
I've moved the level of these messages down to a notice.
Comment 16 errata-xmlrpc 2018-04-10 16:13:30 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/RHEA-2018:0884
Comment 18 Red Hat Bugzilla 2023-09-15 00:05:41 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Note You need to log in before you can comment on or make changes to this bug.