Instance failed after resize due to 'No disk at /var/lib/nova/instances/<VM ID>/disk'

Solution Verified - Updated -

Environment

  • Red Hat Openstack Platform 16.1

Issue

  • Why does the instance have the error No disk at /var/lib/nova/instances/<VM ID>/disk after it was resized?

  • The instance is volume-backed, was resized and not starts after a reboot.

Resolution

Rebuild the instance, so it will force database update.

(overcloud) [stack@director ~]$ openstack server rebuild <VM>

Root Cause

  • The resize was not properly finished due to volume could not be found.
  • The resize was performed after editing the current instance type and rebooting.

Diagnostic Steps

  • The server is in ERROR status and volume looks attached.
(overcloud) [stack@director ~]$ openstack server show <VM>
| fault                               | {'code': 404, 'created': '2023-05-11T01:54:53Z', 'message': 'No disk at /var/lib/nova/instances/<VM ID>/disk'} |
...
| status                              | ERROR |
...
| volumes_attached                    | delete_on_termination='False', id='<ID>' |
  • Volume status is reserved or error.
(overcloud) [stack@director ~]$ openstack volume show <Volume ID>

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments