Open Stack

It seems this 'AvailabilityZoneFilter' is really buggy. The
'instances' table 'availability_zone' field was already updated to
match the target desired zone name, but 'AvailabilityZoneFilter' kept
rejecting the request. I already restarted nova-api, nova-conductor,
nova-scheduler services after updating this database field value, but
that's not helpful.

In the source code in file
'/usr/lib/python3/dist-packages/nova/scheduler/filters/availability_zone_filter.py',
how does 'spec_obj' got its availability_zone value? I don't
understand this particular code. This issue is really frustrating ..
    def host_passes(self, host_state, spec_obj):
        availability_zone = spec_obj.availability_zone

On Wed, Aug 4, 2021 at 5:11 PM hai wu <haiwu.us at gmail.com> wrote:
>
> Hi,
>
> How to update existing vm instances 'availability_zone' field in nova
> database 'instances' table? It turns out there are many VMs with
> default 'nova' availability zone, while the hypervisors are with
> another different target aggregate/availability zone name, thus live
> migration for these VMs are failing.
>
> The strange thing is that the 'OS-EXT-AZ:availability_zone' output
> from 'openstack server show VM_NAME' is showing these VMs are already
> with the target availibity_zone name. No idea why we have this
> inconsistency.
>
> Would it be ok to just update database table entry directly to set
> 'availility_zone' to different value for these VMs? Or there might be
> better alternatives I am not aware of?
>
> Thanks,
> Hai