yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #68825
[Bug 1727260] [NEW] Nova assumes that a volume is fully detached from the compute if the volume is not defined in the instance's libvirt definition
Public bug reported:
During a volume detach operation, Nova compute attempts to remove the
volume from libvirt for the instance before proceeding to remove the
storage lun from the underlying compute host. If Nova discovers that the
volume was not found in the instance's libvirt definition then it
ignores that error condition and returns (after issuing a warning
message "Ignoring DiskNotFound exception while detaching").
However, under certain failure scenarios it may be that although the
libvirt definition for the volume has been removed for the instance that
the associated storage lun on the compute server may not have been fully
cleaned up yet.
** Affects: nova
Importance: Undecided
Assignee: sahid (sahid-ferdjaoui)
Status: New
** Tags: libvirt ocata-backport-potential
** Changed in: nova
Assignee: (unassigned) => sahid (sahid-ferdjaoui)
--
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/1727260
Title:
Nova assumes that a volume is fully detached from the compute if the
volume is not defined in the instance's libvirt definition
Status in OpenStack Compute (nova):
New
Bug description:
During a volume detach operation, Nova compute attempts to remove the
volume from libvirt for the instance before proceeding to remove the
storage lun from the underlying compute host. If Nova discovers that
the volume was not found in the instance's libvirt definition then it
ignores that error condition and returns (after issuing a warning
message "Ignoring DiskNotFound exception while detaching").
However, under certain failure scenarios it may be that although the
libvirt definition for the volume has been removed for the instance
that the associated storage lun on the compute server may not have
been fully cleaned up yet.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1727260/+subscriptions
Follow ups