Couldn’t it just have a configuration option to enable it? While I’m not convinced it can fix the root cause of our
problem, it could at least contribute to the stability of our and other people’s Openstack cluster.
so this is a subtel thing. its not really a nova bug. its an issue where invalid data is returned by neuton and that
currupts the nova database. The force refesh will heal nova if and only if the neutron issue that casue the issue in the
first place is resovled. if the neutron issue is not fix then the force refresh will contiune to force update the nova
networking info cache with incomplete data.
so if you never have a netuon issue that returns invalid data then you will never need this patch
if you do for say because you broke the neutron policy file then this backprot will fix the nova database only
once the policy issue is corrected. we have had several large customer that have had issue with neutron due to
misconfiging the polify file or due to a third part sdn contol who maintianed port information in an external db
seperate form neutron. in the case of the policy file customer this self healing worked once they corrected the issue.
in the case of the sdn contoler customer it did not until the sdn vendor fix the sdn contols db. once it returned
correct data again the periodic task healed nova.