Doesn't download image from _base folder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hello.
Recently I encountered with strange behavior of nova while upgrading instance to a new flavor.
I did:
1. I created an instance from a previously made snapshot.
2. After the instance has been successfully created, I deleted the snapshot from image storage.
3. Created a new flavor with a bigger of disk space for the instance.
4. I made resize the instance using a new flavor, with case when there are not enough resources on the src compute node and the instance started migrating to another compute node where there are enough resources.
5. Once the instance disk has been completely copied to the new compute and the instance status has changed to VERITY_RESZIE, the instance disk (block device) remains the same size as in the old flavor. After confirming the upgrade, the disk remains the same size.
In the logs I don't see any errors only a message like https:/
I made the following edits in the code:
/usr/lib/
@@ -7676,13 +7676,13 @@
- def copy_from_
+ def copy_from_
- filename=filename)
+ filename=filename, image_id=image_id)
And after that, everything worked as expected. The instance successfully migrated to dst compute during the upgrade, the disk grew according to the new flavor.
But then I ran into one more issue, when the instance goes into the VERIFY_RESIZE status in the database already indicated that it is running on a different compute node and the image on the scr compute can be deleted due to remove_
I made the following edits in the code:
+++ /usr/lib/
@@ -7932,7 +7932,21 @@
+ filters_
+ 'source_compute': nodes,
+ 'migration_type': 'resize'}
+ migration_
+ if migration_
+ uuids = []
+ for migration_instance in migration_
+ uuids.append(
+ filters_by_instance = {'uuid': uuids}
+ filtered_
+ filtered_instances = filtered_instances + filtered_
Thus, we will not delete the images of instances that are still in the VERIFY_RESIZE status.
I would like to clarify if this is the basic behavior of nova or is it still a bug? Perhaps someone else has encountered similar problems.
Environment
OS - Ubuntu 16.04
Linux compute1 4.15.0-122-generic #124~16.04.1-Ubuntu SMP Thu Oct 15 16:08:36 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
OpenStack release - Queens
hypervisor - Libvirt + KVM
dpkg -l | grep nova
ii nova-common 2:17.0.
ii nova-compute 2:17.0.
ii nova-compute-kvm 2:17.0.
ii nova-compute-
ii python-nova 2:17.0.
ii python-nova-helper 1.3+0~201909161
ii python-novaclient 2:9.1.1-
This bug has been open for quite a long time without activities. So I really apologize if you cannot have the support required.
However, the bug was on older version, which is out of support now.
I propose closing this bug unless you still have it, and you can reproduce it on a supported release. Please provide the new info and set this bug back to new.