Hypervisor List Fails With "500 Internal Server" Error When Using Compute API Microversion
Problem
The openstack hypervisor list command fails with a 500 Internal Server Error, even though nova hypervisor-list and openstack hypervisor show <ID> work as expected.
The failure occurs specifically when querying the /os-hypervisors/detail API endpoint, which is used by the OpenStack unified client. For Self-Hosted PCD users, the nova-api-osapipod logs shows repeated warnings about invalid UUIDs, such as:
Invalid uuid: nova. To ensure interoperability, identifiers should be a valid uuid.Environment
Private Cloud Director Virtualization - v2025.4 and Higher
Self-Hosted Private Cloud Director Virtualization - v2025.4 and Higher
Component: OpenStack-CLI version 8.1.0 and above.
Cause
This is an expected behavior, starting from Compute API micro version 2.53, Nova replaced integer-based service and hypervisor IDs with UUIDs to ensure global uniqueness across multi-cell deployments.
In upgraded environments (from pre-Newton/Ocata releases), the compute_nodes or services tables may still contain old non-UUID identifiers (e.g., nova, compute-01, or blank fields).
When /os-hypervisors/detail is queried using microversion ≥ 2.53, Nova attempts to serialize these IDs as UUIDs. If invalid values are encountered, an internal Python OSError or ValueError is raised, leading to the 500 error.
Older microversions (≤ 2.52) continue to work as they still rely on integer-based IDs and do not enforce UUID validation.
Diagnostics
Command failure observed:
Verification using older micro version:
Resolution
Run with a supported micro version ≤ 2.52 (before UUID enforcement):
Validation
Command working after using older microversion:
The command should return a valid hypervisor list with no 500 errors, and For Self Hosted PCD users, nova-api-osapi pod logs should no longer display “Invalid uuid” warnings.
Additional Information
References:
Last updated