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 1357058 - identifying block devices by persistent identifiers in journal entries
Summary: identifying block devices by persistent identifiers in journal entries
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.0
Hardware: All
OS: Linux
high
high
Target Milestone: beta
: 7.0
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 998695
Blocks: 727046 947660 1313485
TreeView+ depends on / blocked
 
Reported: 2016-07-15 15:22 UTC by mulhern
Modified: 2023-09-14 03:28 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 947636
Environment:
Last Closed: 2020-12-15 07:42:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 mulhern 2016-07-15 18:07:43 UTC 
It would be desirable to make it possible for a sysadmin to retrospectively examine the history of a specified physical device across boots as it appears in the journal. Currently, no such facility is available. The enhancement in journalctl supplied in response to BZ#947636 does not supply such a facility.

It would be necessary to base such a search on a record which contained a unique identifier for that specific device. Due to the reasons explained in BZ#947636, the _UDEV_DEVLINK field is not much use.

The existing, RHEL-specific solution to this problem is documented in BZ#1032711, but is expensive and not automatic, i.e., a reader of the log must still manually match up the device link information with the particular device node.

In general, and for many uses, it would be preferred if log entries which now only refer to a device node also contained sufficient information so that the physical device referred to could be automatically inferred and shown to the user.

The solution in BZ#1032711 has always been understood to be a temporary one. This BZ is the BZ for an as yet not determined permanent solution.
Comment 6 RHEL Program Management 2020-12-15 07:42:58 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 7 Red Hat Bugzilla 2023-09-14 03:28:10 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.