Late affinity check failre counted as failed build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Yusuke Okada |
Bug Description
The late anti-affinity checks runs in the compute manager to avoid parallel scheduling requests to invalidate the anti-affinity server group policy. When the check fails the instance is re-scheduled. However this failure counted as a real instance boot failure of the compute host[1][2][3] and can lead to de-prioritization of the compute host in the scheduler via BuildFailureWei
[1] https:/
[2] https:/
[3] https:/
[4] https:/
tags: | added: compute scheduler |
Changed in nova: | |
assignee: | nobody → Amit Uniyal (auniyal) |
Changed in nova: | |
assignee: | nobody → Yusuke Okada (yusokada) |
this is a bug yes and a trivially fixable one.
we just need to add a new exception that inherits from the existing build failed exception and skip incrementing the fail
count if its for affinity.
setting this to low as the impact is low and this is more an optimisation then a bug.