I wanted to note that although the "just restart nova scheduler"
workaround is "simple", it's not actually usable, as we'd potentially
need to restart nova scheduler after every parallel call to the
aggregates API.


For our usage, we ended up needing to fork nova and write a custom prefilter 
rather than using filter plugins.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542491

Title:
  Scheduler update_aggregates race causes incorrect aggregate
  information

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to