yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80136
[Bug 1844993] Re: migrate a server with qos port with compute RPC pinned to 5.1 fails and leaves the qos port in an inconsistent state
Reviewed: https://review.opendev.org/683948
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4a10f8eaa7685e3ce03d728a4a1669946492097d
Submitter: Zuul
Branch: master
commit 4a10f8eaa7685e3ce03d728a4a1669946492097d
Author: Balazs Gibizer <balazs.gibizer@xxxxxxxx>
Date: Mon Sep 23 12:48:20 2019 +0200
Reject migration with QoS port from conductor if RPC pinned
The MigrationTask in the conductor already checks the service version as
old computes cannot support migration with QoS port. However it is still
possible that every compute is new but the compute RPC API is pinned to
< 5.2. In this case the migration still cannot be supported.
This patch adds an extra RPC version check to the conductor.
Change-Id: Ib4e0b9ab050a59ab5a290e6eecea01b87c3bd4c6
Closes-Bug: #1844993
** Changed in: nova
Status: In Progress => 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/1844993
Title:
migrate a server with qos port with compute RPC pinned to 5.1 fails
and leaves the qos port in an inconsistent state
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Steps to reproduce
==================
1) Set the [upgrade_levels]/compute config parameter to '5.1'
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
References