Public bug reported:
When I try to live migrate an instance that uses the serial console, the
migration fails due to a libvirt error.
I do not have a solution for this problem yet, please let me know if
anyone else hits this or if it might be a configuration problem.
Command I ran:
# nova live-
Public bug reported:
When adding or removing CPUs to a compute node running the libvirt
driver, the correct new amount of CPUs is not reported to the
controller/scheduler.
As a result, the scheduler will not consider added or removed capacity
in future scheduling decisions.
To fix this, the numb
** Changed in: anvil
Assignee: (unassigned) => Alexander Schmidt (alexs-h)
** Changed in: anvil
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to anvil.
https://bugs.launchp
Public bug reported:
The resize_fs_using_block_device config option allows to configure if a
filesystem within an image is resized by nova during spawn or not. When
it's set to False (which is the default) nova still tries to access the
image to find out if it's extendable or not, although it's no
Public bug reported:
nova-baremetal-* tools were removed from nova during kilo development,
see
http://git.openstack.org/cgit/openstack/nova/commit/?id=46ed619b9ab1d61582f36155eea0d4a88f31fd50
Due to this change the anvil build step fails.
I'll send a patch to address this in the nova spec temp
Public bug reported:
When a host system has CPUs that are offlined via CPU hotplug, nova
fails to start an instance on the host. On a test system, I've offlined
CPU 31 on an Intel blade server by running the following command:
sudo echo 0 > /sys/devices/system/cpu/cpu31/online
When starting an i
6 matches
Mail list logo
