Public bug reported:
Description
===
Boot instance with metadata will remain some images in
'/var/tmp/.guestfs-0/appliance.d' when this compute_node config
CONF.libvirt.inject_partition=-1.
Steps to reproduce
==
1) Config inject_partition=-1(/etc/nova/nova.conf) in compu
Public bug reported:
Description
===
In compute node, the periodic task to clean up expired console_auth tokens is
invalid, can't remove expired console auth tokens for this host.
Steps to reproduce
==
1.In controller node, config nova-novncproxy using database to store n
Public bug reported:
Description
===
Create an instance in anti-affinity group, then migrate this instance from one
host to another success, but migrate back failed.
Steps to reproduce
==
1. create anti-affinity group
+--+--
** 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/1804356
Title:
Delete instance while resize instance to other compute no
Public bug reported:
Description
===
Configure nova configuration item 'cross_az_attch' on 'false'. Using a volume
with availability_zone property to create instance failed when all compute
nodes are in same availability_zone.
Steps to reproduce
==
1.Configure 'cross_az_
Public bug reported:
Description
===
Delete instance while instance resize to other compute_nodes. If the deletion
action starts before instance's vm_state is "resized", source compute_node or
dest compute_node will remain "_resize" directory.
Steps to reproduce
==
1) Cr
Public bug reported:
Description
===
When instance live-migration to another host, the vnc connection will
disconnect and can not continue to use.
Steps to reproduce
==
1.build a vm
nova boot --flavor 777 --image 80c83482-1c69-4cf6-b7ac-c2848e001a3e --nic
net-id=4daeddbd
Public bug reported:
Description
===
If add some host to an availability_zone continuously, nova_scheduler's
aggs_by_id and host_aggregates_map may be lost some host aggregate data. Then
create instance in this availability_zone will not select those lost host every
time.
Steps to repr
Public bug reported:
Description
===
When the instance evacuated to destination host successfully, then deleted this
instance. The source host up will cleanup this instance failed.
Steps to reproduce
==
1.deploy a local instance in source host.
2.power off the source host
9 matches
Mail list logo