[Bug 1890244] Re: nova scheduler should ignore removed groups

OpenStack Infra 1890244 at bugs.launchpad.net
Thu Mar 2 20:41:48 UTC 2023


Reviewed:  https://review.opendev.org/c/openstack/nova/+/872663
Committed: https://opendev.org/openstack/nova/commit/f57900ad20d21aac5cb91aed87edc121f9008115
Submitter: "Zuul (22348)"
Branch:    stable/yoga

commit f57900ad20d21aac5cb91aed87edc121f9008115
Author: Sean Mooney <work at seanmooney.info>
Date:   Tue Jun 21 12:04:20 2022 +0100

    add repoducer test for bug 1890244
    
    This change adds a test to simulate validating
    a instnace group policy where the group has been
    deleted but is still referenced in the scheduler hint.
    
    Change-Id: I803e6286a773d9e53639ab0cd449fc72bb3be613
    Related-Bug: #1890244
    (cherry picked from commit 84a84f7f2fff58cf6254d6267af0ca5cee64c53b)


** Tags added: in-stable-yoga

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1890244

Title:
  nova scheduler should ignore removed groups

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in Ubuntu Cloud Archive victoria series:
  New
Status in Ubuntu Cloud Archive wallaby series:
  New
Status in Ubuntu Cloud Archive xena series:
  New
Status in Ubuntu Cloud Archive yoga series:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  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




More information about the Ubuntu-openstack-bugs mailing list