** Changed in: nova (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-archive
Status: New => Fix Released
--
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/1890244
Title:
[SRU] nova scheduler should ignore removed groups
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive yoga series:
New
Status in Ubuntu Cloud Archive zed series:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in nova package in Ubuntu:
Fix Released
Status in nova source package in Jammy:
New
Status in nova source package in Kinetic:
Fix Released
Bug description:
[Impact]
Fixes nova to not fail when scheduling a vm that previously belonged to a
server group that has been deleted.
[Test Plan]
* deploy Openstack Yoga with shared storage e.g. Ceph
* create a server group (e.g. affinity) and boot one or more instances within
that group:
openstack server group create --policy affinity sg1
openstack server create --image jammy --flavor m1.small --key-name testkey
--nic net-id=private vm1 --hint group=e29105e1-06a2-40fa-85fa-899db944a82 --wait
* delete the server group:
openstack server group delete sg1
* poweroff the compute host where the vms are running
* evacuate the vms from the powered down host:
nova evacuate vm1 juju-882778-lp1890244-focal-yoga-13.cloud.sts
* check vms are ACTIVE and reachable on new compute host(s)
[Regression Potential]
No regressions are expected as a result of this fix.
-------------------------------------------------------------------------
Description
===========
We created a server group and started some instances in it.
Later we removed the server group.
Some time later, we had to evacuate these instances, but this failed, because
the
scheduler removed all available hosts during filtering.
Steps to reproduce
==================
* create a server group
* start some instances in this group
* delete the server group
* ( hard poweroff your hypervisor )
* evacuate the instances
Expected result
===============
The instances are evacuated
Actual result
=============
The instances run into ERROR-state, because the server group is not found.
Environment
===========
* Kolla deployed OpenStack Train
* Ubuntu 18.04 / KVM + Libvirt
Logs & Configs
==============
scheduler tells:
Filtering removed all hosts for the request with instance ID
'adddf2c9-0252-4463-a97c-f1ec209d9f49'. Filter results:
['AvailabilityZoneFilter: (start: 2, end: 2)', 'ComputeFilter: (start:
2, end: 2)', 'ComputeCapabilitiesFilter: (start: 2, end: 2)',
'ImagePropertiesFilter: (start: 2, end: 2)',
'ServerGroupAntiAffinityFilter: (start: 2, end: 2)',
'ServerGroupAffinityFilter: (start: 2, end: 0)']
instance show:
| fault | {'code': 404, 'created': '2020-08-04T06:13:41Z', 'message':
'Instance group 7e84dc57-de05-4c92-9e3b-6e2d06c1d85b could not be
found.'} |
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1890244/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
