Bug 1881036 - System serial number is not detected, and dmidecode command is missing from the iso image
Summary: System serial number is not detected, and dmidecode command is missing from t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ori Amizur
QA Contact: Yuri Obshansky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-21 12:08 UTC by Udi Kalifon
Modified: 2020-09-22 12:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-22 12:39:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Udi Kalifon 2020-09-21 12:08:19 UTC
Description of problem:
I registered some hosts (libvirt) to the service and noticed that the serial number is not detected. I tried to run "dmidecode -s system-serial-number" in the discovery iso and the command is not even available there.


Version-Release number of selected component (if applicable):
Staging on Sep. 21


How reproducible:
100%


Steps to Reproduce:
1. Create a cluster
2. Download the discovery iso
3. Boot some libvirt machines with the iso


Actual results:
In the GUI after the machines register, the introspection data is missing the serial number

Comment 1 Ori Amizur 2020-09-22 09:55:36 UTC
ukalifon The dmidecode command is in the container, not in the machine.
We are using the baseboard-serial-number and not system-serial-number.
Serial number is not available on virtual machines.  We use system uuid (system-uuid) instead.
I suggest to close the issue.
cc: alazar


Note You need to log in before you can comment on or make changes to this bug.