yahoo-eng-team team mailing list archive

[melanie witt <1863190@xxxxxxxxxxxxxxxxxx>]

I've proposed a doc update ^ related to this bug report.

Closing this as Invalid because server group affinity has not been
regressed, as explained in comment 7 and comment 8.

** 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/1863190

Title:
  Server group anti-affinity no longer works

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Server group anti-affinity is no longer working, at least in the
  simple case. I am able to boot two VMs in an anti-affinity server
  group on a devstack that only has one compute instance. Previously
  this would fail and/or require soft-anti-affinity enabled.

  $ openstack host list
  +-----------+-----------+----------+
  | Host Name | Service   | Zone     |
  +-----------+-----------+----------+
  | devstack2 | scheduler | internal |
  | devstack2 | conductor | internal |
  | devstack2 | conductor | internal |
  | devstack2 | compute   | nova     |
  +-----------+-----------+----------+

  $ openstack compute service list
  +----+----------------+-----------+----------+---------+-------+----------------------------+
  | ID | Binary         | Host      | Zone     | Status  | State | Updated At                 |
  +----+----------------+-----------+----------+---------+-------+----------------------------+
  |  3 | nova-scheduler | devstack2 | internal | enabled | up    | 2020-02-14T00:59:15.000000 |
  |  6 | nova-conductor | devstack2 | internal | enabled | up    | 2020-02-14T00:59:16.000000 |
  |  1 | nova-conductor | devstack2 | internal | enabled | up    | 2020-02-14T00:59:19.000000 |
  |  3 | nova-compute   | devstack2 | nova     | enabled | up    | 2020-02-14T00:59:17.000000 |
  +----+----------------+-----------+----------+---------+-------+----------------------------+

  $ openstack server list
  +--------------------------------------+----------------------------------------------+--------+-----------------------------------------------+---------------------+------------+
  | ID                                   | Name                                         | Status | Networks                                      | Image               | Flavor     |
  +--------------------------------------+----------------------------------------------+--------+-----------------------------------------------+---------------------+------------+
  | a44febef-330c-4db5-b220-959cbbff8f8c | amphora-1bc97ddb-80da-446a-bce3-0c867c1fc258 | ACTIVE | lb-mgmt-net=192.168.0.58; public=172.24.4.200 | amphora-x64-haproxy | m1.amphora |
  | de776347-0cf4-47d5-bb37-17fb37d79f2e | amphora-433abe98-fd8e-4e4f-ac11-4f76bbfc7aba | ACTIVE | lb-mgmt-net=192.168.0.199; public=172.24.4.11 | amphora-x64-haproxy | m1.amphora |
  +--------------------------------------+----------------------------------------------+--------+-----------------------------------------------+---------------------+------------+

  $ openstack server group show ddbc8544-c664-4da4-8fd8-32f6bd01e960
  +----------+----------------------------------------------------------------------------+
  | Field    | Value                                                                      |
  +----------+----------------------------------------------------------------------------+
  | id       | ddbc8544-c664-4da4-8fd8-32f6bd01e960                                       |
  | members  | a44febef-330c-4db5-b220-959cbbff8f8c, de776347-0cf4-47d5-bb37-17fb37d79f2e |
  | name     | octavia-lb-cc40d031-6ce9-475f-81b4-0a6096178834                            |
  | policies | anti-affinity                                                              |
  +----------+----------------------------------------------------------------------------+

  Steps to reproduce:
  1. Boot a devstack.
  2. Create an anti-affinity server group.
  2. Boot two VMs in that server group.

  Expected Behavior:

  The second VM boot should fail with an error similar to "not enough
  hosts"

  Actual Behavior:

  The second VM boots with no error, The two instances in the server
  group are on the same host.

  Environment:
  Nova version (current Ussuri): 0d3aeb0287a0619695c9b9e17c2dec49099876a5
  commit 0d3aeb0287a0619695c9b9e17c2dec49099876a5 (HEAD -> master, origin/master, origin/HEAD)
  Merge: 1fcd74730d 65825ebfbd
  Author: Zuul <zuul@xxxxxxxxxxxxxxxxxx>
  Date:   Thu Feb 13 14:25:10 2020 +0000

      Merge "Make RBD imagebackend flatten method idempotent"

  Fresh devstack install, however I have another devstack from August
  that is also showing this behavior.

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