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

"Delete dependent objects of this resource" might cause confusions

    XMLWordPrintable

Details

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

      None

      Show
      None
    • Hide
      * Previously, when deleting a deployment or resources, the web console shows a pre-selected *Delete dependent objects of this resource* checkbox. This action did not remove all the resources created when using the *Import from Git* or *Import image container* flows and new imports failed. With this fix, a second pre-selected option *Delete other resources created by console* is introduced which deletes all the resources. As a result, you can import the same application with the same name again. (link:https://issues.redhat.com/browse/OCPBUGS-6765[*OCPBUGS-6765*])
      Show
      * Previously, when deleting a deployment or resources, the web console shows a pre-selected *Delete dependent objects of this resource* checkbox. This action did not remove all the resources created when using the *Import from Git* or *Import image container* flows and new imports failed. With this fix, a second pre-selected option *Delete other resources created by console* is introduced which deletes all the resources. As a result, you can import the same application with the same name again. (link: https://issues.redhat.com/browse/OCPBUGS-6765 [* OCPBUGS-6765 *])
    • Bug Fix
    • Done

    Description

      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:

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-6766 "Delete dependent objects of this resource" might cause confusions

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is depended on by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-6766 "Delete dependent objects of this resource" might cause confusions

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-6685 [knative][flake] Removal of the whole app leaves the imagestream

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link Github openshift/console/pull/12390

          Activity

            People

              divgupta Divyanshi Gupta
              cjerolim Christoph Jerolimov
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: