Pre-cached neutron-port resource residues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
New
|
Undecided
|
Unassigned |
Bug Description
I have a node deleted and the port previously cached on that node still exists.
Residual resources in two cases.
1、When the ovs-agent exception on a kuryr node results in the creation of a neutron-port binding failed. This situation will result in the creation of a large number of neutron-ports on that node, and there is no place to remove the port that failed to be bound.
2、When a node with k8s is removed, the neutron-port previously cached on that node still exists.
Also, I have a question:
In the interface _recover_
if not port.binding_
# NOTE(ltomasbo): kuryr-controller is running without the
# rights to get the needed information to recover the ports.
# Thus, removing the port instead
In case port.binding_
1. I don't think we ever saw this happening, can you elaborate? /github. com/openstack/ kuryr-kubernete s/blob/ master/ kuryr_kubernete s/controller/ drivers/ vif_pool. py#L482. Do you think it doesn't work? Do you use nested or neutron VIF driver?
2 We have this part of code that's being run periodically: https:/
3. Right, it may make sense to delete them there, though binding_failed is most of the time indication of some Neutron issues, so underlying cluster might be just broken.