Public bug reported:
Steps to reproduce
===
1, launch a boot from volume instance named bfv1
2, attach a volume (blank-volume1) to instance bfv1
3, take a snapshot on bfv1 and a new image bfv1-snap1 created
4, launch another boot from image instance named bfi1
4, rebuild bfi1 from
Public bug reported:
Description
I did some test on boot from volume instance. I found that sometime the
instance boot from volume will fail on evacuate operation. After some
dig, I found evacuate operation failed due to the conductor service
returned wrong block device mapping which
Public bug reported:
I tested instance deferred delete function. I found that when a instance
is SOFT_DELETED, I can detach volume from that instance. However I can't
detach interface from a SOFT_DELETED instance. I think we should also
allow interface detach operation when a instance is SOFT_DELE
** Changed in: neutron
Status: Incomplete => Fix Released
** Changed in: neutron
Assignee: Jiajun Liu (ljjjustin) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchp
Public bug reported:
we don't pass migrate_data to live migration recover method, so if live
migration failed, instance's image will be deleted in cleanup action if
the instance is using shared block device like ceph rbd.
** Affects: nova
Importance: Undecided
Assignee:
I can reproduce this bug with nova+cinder+sheepdog.
** Changed in: nova
Status: Invalid => Confirmed
--
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/1211224
Title:
I tested with the latest havana release. It works fine. I looked at the
source code and I found that those check code have been removed. So we
should change the status to 'fix released'.
** Changed in: nova
Status: Triaged => Fix Released
--
You received this bug notification because you
** Changed in: nova
Assignee: Jiajun Liu (ljjjustin) => (unassigned)
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
when we ping VM from hypervisor, the hypervisor will use the shared dhcp
address as source ip address. however, the ebtables rule added in
https://review.openstack.org/#/c/16578/ will drop those packets who's
source ip address is shared dhcp address. so we can not ping VM from
hypervisor. We need
9 matches
Mail list logo