Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-2461

Race during deletion of resources in terminating member namespace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • maistra-2.0.6.2
    • maistra-2.0.5
    • operator
    • None
    • Sprint 6, Sprint 7

      When you delete a member namespace and immediately also remove it from the ServiceMeshMemberRoll, the operator starts deleting resources in the namespace, but OpenShift also does this. You end up with errors in the operator log, because a resources may get deleted by OpenShift just as the operator tries to delete it.

      This scenario is especially common when using the ServiceMeshMember resource. By deleting the namespace, the resource is deleted by OpenShift. This causes the servicemeshmember controller in the operator to remove the namespace from the ServiceMeshMemberRoll and this then causes the servicemeshmemberroll controller to start deleting the resources in the namespace. At the same time, OpenShift may still be deleting the other resources in the namespace.

      There's no need for the operator to delete mesh resources in a namespace that's being deleted. OpenShift cleans up everything itself. The only time the operator needs to delete mesh resources from a member namespace is when the member is removed from the SMMR (and the namespace is NOT deleted).

              mluksa@redhat.com Marko Luksa
              mluksa@redhat.com Marko Luksa
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: