Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2010647

Summary:	ReplicationController objects are not getting deleted when deleting the DeploymentConfig (DC).
Product:	OpenShift Container Platform	Reporter:	Divyam Pateriya <dpateriy>
Component:	kube-controller-manager	Assignee:	Tomas Smetana <tsmetana>
Status:	CLOSED NOTABUG	QA Contact:	zhou ying <yinzhou>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.8	CC:	aos-bugs, jfindysz, mfojtik, openshift-bugs-escalate, sttts, wking
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	EmergencyRequest
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-06 09:10:53 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 Divyam Pateriya 2021-10-05 09:23:20 UTC

Description of problem:

Dependent objects are not deleted when deployment config is removed

ReplicationController objects are not getting deleted when deleting the DeploymentConfig (DC).

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

How reproducible:
Customer Specific


Actual results:
Deleting deploymentconfig isn't deleting the replicationcontroller as well.

Expected results:
Deleting deploymentconfig should delete the replicationcontroller.

Additional info:
This is happening only on one cluster which was actually upgraded to clusters to v4.8.12.

I will upload all the required data shortly

Comment 2 Michal Fojtik 2021-10-05 09:30:07 UTC

** A NOTE ABOUT USING URGENT **

This BZ has been set to urgent severity and priority. When a BZ is marked urgent priority Engineers are asked to stop whatever they are doing, putting everything else on hold.
Please be prepared to have reasonable justification ready to discuss, and ensure your own and engineering management are aware and agree this BZ is urgent. Keep in mind, urgent bugs are very expensive and have maximal management visibility.

NOTE: This bug was automatically assigned to an engineering manager with the severity reset to *unspecified* until the emergency is vetted and confirmed. Please do not manually override the severity.

** INFORMATION REQUIRED **

Please answer these questions before escalation to engineering:

1. Has a link to must-gather output been provided in this BZ? We cannot work without. If must-gather fails to run, attach all relevant logs and provide the error message of must-gather.
2. Give the output of "oc get clusteroperators -o yaml".
3. In case of degraded/unavailable operators, have all their logs and the logs of the operands been analyzed [yes/no]
4. List the top 5 relevant errors from the logs of the operators and operands in (3).
5. Order the list of degraded/unavailable operators according to which is likely the cause of the failure of the other, root-cause at the top.
6. Explain why (5) is likely the right order and list the information used for that assessment.
7. Explain why Engineering is necessary to make progress.

Comment 6 Stefan Schimanski 2021-10-05 11:48:06 UTC

Garbage collection controller is broken due a wrongly configured conversion webhooks:

2021-10-04T17:54:13.166169446Z E1004 17:54:13.165999      19 cacher.go:420] cacher (*unstructured.Unstructured): unexpected ListAndWatch error: failed to list workspace.devfile.io/v1alpha2, Kind=DevWorkspace: conversion webhook for workspace.devfile.io/v1alpha1, Kind=DevWorkspace failed: Post "https://devworkspace-controller-manager-service.openshift-operators.svc:443/convert?timeout=30s": service "devworkspace-controller-manager-service" not found; reinitializing...

Please remove the CRD (and with that the webhook definition). Please confirm that this helps and close the bug if it does.