resize or migrate problem
hello I use OpenStack and I create some VMs in different compute in one region. when I resize the VM. if the compute doesn't have enough space, automatically the vm will be migrated to another compute. but my problem is here that when it migrated, the _base file doesn't migrate and remains in the first compute that it doesn't have enough space. because of this, the VM appears with an error status in OpenStack. if I move the _base from first compute to final compute and reboot the server this problem has been solved. so i need to not transfer _base manually and if it migrated to another compute the disk and _base transfer with each other. could you please help me to solve this problem? thanks in advance
On Tue, 2022-08-02 at 12:33 +0430, fereshteh loghmani wrote:
hello I use OpenStack and I create some VMs in different compute in one region. when I resize the VM. if the compute doesn't have enough space, automatically the vm will be migrated to another compute. but my problem is here that when it migrated, the _base file doesn't migrate and remains in the first compute that it doesn't have enough space. because of this, the VM appears with an error status in OpenStack. if I move the _base from first compute to final compute and reboot the server this problem has been solved. so i need to not transfer _base manually and if it migrated to another compute the disk and _base transfer with each other. could you please help me to solve this problem?
the _base file shoudl be automatically copied when requried. has the image been deleted in glance? what release of openstack are you using and what storage backend are you using for nova and glance. can i assume nova is useing the defaul qcow2 backend?
thanks in advance
hello thank you for your response. about your questions: has the image been deleted in glance? - yes my image has been deleted in glance what release of openstack are you using and what storage backend are you using? - openstack_release: "victoria" -i don't use ceph and I use dedicated storage. and the backing file format: raw On Tue, Aug 2, 2022 at 2:37 PM Sean Mooney <smooney@redhat.com> wrote:
On Tue, 2022-08-02 at 12:33 +0430, fereshteh loghmani wrote:
hello I use OpenStack and I create some VMs in different compute in one region. when I resize the VM. if the compute doesn't have enough space, automatically the vm will be migrated to another compute. but my problem is here that when it migrated, the _base file doesn't migrate and remains in the first compute that it doesn't have enough space. because of this, the VM appears with an error status in OpenStack. if I move the _base from first compute to final compute and reboot the server this problem has been solved. so i need to not transfer _base manually and if it migrated to another compute the disk and _base transfer with each other. could you please help me to solve this problem?
the _base file shoudl be automatically copied when requried. has the image been deleted in glance? what release of openstack are you using and what storage backend are you using for nova and glance. can i assume nova is useing the defaul qcow2 backend?
thanks in advance
On Wed, Aug 3, 2022 at 10:49 AM fereshteh loghmani <fereshtehloghmani@gmail.com> wrote:
hello thank you for your response. about your questions: has the image been deleted in glance? - yes my image has been deleted in glance
ack that is what i tought might be the case.
what release of openstack are you using and what storage backend are you using? - openstack_release: "victoria" -i don't use ceph and I use dedicated storage. and the backing file format: raw ok so there was a know issue where if the image was deleted and the backing file was not present on the source or could not be copied for some reasons that you would encounter the behaivor you observed.
normally if the backing file is not accessible on the source node it will be downloaded form glance on the dest. which does not work in the case where the file is deleted. there was a bug directly relate to this which ii believe is fixed but im not sure if its fixed on victoria. i cant find the bug on launchpad quickly but i think if we look at gerrit or the nova code that perhaps lee yarwood fixed it 12-24 months ago. i might be miss remembering but i know there was an edge case for delete images with evacuate and i think it also affect cold migrate.
On Tue, Aug 2, 2022 at 2:37 PM Sean Mooney <smooney@redhat.com> wrote:
On Tue, 2022-08-02 at 12:33 +0430, fereshteh loghmani wrote:
hello I use OpenStack and I create some VMs in different compute in one region. when I resize the VM. if the compute doesn't have enough space, automatically the vm will be migrated to another compute. but my problem is here that when it migrated, the _base file doesn't migrate and remains in the first compute that it doesn't have enough space. because of this, the VM appears with an error status in OpenStack. if I move the _base from first compute to final compute and reboot the server this problem has been solved. so i need to not transfer _base manually and if it migrated to another compute the disk and _base transfer with each other. could you please help me to solve this problem?
the _base file shoudl be automatically copied when requried. has the image been deleted in glance? what release of openstack are you using and what storage backend are you using for nova and glance. can i assume nova is useing the defaul qcow2 backend?
thanks in advance
participants (2)
-
fereshteh loghmani
-
Sean Mooney