Bug 2027524

Summary: Delete Application doesn't delete Channels or Brokers
Product: OpenShift Container Platform Reporter: Serena <sdoyle>
Component: Dev ConsoleAssignee: Debsmita Santra <dsantra>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9CC: aos-bugs, dsantra, jakumar, kjeeyar, nmukherj
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:31:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Serena 2021-11-29 22:00:50 UTC 
Description of problem:
If the user is in Topology and deletes an application containing a broker OR a channel, all objects are deleted except for brokers and channels, thus the application is still left standing.

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


How reproducible:

Every time


Steps to Reproduce:
1. Use Import from Git - add it to Application A
2.Create a Broker and put it in Application A
3.From topology, right click on Application A and hit Delete application

Actual results:

The Deployment is removed, but the broker and application are left

Expected results:

The deployment, broker and application should all be deleted.
Additional info:
Comment 7 spathak@redhat.com 2022-02-04 09:44:49 UTC 
Verified on build version: 4.10.0-0.nightly-2022-02-04-015640
Browser: Google Chrome 97
Comment 9 errata-xmlrpc 2022-03-10 16:31:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056