Bug 2055938

Summary:	Stuck with timeouts when executed "oc replace --force"
Product:	OpenShift Container Platform	Reporter:	Daein Park <dapark>
Component:	kube-apiserver	Assignee:	Abu Kashem <akashem>
Status:	CLOSED EOL	QA Contact:	Ke Wang <kewang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	aojeagar, aos-bugs, hfuruich, mfojtik, xxia
Target Milestone:	---
Target Release:	---
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-08-22 09:13:05 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 Daein Park 2022-02-18 00:58:39 UTC

Description of problem:

If the --force option is given as in documentation[0], oc replace command will hang and then timeout in OCP 4.9 as follows:

~~~
$ oc project openshift

$ oc replace --force -f http://raw.githubusercontent.com/jboss-container-images/jboss-eap-openshift-templates/eap74/eap74-openjdk8-image-stream.json

W0117 12:32:44.636847   34887 shim_kubectl.go:55] Using non-groupfied API resources is deprecated and will be removed in a future release, update apiVersion to "image.openshift.io/v1" for your resource
imagestream.image.openshift.io "jboss-eap74-openjdk8-openshift" deleted
W0117 12:32:44.643928   34887 shim_kubectl.go:55] Using non-groupfied API resources is deprecated and will be removed in a future release, update apiVersion to "image.openshift.io/v1" for your resource
imagestream.image.openshift.io "jboss-eap74-openjdk8-runtime-openshift" deleted
W0117 12:32:44.885457   34887 shim_kubectl.go:55] Using non-groupfied API resources is deprecated and will be removed in a future release, update apiVersion to "image.openshift.io/v1" for your resource
W0117 12:37:44.898751   34887 shim_kubectl.go:55] Using non-groupfied API resources is deprecated and will be removed in a future release, update apiVersion to "image.openshift.io/v1" for your resource

timed out waiting for the condition   <<<===
timed out waiting for the condition   <<<===
~~~

[0] 2.4. Import the Latest JBoss EAP for OpenShift Imagestreams and Templates
    [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.4/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/index#import_imagestreams_templates]

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

$ oc version
Client Version: 4.9.11
Server Version: 4.9.11

How reproducible:

Customer said it always reproduced when executed with "--force" option at their OCP cluster as follows

Steps to Reproduce:

1. "oc project openshift"
2. "oc replace --force -f http://raw.githubusercontent.com/jboss-container-images/jboss-eap-openshift-templates/eap74/eap74-openjdk8-image-stream.json"

Actual results:

"oc replace --force" command stopped with "timed out waiting for the condition" messages.

Expected results:

"oc replace --force" command complete without any issues.

Additional info:

This issue has been reported from customers.