Bug 1327513

Summary: Deleting deploymentconfigs buildconfigs on Web GUI does not work
Product: OpenShift Container Platform Reporter: Miheer Salunke <misalunk>
Component: RFEAssignee: Samuel Padgett <spadgett>
Status: CLOSED DEFERRED QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, erich, jforrest, jokerman, maszulik, mbarrett, misalunk, mmccomas, pweil, spadgett, trankin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-12 13:54:36 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:

Description Miheer Salunke 2016-04-15 09:41:22 UTC 
Description of problem:

If we are deleting a deployment config via oc command, its works like it is expected.
If we are deleting a deployment config via web gui, the dc will be deleted, but the rc and pods still exist.

oc delete dc <dc-config> will delete dc, rc and pods. Everything to do with the dc has (rc, pods) will be deleted.

The GUi says the dc is marked to deletion.
I added two images from the pod and deployment overview.
Bildschirmfoto_2016-04-14_um_14.43.50.png 
Bildschirmfoto_2016-04-14_um_14.43.40.png 
oc delete dc test will delete and destroy all pods.


We have the same with buildconfigs.
oc delete bc will delete the buildconfig and all builds.
The GUI will only delete the buildconfig. The all builds needs delete manually.
Bildschirmfoto_2016-04-14_um_14.47.06.png (


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

[root@ose-master2 ~]# rpm -qa | grep openshift
openshift-ansible-filter-plugins-3.0.47-1.git.0.4498ce3.el7aos.noarch
openshift-ansible-lookup-plugins-3.0.47-1.git.0.4498ce3.el7aos.noarch
atomic-openshift-utils-3.0.47-1.git.0.4498ce3.el7aos.noarch
atomic-openshift-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
atomic-openshift-node-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
atomic-openshift-master-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
openshift-ansible-3.0.47-1.git.0.4498ce3.el7aos.noarch
openshift-ansible-playbooks-3.0.47-1.git.0.4498ce3.el7aos.noarch
atomic-openshift-clients-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
tuned-profiles-atomic-openshift-node-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64
openshift-ansible-roles-3.0.47-1.git.0.4498ce3.el7aos.noarch
atomic-openshift-sdn-ovs-3.1.1.6-4.git.32.adf8ec9.el7aos.x86_64


How reproducible:
Always

Steps to Reproduce:
1.Mentioned in the description
2.
3.

Actual results:
deleting dc from ui shall delete rc and pods
deleting bc from ui shall delete builds. The all builds needs delete manually. 

Expected results:
deleting dc from ui deletes only dc
deleting bc from ui deletes only bc

Additional info:
Comment 4 Jessica Forrester 2016-04-15 12:57:31 UTC 
The API does not properly support cascading deletes today, the CLI is making individual calls to go delete each on of those builds/deployments.  We will implement cascading delete in the console when it is supported by the API.
Comment 5 Jessica Forrester 2016-08-08 17:10:58 UTC 
*** Bug 1364952 has been marked as a duplicate of this bug. ***
Comment 12 Eric Rich 2018-03-12 13:54:36 UTC 
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.