Bug 2226031

Summary: Make Hostid compliant with TP-4126
Product: Red Hat Enterprise Linux 9 Reporter: John Meneghini <jmeneghi>
Component: nvme-cliAssignee: John Meneghini <jmeneghi>
Status: CLOSED MIGRATED QA Contact: Zhang Yi <yizhan>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.3CC: tbzatek
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: NVMe_P0
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-11 02:19:52 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:

Description John Meneghini 2023-07-25 18:42:45 UTC
Description of problem:

The nvme-cli rpm install script currently generates a random UUID string for the /etc/nvme/hostid.  This is not compliant with TP-4126, which says:
 
[The] OS environment should use a fixed platform UUID to create a HostNQN and HostID. The implementation should use the System UUID found in the SMBIOS table. The System Management BIOS (SMBIOS) Reference Specification is described in DSP0134. 

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

nvme-cli-2.4-8.el9

How reproducible:

install the rpm.

Actual results:

# find /etc/nvme/ -type f -exec cat {}  \; -print
nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0034-5310-8057-b2c04f355333
/etc/nvme/hostnqn
11c85b31-28df-4521-9ee9-bbab42cc0607 <<
/etc/nvme/hostid


Expected results:

# find /etc/nvme/ -type f -exec cat {}  \; -print
nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0034-5310-8057-b2c04f355333
/etc/nvme/hostnqn
4c4c4544-0034-5310-8057-b2c04f355333 <<
/etc/nvme/hostid

Additional info:

Comment 3 RHEL Program Management 2023-08-11 02:19:52 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.