yahoo-eng-team team mailing list archive

[D G Lee <1699054@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Test steps:

1. There are multiple nova-scheduler services.
2. The value of default_availability_zone is 'nova'.
3. Create an aggregate and its availability_zone is 'az-test'.
4. Add all hosts to the new aggregate.

In step 4, the nova api will send asynchronous RPC message to all nova
schedulers to update aggregate information in memory. Because of
rabbitmq fails，some nova scheduler can't consume the message from nova
api, so the data is not consistent in memory and database. create the
instance with 'az-test' availability zone will fail because without 'az-
test' availability_zone in nova scheduler.

There is no way to know that host_aggregates_map is inconsistent with
the database.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  nova-scheduler is not consistent in host_aggregates_map and database

Status in OpenStack Compute (nova):
  New

Bug description:
  Test steps:

  1. There are multiple nova-scheduler services.
  2. The value of default_availability_zone is 'nova'.
  3. Create an aggregate and its availability_zone is 'az-test'.
  4. Add all hosts to the new aggregate.

  In step 4, the nova api will send asynchronous RPC message to all nova
  schedulers to update aggregate information in memory. Because of
  rabbitmq fails，some nova scheduler can't consume the message from nova
  api, so the data is not consistent in memory and database. create the
  instance with 'az-test' availability zone will fail because without
  'az-test' availability_zone in nova scheduler.

  There is no way to know that host_aggregates_map is inconsistent with
  the database.

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