yahoo-eng-team team mailing list archive

Thread
Date

[Bug 2049852] [NEW] VM reboot issues

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Aravindh <2049852@xxxxxxxxxxxxxxxxxx>
Date: Fri, 19 Jan 2024 08:02:51 -0000
Reply-to: Bug 2049852 <2049852@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

Problem Statement: Creating VM from image work fine, but reboot of that
instance from openstack results in Error state.

Steps to re-create:

1. Create a VM from Openstack with Image as the source. VM is created successfully.
2. Now issue a openstack server reboot <VM>
3. Softreboot fails after sometime, and hard reboot is attempted, but it fails and moves the instance to an Error state.

Observations.

1. Weird thing I noticed is, when the instance is being created the nova
log shows this (Note the VOLUME ID)

2024-01-19 06:45:06.536 7 INFO nova.virt.block_device [req-
da372940-2784-4aba-881f-7636460efb46 req-
bffdffd6-7521-4450-9ab9-93bac32789e1 a828b4ad4d794e18ac9c6238e893522d
1f4d24639d564e40816d90be4cac8ecd - - default default] [instance:
330922ac-8333-4ee7-a634-0075a00f1fd7] Booting with volume-backed-image
0e1aa7ba-23cc-4ced-8aa2-c9f78535d435 at /dev/vda

2. The create volume (c22d487d-ab7a-4373-b69f-91cd02f32cc8) in openstack
does not match this ID at all.

3. openstack server show VM shows the correct volume ID as in 2.

4. During reboot issued though openstack, the multipath just fails and
nova logs are stuck at cleaning stale cinder volumes.

5. Reboot command from inside the VM work fine. (sudo reboot)

----

6. When I use volume as the source to create instance, I have none of
these problems. Nova log shows the correct volume ID during the creation
phase and reboot works great with no issues.

I can consistently reproduce this error.

Host OS - Ubuntu 22.04
Deployment - Kolla Ansible with Docker containers
Storage - Netapp with iSCSI
Hypervisor - KVM
Nova Version - 18.4.0

** Affects: nova
Importance: Undecided
Status: New

--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2049852

Title:
VM reboot issues

Status in OpenStack Compute (nova):
New

Bug description:
Problem Statement: Creating VM from image work fine, but reboot of
that instance from openstack results in Error state.

Steps to re-create:

Observations.

1. Weird thing I noticed is, when the instance is being created the
nova log shows this (Note the VOLUME ID)

2. The create volume (c22d487d-ab7a-4373-b69f-91cd02f32cc8) in
openstack does not match this ID at all.