Bug 1876434 - kuryrnetworks blocking namespace deletion
Summary: kuryrnetworks blocking namespace deletion
Keywords:
Status: CLOSED DUPLICATE of bug 1873449
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Luis Tomas Bolivar
QA Contact: GenadiC
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-07 08:16 UTC by zhou ying
Modified: 2020-09-07 10:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-07 10:46:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description zhou ying 2020-09-07 08:16:39 UTC
Description of problem:
kuryrnetworks blocking namespace deletion 

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-09-03-084733

How reproducible:
Sometimes

Steps to Reproduce:
1. The automated case failed with delete the project 

Actual results:
1. Project deletion blocked by kuryrnetworks:

08:40:48 INFO> Shell Commands: oc delete projects ns-ocp30279 --wait=false --kubeconfig=/home/jenkins/workspace/Runner-v3/workdir/ocp4_admin.kubeconfig
project.project.openshift.io "ns-ocp30279" deleted
08:40:49 INFO> Exit Status: 0
08:40:50 INFO> oc get projects ns-ocp30279 --output=yaml --kubeconfig=/home/jenkins/workspace/Runner-v3/workdir/ocp4_admin.kubeconfig
08:45:50 INFO> After 145 iterations and 301 seconds:
apiVersion: project.openshift.io/v1
kind: Project
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Namespace","metadata":{"annotations":{},"labels":{"openshift.io/cluster-monitoring":"true"},"name":"ns-ocp30279"},"spec":{}}
    openshift.io/sa.scc.mcs: s0:c66,c20
    openshift.io/sa.scc.supplemental-groups: 1004330000/10000
    openshift.io/sa.scc.uid-range: 1004330000/10000
  creationTimestamp: "2020-09-02T08:40:45Z"
  deletionTimestamp: "2020-09-02T08:40:49Z"
  labels:
    olm.operatorgroup.uid/ef06dae7-47a3-40d2-9193-d5133bc6fa72: ""
    openshift.io/cluster-monitoring: "true"
  managedFields:
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          f:openshift.io/sa.scc.mcs: {}
          f:openshift.io/sa.scc.supplemental-groups: {}
          f:openshift.io/sa.scc.uid-range: {}
    manager: cluster-policy-controller
    operation: Update
    time: "2020-09-02T08:40:45Z"
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:labels:
          .: {}
          f:openshift.io/cluster-monitoring: {}
      f:status:
        f:phase: {}
    manager: oc
    operation: Update
    time: "2020-09-02T08:40:45Z"
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        f:conditions:
          .: {}
          k:{"type":"NamespaceContentRemaining"}:
            .: {}
            f:lastTransitionTime: {}
            f:message: {}
            f:reason: {}
            f:status: {}
            f:type: {}
          k:{"type":"NamespaceDeletionContentFailure"}:
            .: {}
            f:lastTransitionTime: {}
            f:message: {}
            f:reason: {}
            f:status: {}
            f:type: {}
          k:{"type":"NamespaceDeletionDiscoveryFailure"}:
            .: {}
            f:lastTransitionTime: {}
            f:message: {}
            f:reason: {}
            f:status: {}
            f:type: {}
          k:{"type":"NamespaceDeletionGroupVersionParsingFailure"}:
            .: {}
            f:lastTransitionTime: {}
            f:message: {}
            f:reason: {}
            f:status: {}
            f:type: {}
          k:{"type":"NamespaceFinalizersRemaining"}:
            .: {}
            f:lastTransitionTime: {}
            f:message: {}
            f:reason: {}
            f:status: {}
            f:type: {}
    manager: kube-controller-manager
    operation: Update
    time: "2020-09-02T08:41:05Z"
  - apiVersion: v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          f:olm.operatorgroup.uid/ef06dae7-47a3-40d2-9193-d5133bc6fa72: {}
    manager: olm
    operation: Update
    time: "2020-09-02T08:42:05Z"
  name: ns-ocp30279
  resourceVersion: "124953"
  selfLink: /apis/project.openshift.io/v1/projects/ns-ocp30279
  uid: 35b61cbc-e0dc-41a6-8ea5-88e92c30c21e
spec:
  finalizers:
  - kubernetes
status:
  conditions:
  - lastTransitionTime: "2020-09-02T08:41:05Z"
    message: All resources successfully discovered
    reason: ResourcesDiscovered
    status: "False"
    type: NamespaceDeletionDiscoveryFailure
  - lastTransitionTime: "2020-09-02T08:41:05Z"
    message: All legacy kube types successfully parsed
    reason: ParsedGroupVersions
    status: "False"
    type: NamespaceDeletionGroupVersionParsingFailure
  - lastTransitionTime: "2020-09-02T08:41:05Z"
    message: All content successfully deleted, may be waiting on finalization
    reason: ContentDeleted
    status: "False"
    type: NamespaceDeletionContentFailure
  - lastTransitionTime: "2020-09-02T08:41:05Z"
    message: 'Some resources are remaining: kuryrnetworks.openstack.org has 1 resource
      instances'
    reason: SomeResourcesRemain
    status: "True"
    type: NamespaceContentRemaining
  - lastTransitionTime: "2020-09-02T08:41:05Z"
    message: 'Some content in the namespace has finalizers remaining: kuryrnetwork.finalizers.kuryr.openstack.org
      in 1 resource instances'
    reason: SomeFinalizersRemain
    status: "True"
    type: NamespaceFinalizersRemaining
  phase: Terminating
08:45:50 ERROR> #<RuntimeError: BushSlicer::Project ns-ocp30279 did not disappear within 300 sec>


Expected results:
1. Project delete succeed.

Additional info:

Comment 2 Maciej Szulik 2020-09-07 09:58:57 UTC
Sending this to kuryr team to investigate since they own that bit and it's clearly their finalizer that is blocking namespace deletion.

Comment 3 Luis Tomas Bolivar 2020-09-07 10:46:13 UTC
This is most probably a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1873449 and should be fixed already (on a more recent release image, it was a problem on the fix of that bug actually). Closing it, but feel free to reopen (or comment in the other one) if you hit it on a newer image

*** This bug has been marked as a duplicate of bug 1873449 ***


Note You need to log in before you can comment on or make changes to this bug.