Nova VMwareapi Resize of Volume Backed server fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Description
===========
More specifically the following tempest test in master fails:
tempest.
Steps to reproduce
==================
* Install Devstack from master
* Run tempest test `tempest.
Expected result
===============
The test succeeds.
Actual result
=============
What happened instead of the expected result?
How did the issue look like?
Environment
===========
1. Git 1858cf18b940b36
https:/
As instance creation is impossible without that patch.
2. Which hypervisor did you use? What's the version of that?
vmwareapi (VSphere 7.0.3 & ESXi 7.0.3)
2. Which storage type did you use?
vmdk on NFS 4.1
3. Which networking type did you use?
networking-nsx-t (https:/
Logs & Configs
==============
Can be found here: http://
The critical exception for this bug report is (abbreviated and reformatted for clarity):
----
req-7aa5ded6-
[ 865.017199] env[58735]: ERROR nova.compute.
Traceback (most recent call last):
File "/opt/stack/
yield
File "/opt/stack/
disk_info = self.driver.
File "/opt/stack/
return self._vmops.
File "/opt/stack/
self.
File "/opt/stack/
self.
File "/opt/stack/
disk_key = device.key
AttributeError: 'NoneType' object has no attribute 'key'
---
The bug is actually in the function `nova.virt.
https:/
The code works with the assumption, that the root-disk is named as the instance.
This assumption breaks in several cases, but most for this test-case, the root volume is actually a cinder volume.
It will also break when the the disk gets migrated to another datastore, either through a live-migration with no shared storage, or simply automatically with SDRS..
I have an alternative implementation here: https:/
I'll provide a bug fix from it.
Fix proposed to branch: master /review. opendev. org/c/openstack /nova/+ /910627
Review: https:/