non-zero disk size
4. Rescue the instance
5. Unrescue the instance
6. Observe the rescue image left in nova-lvm/.rescue
** Affects: nova
Importance: Undecided
Assignee: Dan Genin (daniel-genin)
Status: New
** Tags: leak lvm unrescue
--
You received this bug notification be
Public bug reported:
LVM ephemeral storage backend is broken in the most recent Nova (commit
945646e1298a53be6ae284766f5023d754dfe57d)
To reproduce in Devstack:
1. Configure Nova to use LVM ephemeral storage by adding to
create_nova_conf function in lib/nova
iniset $NOVA_CONF libvirt im
Rafi,
I don't think this is a bug but rather a missing feature, so I am going
to mark this as "Invalid". If you want to implement this, you should
file it under "Wishlist" and submit a blueprint to Nova
https://wiki.openstack.org/wiki/Blueprints. The blueprint is important
so that implementation d
This appears to be a duplicate of
https://bugs.launchpad.net/nova/+bug/1094134, which was fixed in
commit 02ea0f9f9e5c7f022b465a96ba3a4f089c633bee
Merge: cd2008c 9d3f524
Author: Jenkins
Date: Fri Jan 11 23:35:10 2013 +
Merge "Correct the calculating of disk size when using lvm disk
backend."
This has been fixed in
commit 02ea0f9f9e5c7f022b465a96ba3a4f089c633bee
Merge: cd2008c 9d3f524
Author: Jenkins
Date: Fri Jan 11 23:35:10 2013 +
Merge "Correct the calculating of disk size when using lvm disk
backend."
** Changed in: nova
Status: Confirmed => Fix Released
--
You
Public bug reported:
Attempting to boot an LVM backed instance that exceeds available disk
space results in ProcessExecutionError exception leading to an ERROR
state instead of clean termination.
Observed in Nova 209c0a29 on DevStack b160640d. To generate the failure
configure Nova for LVM epheme
** Changed in: nova
Status: Invalid => 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/1270305
Title:
LVM backed instance migration does not copy disk
Status
Migrating instances that have no root disk indeed does not copy data to
the target host. This, however, is probably the expected behavior.
Instances with a non-zero size root disk migrate as expected.
My apologies for not catching this before.
** Changed in: nova
Status: New => Invalid
--
Public bug reported:
When an LVM backed instance is migrated (in Devstack) the instance's
disk is not copied to the destination compute node and the is not
deleted from the source compute node.
Observed with nova 3912d7aae21dfff5a42dd71bd45ef5c5f3b1a82b and devstack
78411958fd086acc0270c2380dd61f
9 matches
Mail list logo