| 2019-07-04 14:14:53 |
Balazs Gibizer |
description |
The nova-manage placement heal_allocation implementation queries the instance consumer from placement[1][2]. It assumes that if the placement query returned a non 200 response then the consumer does not exists and needs to be healed. However placement returns http 200 even if the consumer does not exits so the assumption in [1] is invalid.
[1]https://github.com/openstack/nova/blob/de2c04981b438d4d10d4ee0207d79b4d3ec5135e/nova/cmd/manage.py#L1718-L1727
[2]https://github.com/openstack/nova/blob/de2c04981b438d4d10d4ee0207d79b4d3ec5135e/nova/scheduler/client/report.py#L1509 |
The nova-manage placement heal_allocation implementation queries the instance consumer from placement[1][2]. It assumes that if the placement query returned a non 200 response then the consumer does not exists and needs to be healed. However placement returns http 200 even if the consumer does not exits [3] so the assumption in [1] is invalid.
[1]https://github.com/openstack/nova/blob/de2c04981b438d4d10d4ee0207d79b4d3ec5135e/nova/cmd/manage.py#L1718-L1727
[2]https://github.com/openstack/nova/blob/de2c04981b438d4d10d4ee0207d79b4d3ec5135e/nova/scheduler/client/report.py#L1509
[3] https://developer.openstack.org/api-ref/placement/?expanded=list-allocations-detail#list-allocations |
|
