Public bug reported: When we get a request to migrate a server that has minimum bandwidth resource requests, we check whether the service on the target host is new enough to support resource requests. However, we are not targeting the target host's cell database when we do the lookup. This works OK when the migration is occuring within the same cell, but if the target host is in another cell, we will fail to lookup the service record in the source cell with the following error [1]:
Failed to compute_task_migrate_server: 'NoneType' object has no attribute 'version' This is because when Service.get_by_host_and_binary fails to find a matching record, it returns (and thus returns None). This failure has recently emerged in the nova-multi-cell gate job because tempest tests were recently added for minimum bandwidth resource requests in change: https://review.opendev.org/c/openstack/tempest/+/694539 and these tests include migration tests. To fix this, we just need to target the cell database for the target host's service record when we lookup the service. This change is stable-only because the service version check was recently removed in change: https://review.opendev.org/c/openstack/nova/+/735570 and only exists in stable branches. [1] https://zuul.opendev.org/t/openstack/build/2ee6a4a30c8f403b911386a6cd80fc51/log/controller/logs/screen-n -super-cond.txt#3778 ** Affects: nova Importance: Undecided Status: Invalid ** Affects: nova/ussuri Importance: Undecided Status: New ** Affects: nova/victoria Importance: Undecided Assignee: melanie witt (melwitt) Status: In Progress ** Tags: cells conductor gate-failure ** Tags added: gate-failure ** Also affects: nova/ussuri Importance: Undecided Status: New ** Also affects: nova/victoria Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1907511 Title: nova-multi-cell fails on stable branches with: Failed to compute_task_migrate_server: 'NoneType' object has no attribute 'version' Status in OpenStack Compute (nova): Invalid Status in OpenStack Compute (nova) ussuri series: New Status in OpenStack Compute (nova) victoria series: In Progress Bug description: When we get a request to migrate a server that has minimum bandwidth resource requests, we check whether the service on the target host is new enough to support resource requests. However, we are not targeting the target host's cell database when we do the lookup. This works OK when the migration is occuring within the same cell, but if the target host is in another cell, we will fail to lookup the service record in the source cell with the following error [1]: Failed to compute_task_migrate_server: 'NoneType' object has no attribute 'version' This is because when Service.get_by_host_and_binary fails to find a matching record, it returns (and thus returns None). This failure has recently emerged in the nova-multi-cell gate job because tempest tests were recently added for minimum bandwidth resource requests in change: https://review.opendev.org/c/openstack/tempest/+/694539 and these tests include migration tests. To fix this, we just need to target the cell database for the target host's service record when we lookup the service. This change is stable-only because the service version check was recently removed in change: https://review.opendev.org/c/openstack/nova/+/735570 and only exists in stable branches. [1] https://zuul.opendev.org/t/openstack/build/2ee6a4a30c8f403b911386a6cd80fc51/log/controller/logs/screen-n -super-cond.txt#3778 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1907511/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
