Red Hat Bugzilla – Bug 961906
RHEV upgrade 3.0-3.1 host error reason: no BIOS UUID
Last modified: 2016-02-10 14:10:55 EST
Description of problem:
Upgrade from 3.0 to 3.1 with RHEL host
the error stated:
During the upgrade process, RHEV Manager will not be accessible.
All existing running virtual machines will continue but you will not be able to
start or stop any new virtual machines during the process.
Would you like to proceed? (yes|no): yes
Stopping ovirt-engine service... [ DONE ]
Stopping DB related services... [ DONE ]
Pre-upgrade validations... [ ERROR ]
Pre-upgade host UUID validation failed
Please move the following hosts to maintenance mode before upgrade:
- Host example.com, reason: no BIOS UUID
Version-Release number of selected component (if applicable):3.0-3.1
How reproducible: very
Steps to Reproduce:
1. upgrade with host running
does the host has a BIOS UUID? we stopped being forgiving to these in 3.1.
there are work arounds if you can't fix the host firmware to have a BIOS UUID, but iirc, these are post upgrade.
execute on host:
# dmidecode -s system-uuid
IIUC - the host does not have a bios UUID and we prevent the upgrade on those cases.
IIRC the workaround should be remove the host from engine and than adding it again.
Am I missing something ?
(In reply to comment #3)
> IIUC - the host does not have a bios UUID and we prevent the upgrade on
> those cases.
> IIRC the workaround should be remove the host from engine and than adding it
> Am I missing something ?
You put host in maintenance before upgrade, then after upgrade you reinstall it.
You do not require to remove/add it.
I ran dmidecode against the sosreport and found the system UUID as not settable.
Product Name: ProLiant BL460c G1
Version: Not Specified
UUID: Not Settable
I looked into this and found it to be something from HP's side. I found a way to get the system a UUID though.
Go into the HP Bios Advanced Option>Services Options. There you’ll find Serial Number and Product ID. Locate these number on your server case and set them. When the numbers are set the server should automaticaly generate UUID.
Customer confirmed it resolved their issue.