Public bug reported: This issue was found in stable/havana when we upgraded nova DB from folsom to havana.
When there are multiple host aggregates associated with an availability zone, the migration logic add all hosts belong to the availability zone to the first host aggregate. The code at line 41 of /nova/nova/db/sqlalchemy/migrate_repo/versions/147_no_service_zones.py ** Affects: nova Importance: Undecided Assignee: wei tian (weitian) Status: New ** Changed in: nova Assignee: (unassigned) => wei tian (weitian) -- 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/1336048 Title: hosts added to the wrong host aggregate in DB sync Status in OpenStack Compute (Nova): New Bug description: This issue was found in stable/havana when we upgraded nova DB from folsom to havana. When there are multiple host aggregates associated with an availability zone, the migration logic add all hosts belong to the availability zone to the first host aggregate. The code at line 41 of /nova/nova/db/sqlalchemy/migrate_repo/versions/147_no_service_zones.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1336048/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp