yahoo-eng-team team mailing list archive

[Edward Hope-Morley <1890244@xxxxxxxxxxxxxxxxxx>]

** Changed in: cloud-archive/yoga
       Status: Fix Committed => New

** Also affects: nova (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: nova (Ubuntu Lunar)
   Importance: Undecided
       Status: New

** Also affects: nova (Ubuntu Kinetic)
   Importance: Undecided
       Status: New

** Also affects: nova (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** No longer affects: nova (Ubuntu Lunar)

** Changed in: nova (Ubuntu Kinetic)
       Status: New => Fix Released

** Also affects: cloud-archive/zed
   Importance: Undecided
       Status: New

** Changed in: cloud-archive/zed
       Status: New => Fix Released

** No longer affects: cloud-archive/ussuri

** No longer affects: cloud-archive/victoria

** No longer affects: cloud-archive/wallaby

** No longer affects: cloud-archive/xena

-- 
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:
  nova scheduler should ignore removed groups

Status in Ubuntu Cloud Archive:
  New
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:
  New
Status in nova source package in Jammy:
  New
Status in nova source package in Kinetic:
  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