Controller marked as not ready if components have no limit for quota

Bug #1805814 reported by Maysa de Macedo Souza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
Undecided
Maysa de Macedo Souza

Bug Description

For the policy and vif handlers we didn't treat the case for when neutron resources don't have a limit defined, consequently it was marked as not ready. This can be fixed by assuring that the component is marked as ready when it has no limit.

Changed in kuryr-kubernetes:
assignee: nobody → Maysa de Macedo Souza (maysa)
status: New → In Progress
summary: - Controller marked as not if components have no limit for quota
+ Controller marked as not ready if components have no limit for quota
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-kubernetes (master)

Reviewed: https://review.openstack.org/620883
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=38f541604ff490fbc381f78a23655e30e6aa0bcc
Submitter: Zuul
Branch: master

commit 38f541604ff490fbc381f78a23655e30e6aa0bcc
Author: Maysa Macedo <email address hidden>
Date: Thu Nov 29 10:50:07 2018 +0000

    Fix quota readiness check

    For the policy and vif handlers we didn't treat the case for when
    neutron resources don't have a limit defined, consequently it was
    marked as not ready. This patchs fixes the issue by assuring the
    component is marked as ready when it has no limit.

    Closes-bug: #1805814

    Change-Id: I0a8a7665b01ca6f66c13aa71df0e74adca811d9b

Changed in kuryr-kubernetes:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kuryr-kubernetes 0.6.0

This issue was fixed in the openstack/kuryr-kubernetes 0.6.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers