yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #11443
[Bug 1030108] Re: xenapi: bad handling of "volume in use" errors
This now raises:
Reached maximum number of retries trying to unplug VBD OpaqueRef:50be57f5-7c5a-0e72-7659-38b37608ea2a
Instance goes into the error state.
If the user calls reboot, everything will return to normal.
** Changed in: nova
Status: Triaged => Invalid
--
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/1030108
Title:
xenapi: bad handling of "volume in use" errors
Status in OpenStack Compute (Nova):
Invalid
Bug description:
We have noticed several circumstances (like for example if a volume is
in a raid, or in use) and detach call is issued, the volume stays in
the in-use state, and Xen holds on to that volume. When the volume
becomes not in use any longer (for example if you remove it from the
raid, unmount it), Xen will then still have the detach command queued,
and detach the device. This may lead to confusing behavior for the
user. If a detach fails because it is in use, it should remove the
queued detach command from the instance so that it isn't detached when
not in use any more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1030108/+subscriptions