Neutron LBaaS delay raises kuryr exception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Fix Released
|
High
|
Unassigned |
Bug Description
Dears,
K8s endpoints are supposed to be created and updated frequently in production.
The kuryr-kubernetes currently supports endpoint with Neutron LBaaS (or Octavia).
However, I've seen many PENDING_UPDATE state of LBaaS when multiple endpoints are updated at the same time.
(In both LBaaSv2 and Octavia Env)
Log example:
018-02-05 19:19:56.376 1 DEBUG kuryr_kubernete
2018-02-05 19:19:56.594 1 DEBUG kuryr_kubernete
kuryr-kubernetes now waits for LBaaS activation delay with FIXED CONSTANT TIMEOUT.
-> https:/
If LBaaS is not activated after the timeout, kuryr-controller raises the exception and doesn't do any behavior (No mercy on Neutron).
-> https:/
-> It does not clean up created resources, does not check any failure on k8s resource, and does not have deferred failsafe mechanism either.
I've tried to clean up resources after timeout, but releasing resources are failed again due to LBaaS delay.
The only solution I've come up with was just to configure _ACTIVATION_TIMEOUT of LBaaS and wait for longer dealy.
I'm not sure that this solution is right way to fix.
Please review the change or suggest another change.
Thanks.
Eunsoo Park (Evan)
description: | updated |
Changed in kuryr-kubernetes: | |
status: | New → Triaged |
importance: | Undecided → High |
Related fix proposed to branch: master /review. openstack. org/549945
Review: https:/