Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
(In reply to Coiby from comment #4)
> Hi Kenny,
>
> As you may know, RHEL 7 is currently in Maintenance Support 2 Phase, can I
> close this bug if it's not a critical bug?
Depending on your definition on critical, this issue prevents the system from being registered and thus unable to attach a subscription or enable any repository and consume any content.
There is a workaround however.
(In reply to Kenny Tordeurs from comment #5)
> (In reply to Coiby from comment #4)
> > Hi Kenny,
> >
> > As you may know, RHEL 7 is currently in Maintenance Support 2 Phase, can I
> > close this bug if it's not a critical bug?
>
> Depending on your definition on critical, this issue prevents the system
> from being registered and thus unable to attach a subscription or enable any
> repository and consume any content.
> There is a workaround however.
If the workaround is troublesome and you want the bug to be fixed, could you dump the DMI data to a binary file and upload the file here?
$ dmidecode --dump-bin dump_bin
Description of problem: dmidecode is not "Not Settable" for hosts causing subscription-manager to malfunction. (all physical hosts are considered identical overwriting each others profiles) # dmidecode | grep -i uuid ~~~ UUID: Not Settable ~~~ # dmidecode -u | awk ' BEGIN { in1 = 0; hd = 0 } /, DMI type / { in1 = 0 } /Strings:/ { hd = 0 } { if (hd == 2) { printf "%s-%s\n", $1 $2, $3 $4 $5 $6 $7 $8; hd = 0 } } { if (hd == 1) { printf "UUID: %s-%s-%s-", $9 $10 $11 $12, $13 $14, $15 $16; hd = 2 } } /, DMI type 1,/ { in1 = 1 } /Header and Data:/ { if (in1 != 0) { hd = 1 } }' ~~~ UUID: 00000000-0000-0000-0000-000000000000 ~~~ Version-Release number of selected component (if applicable): # grep dmidecode installed-rpms ~~~ dmidecode-3.2-3.el7.x86_64 Wed May 13 08:48:34 2020 python-dmidecode-3.12.2-4.el7.x86_64 Wed May 13 08:48:50 2020 ~~~ How reproducible: Uncertain as the issue happens with following hardware: Vendor: American Megatrends Inc. Manufacturer: Supermicro Product Name: SYS-2028TP-HTR Steps to Reproduce: 1. 2. 3. Actual results: # dmidecode | grep -i uuid ~~~ UUID: Not Settable ~~~ Expected results: UUID to be set Additional info: Workaround is to manually set a uuid fact for subscription-manager. # echo '{"dmi.system.uuid": "a2d759f2-7c4b-4142-bca9-3e1770cce354"}' > /etc/rhsm/facts/dmi.system.uuid.facts Confirm it is set with: # subscription-manager facts | grep -i uuid