Comment 8 for bug 1378904

Sayali Lunkad (sayalilunkad) wrote :

CONFIRMED FOR NEWTON. After renaming the availability zone which has some instances running in it manual changes to the nova database need to be made in order to update the availability_zone. After that if live migration is carried out without specifying a host or anything which requires the AvailabilityZoneFilter returns no host found and this error message in the nova-scheduler.log
 INFO nova.filters [req-f0377310-f38a-47d8-a01b-65d90d79f202 7682adbc49f741ae8555915f95776a7b 07d042659b65465794e46ceafb1a1397 - - -] Filter AvailabilityZoneFilter returned 0 hosts
2017-08-24 10:04:17.687 20388 INFO nova.filters [req-f0377310-f38a-47d8-a01b-65d90d79f202 7682adbc49f741ae8555915f95776a7b 07d042659b65465794e46ceafb1a1397 - - -] Filtering removed all hosts for the request with
 instance ID 'd08b2dd4-039b-4de0-98f4-28c00c0c8cee'. Filter results: ['RetryFilter: (start: 2, end: 2)', 'AvailabilityZoneFilter: (start: 2, end: 0)']

Adding some addition info to the log point to this:
Availability Zone 'texas' requested. (d52-54-77-77-01-04, d52-54-77-77-01-04.c14.cloud.suse.de) ram: 1991MB disk: 14336MB io_ops: 0 instances: 0 has AZs: set([u'austin'])
for all the available hosts.