yahoo-eng-team team mailing list archive

[Balazs Gibizer <balazs.gibizer@xxxxxxxx>]

Public bug reported:

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

1) Set the [upgrade_levels]/compute config parameter to '5.0'
2) Boot an instance with a neutron port having resource request (e.g. QoS min bandwidth policy)
4) Do the migration

Expected result
===============

Migration is rejected as qos port handing in migration needs at least
RPC 5.2. Instance remains on the source host.

Actual result
=============

Migration fails at finish_resize step. Server goes to ERROR state on the
destination host. The allocation key in the qos port binding profile
still points to the source host.

** Affects: nova
     Importance: Undecided
     Assignee: Balazs Gibizer (balazs-gibizer)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

-- 
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/1844993

Title:
  migrate a server with qos port with compute RPC pinned to 5.0 fails
  and leaves the qos port in an inconsistent state

Status in OpenStack Compute (nova):
  New

Bug description:
  Steps to reproduce
  ==================

  1) Set the [upgrade_levels]/compute config parameter to '5.0'
  2) Boot an instance with a neutron port having resource request (e.g. QoS min bandwidth policy)
  4) Do the migration

  Expected result
  ===============

  Migration is rejected as qos port handing in migration needs at least
  RPC 5.2. Instance remains on the source host.

  Actual result
  =============

  Migration fails at finish_resize step. Server goes to ERROR state on
  the destination host. The allocation key in the qos port binding
  profile still points to the source host.

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