kuryr-kubernetes

kuryrnet leftovers after kuryr-controller restart

Bug #1848761 reported by Luis Tomas Bolivar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
Fix Released
Undecided
Luis Tomas Bolivar

Bug Description

When a namespace is deleted, kuryr-controller is in charge of
deleting its associated openstack resources (net, subnet and ports)
as well as the associated KuryrNet CRD.

As removing OpenStack resources may take some time, if the
kuryr-controller is restarted by any different reason during that
process, the resources are left behind as no new events for the
namespace (already deleted) happen after the restart.

OpenStack Infra (hudson-openstack)
Changed in kuryr-kubernetes:
assignee: nobody → Luis Tomas Bolivar (ltomasbo)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-kubernetes (master)

Reviewed: https://review.opendev.org/689440
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=6d43ad4c787a553e99ebaf5827dbd70e385db14c
Submitter: Zuul
Branch: master

commit 6d43ad4c787a553e99ebaf5827dbd70e385db14c
Author: Luis Tomas Bolivar <email address hidden>
Date: Fri Oct 18 14:26:45 2019 +0200

    Remove namespace leftover upon kuryr-controller restart

    When a namespace is deleted, kuryr-controller is in charge of
    deleting its associated openstack resources (net, subnet and ports)
    as well as the associated KuryrNet CRD.

    As removing OpenStack resources may take some time, if the
    kuryr-controller is restarted by any different reason during that
    process, the resources will be left behind as no new events for the
    namespace (already deleted) will happen after the restart. This
    patch fixes this problem by ensuring upon reboot that there are no
    orphan KuryrNet CRDs for unexisting namespaces, and deleting them
    in case there are (including its associated OpenStack resources).

    Closes-Bug: 1848761

    Change-Id: I0c4852f5bb816756cc1bf536354da20aa3948dc7

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

Fix proposed to branch: stable/train
Review: https://review.opendev.org/690073

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

Reviewed: https://review.opendev.org/690073
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=20cf936db50bcb89a2a4d5843e297d4cad2560a5
Submitter: Zuul
Branch: stable/train

commit 20cf936db50bcb89a2a4d5843e297d4cad2560a5
Author: Luis Tomas Bolivar <email address hidden>
Date: Fri Oct 18 14:26:45 2019 +0200

    Remove namespace leftover upon kuryr-controller restart

    When a namespace is deleted, kuryr-controller is in charge of
    deleting its associated openstack resources (net, subnet and ports)
    as well as the associated KuryrNet CRD.

    As removing OpenStack resources may take some time, if the
    kuryr-controller is restarted by any different reason during that
    process, the resources will be left behind as no new events for the
    namespace (already deleted) will happen after the restart. This
    patch fixes this problem by ensuring upon reboot that there are no
    orphan KuryrNet CRDs for unexisting namespaces, and deleting them
    in case there are (including its associated OpenStack resources).

    Closes-Bug: 1848761

    Change-Id: I0c4852f5bb816756cc1bf536354da20aa3948dc7
    (cherry picked from commit 6d43ad4c787a553e99ebaf5827dbd70e385db14c)

tags: added: in-stable-train
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.