[Yahoo-eng-team] [Bug 1939856] Re: delete vm after shelve vm

Hi gibizer, I have set reclaim_instance_interval = 604800 in nova.conf. So when we call nova `delete` command to delete vm, in fact it means to soft delete the vm. And we can call `force-delete` to delete vm at last. ** Changed in: nova Status: Invalid => New -- You received this bug noti

[Yahoo-eng-team] [Bug 1939856] [NEW] delete vm after shelve vm

Public bug reported: Description === I delete vm after I have done shelve action for vm. Notes: I set reclaim_instance_interval = 604800 in nova.conf Steps to reproduce == It's very important to set reclaim_instance_interval = 604800 in nova.conf Then do steps as followe

[Yahoo-eng-team] [Bug 1823825] [NEW] Evacuation still doesn't respect anti-affinity rules after adding late group check

Public bug reported: Description === When we evacuate multi servers simultaneously, it will break the anti-affinity rules of group. Environment === Prepare three nodes and deploy the multi nodes cluster with kolla-ansible. Steps to reproduce == 1. we have 3 compu

[Yahoo-eng-team] [Bug 1821755] Re: live migration break the anti-affinity policy of server group simultaneously

** This bug is no longer a duplicate of bug 1526642 Simultaneous live migrations break anti-affinity policy -- 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/1821755 Title

[Yahoo-eng-team] [Bug 1821755] [NEW] live migration break the anti-affinity policy of server group simultaneously

Public bug reported: Description === If we live migrate two instance simultaneously, the instances will break the instance group policy. Steps to reproduce == OpenStack env with three compute nodes(node1, node2 and node3). Then we create two VMs(vm1, vm2) with the anti-a

[Yahoo-eng-team] [Bug 1820018] [NEW] instance breaks the affinity/anti-affinity of server group with force_hosts or force_nodes

Public bug reported: Description === Boot a server with server-group(affinity/anti-affinity) and force_host. The second instance broken the affinity/anti-affinity. Steps to reproduce == We create a server-group(with anti-affinity policy). The we begin to test, as follo

[Yahoo-eng-team] [Bug 1816686] [NEW] fail to boot an instance because of "rbd import" qcow2 disk

Public bug reported: Environment === OpenStack: master branch Ceph: luminous Steps to reproduce == 1. Upload a qcow2 format image to glance such as a test qcow2 image `cirros`. 2. Use command to create a new instance: `openstack server create --image --flavor --securit

[Yahoo-eng-team] [Bug 1783467] [NEW] fail to create volume type encryption

02-7a50-4336-b19c-9b48671c183b/encryption returned with HTTP 400 But I can create the volume type encryption by the CLI command 'cinder encryption-type-create '. ** Affects: horizon Importance: Undecided Assignee: Boxiang Zhu (bxzhu-5355) Status: In Progress ** At