Update git submodules
* Update nova from branch 'master' - Merge "Sanity check instance mapping during scheduling" - Sanity check instance mapping during scheduling mnaser reported a weird case where an instance was found in both cell0 (deleted there) and in cell1 (not deleted there but in error state from a failed build). It's unclear how this could happen besides some weird clustered rabbitmq issue where maybe the schedule and build request to conductor happens twice for the same instance and one picks a host and tries to build and the other fails during scheduling and is buried in cell0. To avoid a split brain situation like this, we add a sanity check in _bury_in_cell0 to make sure the instance mapping is not pointing at a cell when we go to update it to cell0. Similarly a check is added in the schedule_and_build_instances flow (the code is moved to a private method to make it easier to test). Worst case is this is unnecessary but doesn't hurt anything, best case is this helps avoid split brain clustered rabbit issues. Change-Id: I335113f0ec59516cb337d34b6fc9078ea202130f
This commit is contained in:
parent
fb0b486975
commit
355544d67c
2
nova
2
nova
@ -1 +1 @@
|
||||
Subproject commit e0adf82defe75b1b52249e8d0d781dc64e896765
|
||||
Subproject commit f1382651dc3b7b945b69a2af0bc05aa472f26b28
|
Loading…
Reference in New Issue
Block a user