yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

This is arguably working as designed, see the ML discussion:

http://lists.openstack.org/pipermail/openstack-
discuss/2019-March/003813.html

I have added this as a topic for discussion at the Train release PTG:

https://etherpad.openstack.org/p/nova-ptg-train

** Changed in: nova
       Status: New => Opinion

** Tags added: api scheduler server-groups

-- 
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/1820018

Title:
  instance breaks the affinity/anti-affinity of server group with
  force_hosts or force_nodes

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  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 followed:
  1. Create the first instance with the server-group
  2. Create the second instance with the server-group and with force_host(the host of first instance)

  Command:
  1. nova boot <instance-name> --flavor <flavor> --image <image> --availability-zone <az> --security-groups <sec-group> --nic net-id=<net-id> --hint group=<server-group>
  2. nova boot <instance-name> --flavor <flavor> --image <image> --availability-zone <az>:<host> --security-groups <sec-group> --nic net-id=<net-id> --hint group=<server-group>

  
  Expected result
  ===============
  ?? Did we expect that the second instance fails to boot.

  
  Actual result
  =============
  The second instance succeeds to boot.

  
  Environment
  ===========
  1. The openstack version is master. And setup the env by devstack tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1820018/+subscriptions