setting status to invalid since I am not seeing the problem anymore. The
review that was associated with this bug
(https://review.openstack.org/#/c/389798/) is now associated with bug
1673090.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification
Public bug reported:
Using either the cli or API, if you attempt to swap disks (nova volume-
update, compute.api.swap_volume) on a stopped instance, the command
appears to succeed, but the swap is not performed. The way you can tell
what didn't happen is that the volume status's of the 2 volumes
Public bug reported:
This was found while testing live migration with the new cinder v3 api
using a bfv instance.
In compute.manager._validate_bdm(...) is this:
...
if (min_compute_version >=
BFV_RESERVE_MIN_COMPUTE_VERSION):
volume = self._check_attach_and_reserve_volume(
** Changed in: nova
Status: New => 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/1697537
Title:
cinder v3 api, validate_bdm calling
Public bug reported:
I hit an extra exception during a failed live migration rollback. This
exception occurred on the destination node. This bug is not about the
reason for the failed migration, but for the failure in the rollback.
The exception:
Traceback (most recent call last):
File
Public bug reported:
While testing live migration, I hit an exception during libvirt.driver
rollback_live_migration_at_destination. The first step is this:
self.destroy(context, instance, network_info, block_device_info,
destroy_disks, migrate_data)
But there is no arg
Public bug reported:
There is a known problem using certain versions of qemu and libvirt with
multiattach. Nova will not let you attach a multiattach enabled volume
if the version of libvirt is <= 3.10 or qemu >= 2.10. This bug is only
about the user error message that is displayed when you hit
Public bug reported:
With multiattach now enabled, it should be possible to use the Create
Multiple Servers compute api to create multiple instances with a common
multiattach disk attached to all of them (assuming you have met all the
prerequisites for multiattach to work).
Currently when you
8 matches
Mail list logo
