Bug 2055938 - Stuck with timeouts when executed "oc replace --force"
Summary: Stuck with timeouts when executed "oc replace --force"
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Abu Kashem
QA Contact: Ke Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-18 00:58 UTC by Daein Park
Modified: 2022-08-25 05:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-22 09:13:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.