Listener timeout wrongly updated
Bug #1923605 reported by
Maysa de Macedo Souza
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The listeners timeout are constantly updated with Octavia default values for the timeouts, even if no annotation was set on the respective Service. The constant execution of this task makes all the Load Balancers on the cluster to be stuck with PENDING_UPDATE status.
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /kuryr- kubernetes/ +/786038 /opendev. org/openstack/ kuryr-kubernete s/commit/ f10003f67ee4c0b e2490c5c0499876 c4d8f6b40a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit f10003f67ee4c0b e2490c5c0499876 c4d8f6b40a
Author: Maysa Macedo <email address hidden>
Date: Tue Apr 13 11:35:25 2021 +0000
Fix constant update of Listeners timeout
The listeners timeout are constantly updated with
Octavia default values, even if no annotation was
updated on the respective Service. The constant
execution of this task makes the Load Balancer
to be stuck with PENDING_UPDATE status. This commit
fixes the issue by ensuring the listener values
are only added to the CR once there was annotation
changes, also it enforces the default values of not
existence of the field to be the same.
Change-Id: Id93ac765507613 98c853ebfd03ac2 e59667e0e06
Closes-Bug: 1923605