Public bug reported:
When a compute host is unreachable, a port detach for a VM on that host
will not complete until the host is reachable again. In some cases, this
may for an extended period or even indefinitely (for example, a host is
powered down for hardware maintenance, and possibly needs to be removed
from the fleet entirely). This is problematic for multiple reasons:
1) The port should not be deleted in this state (it can be, but for reasons
outside the scope of this bug, that is not recommended). Thus, the quota cannot
be reclaimed by the project.
2) The port cannot be reassigned to another VM. This means that for projects
that rely heavily on maintaining a published IP (or possibly even a published
port ID), there is no way to proceed. For example, if Octavia wanted to allow
failing over from one VM to another in a VM down event (as would happen if the
host was powered off) without using AAP, it would be unable to do so, leading
to an extended downtime.
Nova will supposedly clean up such resources after the host has been
powered up, but that could take hours or possibly never happen. So,
there should be a way to force the port to detach regardless of ability
to reach the compute host, and simply allow the cleanup to happen on
that host in the future (if possible) but immediately release the port
for delete or rebinding.
** Affects: nova
Importance: Undecided
Status: New
** Affects: octavia
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/1827746
Title:
Port detach fails when compute host is unreachable
Status in OpenStack Compute (nova):
New
Status in octavia:
New
Bug description:
When a compute host is unreachable, a port detach for a VM on that
host will not complete until the host is reachable again. In some
cases, this may for an extended period or even indefinitely (for
example, a host is powered down for hardware maintenance, and possibly
needs to be removed from the fleet entirely). This is problematic for
multiple reasons:
1) The port should not be deleted in this state (it can be, but for reasons
outside the scope of this bug, that is not recommended). Thus, the quota cannot
be reclaimed by the project.
2) The port cannot be reassigned to another VM. This means that for projects
that rely heavily on maintaining a published IP (or possibly even a published
port ID), there is no way to proceed. For example, if Octavia wanted to allow
failing over from one VM to another in a VM down event (as would happen if the
host was powered off) without using AAP, it would be unable to do so, leading
to an extended downtime.
Nova will supposedly clean up such resources after the host has been
powered up, but that could take hours or possibly never happen. So,
there should be a way to force the port to detach regardless of
ability to reach the compute host, and simply allow the cleanup to
happen on that host in the future (if possible) but immediately
release the port for delete or rebinding.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1827746/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
