Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-7043

"Delete dependent objects of this resource" might cause confusions

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.13.0, 4.12.0, 4.11.0, 4.10.0, 4.9.0, 4.8.0
    • Dev Console
    • Moderate
    • ODC Sprint 232
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: The web console shows a pre-selected "Delete dependent objects of this resource" checkbox when deleting a Deployment, or many other resources. Users expected that deleting a Deployment removes all resources that the web console created when using the "Import from Git" or "Import image container" flow. But other resources like the created ImageStream, Route, Service and Secrets wasn't deleted. The checkbox only deletes resources that are linked with metadata.ownerReferences field. See https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/

      Consequence: Users are confused that the web console doesn't delete everything. And a new import via "Import from Git" or "Import image container" (with the same name) fails because of these leftover resources with an error "ImageStream with that name already exists".

      Fix: When deleting a Deployment the web console now shows a second pre-selected option "Delete other resources created by console". If the user kept this checkbox enabled all mentioned resources above are automatically deleted.

      Result: The web console now cleanup resources it creates and allows the user to reimport the same application with the same name again.
      Show
      Cause: The web console shows a pre-selected "Delete dependent objects of this resource" checkbox when deleting a Deployment, or many other resources. Users expected that deleting a Deployment removes all resources that the web console created when using the "Import from Git" or "Import image container" flow. But other resources like the created ImageStream, Route, Service and Secrets wasn't deleted. The checkbox only deletes resources that are linked with metadata.ownerReferences field. See https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/ Consequence: Users are confused that the web console doesn't delete everything. And a new import via "Import from Git" or "Import image container" (with the same name) fails because of these leftover resources with an error "ImageStream with that name already exists". Fix: When deleting a Deployment the web console now shows a second pre-selected option "Delete other resources created by console". If the user kept this checkbox enabled all mentioned resources above are automatically deleted. Result: The web console now cleanup resources it creates and allows the user to reimport the same application with the same name again.
    • Proposed

      This is a clone of issue OCPBUGS-6766. The following is the description of the original issue:

      This is a clone of https://bugzilla.redhat.com/show_bug.cgi?id=2083087 (OCPBUGSM-44070) to backport this issue.

      Description of problem:
      "Delete dependent objects of this resource" is a bit of confusing for some users because when creating the Application in Dev console not only the deployment but also IS, route, svc, secret objects will be created as well. When deleting the Application (in fact it is deployment), there is an option called "Delete dependent objects of this resource" and some users might think this means the IS, route, svc and any other objects which are created alongside with the deployment will be deleted as well

      Version-Release number of selected component (if applicable):
      4.8

      How reproducible:
      Always

      Steps to Reproduce:
      1. Create Application in Dev console
      2. Delete the deployment
      3. Check "Delete dependent objects of this resource"

      Actual results:
      Only deployment will be deleted and IS, svc, route will not be deleted

      Expected results:
      We either change the description of this option, or we really delete IS, svc, route and any other objects created under this Application.

      Additional info:

            divgupta Divyanshi Gupta
            openshift-crt-jira-prow OpenShift Prow Bot
            Sanket Pathak Sanket Pathak
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: