yahoo-eng-team team mailing list archive

[Uggla <1978573@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
Unshelving a shelved offloaded server will go through the
scheduler to pick a new host, so we update the
RequestSpec.availability_zone here. Note that if scheduling
fails the RequestSpec will remain updated, which is not great.

https://review.opendev.org/c/openstack/nova/+/831507/comment/12fd28cd_42160512/


Steps to reproduce
==================
NA


Expected result
===============
If schedule fails, restore the original az.


Actual result
=============
RequestSpec inconsistent if schedule fails.


Environment
===========
This was introduced in Train (Aug 28, 2019) with the following note:
If we want to change that we need to defer updating the
RequestSpec until conductor which probably means RPC changes to
pass the new_az variable to conductor. This is likely low
priority since the RequestSpec.availability_zone on a shelved
offloaded server does not mean much anyway and clearly the user
is trying to put the server in the target AZ.


Logs & Configs
==============
NA

** Affects: nova
     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/1978573

Title:
  Unshelve with az update the requestSpec.availability_zone this can be
  inconsistent  if schedule fails

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Unshelving a shelved offloaded server will go through the
  scheduler to pick a new host, so we update the
  RequestSpec.availability_zone here. Note that if scheduling
  fails the RequestSpec will remain updated, which is not great.

  https://review.opendev.org/c/openstack/nova/+/831507/comment/12fd28cd_42160512/

  
  Steps to reproduce
  ==================
  NA

  
  Expected result
  ===============
  If schedule fails, restore the original az.

  
  Actual result
  =============
  RequestSpec inconsistent if schedule fails.

  
  Environment
  ===========
  This was introduced in Train (Aug 28, 2019) with the following note:
  If we want to change that we need to defer updating the
  RequestSpec until conductor which probably means RPC changes to
  pass the new_az variable to conductor. This is likely low
  priority since the RequestSpec.availability_zone on a shelved
  offloaded server does not mean much anyway and clearly the user
  is trying to put the server in the target AZ.

  
  Logs & Configs
  ==============
  NA

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1978573/+subscriptions