Listener timeout wrongly updated

Bug #1923605 reported by Maysa de Macedo Souza on 2021-04-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-kubernetes (master)

Reviewed: https://review.opendev.org/c/openstack/kuryr-kubernetes/+/786038
Committed: https://opendev.org/openstack/kuryr-kubernetes/commit/f10003f67ee4c0be2490c5c0499876c4d8f6b40a
Submitter: "Zuul (22348)"
Branch: master

commit f10003f67ee4c0be2490c5c0499876c4d8f6b40a
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: Id93ac76550761398c853ebfd03ac2e59667e0e06
    Closes-Bug: 1923605

Changed in kuryr-kubernetes:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers