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

Bug 1831967

Summary: ERROR PlatformFeaturesAvailability:124 - Detection of Kuberetes version failed
Product: OpenShift Container Platform Reporter: Jatan Malde <jmalde>
Component: ISV OperatorsAssignee: Matt Dorn <mdorn>
Status: CLOSED WONTFIX QA Contact: Bruno Andrade <bandrade>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.zCC: aos-bugs, jcrumple, mdorn, pkanthal, sd-ecosystem
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-30 18:04: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 Jatan Malde 2020-05-06 03:29:14 UTC
Description of problem:

IHAC reporting usage of amq-streams-1.4.1 on OCP 4.2 and the cluster-operator fails with the following message, 

2020-05-06 02:41:43 INFO  Main:58 - ClusterOperator 0.17.0.GA-redhat-00006 is starting
2020-05-06 02:41:45 ERROR PlatformFeaturesAvailability:124 - Detection of Kuberetes version failed.
io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.
	at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:64) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:53) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.fabric8.kubernetes.client.dsl.internal.ClusterOperationsImpl.fetchVersion(ClusterOperationsImpl.java:51) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.fabric8.kubernetes.client.DefaultKubernetesClient.getVersion(DefaultKubernetesClient.java:293) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.strimzi.operator.PlatformFeaturesAvailability.lambda$getVersionInfoFromKubernetes$5(PlatformFeaturesAvailability.java:122) ~[io.strimzi.operator-common-0.17.0.GA-redhat-00006.jar:0.17.0.GA-redhat-00006]
	at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$2(ContextImpl.java:316) ~[io.vertx.vertx-core-3.8.5.redhat-00005.jar:3.8.5.redhat-00005]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[io.vertx.vertx-core-3.8.5.redhat-00005.jar:3.8.5.redhat-00005]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_252]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_252]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty.netty-common-4.1.45.Final-redhat-00002.jar:4.1.45.Final-redhat-00002]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]

I will include the csv and packagemanifests details on the latest comments. 

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


How reproducible:
Steps to Reproduce:
1. Deploy OCP 4.2 cluster(latest would also be fine)
2. From the OperatorHub select AMQ-stream operator
3. checking the amq-streams-cluster-operator logs itself.

Actual results:

The cluster-operator fails on the first place while the rest of provider.apis do not get registered

Expected results:

It is expected that the operator is configured to correctly detect the kuberenetes version

Additional info:

1. Operator pod logs, 
2. csv uploaded
3. packagemanifests specfying the channel where it got included.

I tested the amq-stream operator in OCP 4.3 and the operator was successfully started with errors.

Comment 5 Hugo Cisneiros (Eitch) 2020-05-13 20:34:47 UTC
Hi there,

I have another case with this exact error, running on OCP 4.3.1. Logs:

2020-05-12 08:19:38 INFO  Main:58 - ClusterOperator 0.17.0.GA-redhat-00006 is starting
2020-05-12 08:19:39 ERROR PlatformFeaturesAvailability:124 - Detection of Kuberetes version failed.
io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.
	at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:64) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:53) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.fabric8.kubernetes.client.dsl.internal.ClusterOperationsImpl.fetchVersion(ClusterOperationsImpl.java:51) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.fabric8.kubernetes.client.DefaultKubernetesClient.getVersion(DefaultKubernetesClient.java:293) ~[io.fabric8.kubernetes-client-4.6.4.redhat-00001.jar:?]
	at io.strimzi.operator.PlatformFeaturesAvailability.lambda$getVersionInfoFromKubernetes$5(PlatformFeaturesAvailability.java:122) ~[io.strimzi.operator-common-0.17.0.GA-redhat-00006.jar:0.17.0.GA-redhat-00006]
	at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$2(ContextImpl.java:316) ~[io.vertx.vertx-core-3.8.5.redhat-00005.jar:3.8.5.redhat-00005]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[io.vertx.vertx-core-3.8.5.redhat-00005.jar:3.8.5.redhat-00005]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_252]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_252]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty.netty-common-4.1.45.Final-redhat-00002.jar:4.1.45.Final-redhat-00002]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
Caused by: java.net.SocketException: Broken pipe (Write failed)
	at java.net.SocketOutputStream.socketWrite0(Native Method) ~[?:1.8.0_252]
[...]

Notice the "Broken pipe (Write failed)" there, but I couldn't notice any problems with the Kubernetes API and everything else in the cluster seems to be working.

Image used by the operator pod:

registry.redhat.io/amq7/amq-streams-rhel7-operator@sha256:49206f4add46050cdd0da7cb74f1f767240892403695e9e7119f68784da545af

I don't know if it's still possible to upgrade OCP to the latest 4.3.x version but I'll update here if so. Let me know if you need any more information.

Comment 8 Matt Dorn 2020-05-21 22:05:03 UTC
*** Bug 1837416 has been marked as a duplicate of this bug. ***

Comment 18 Rory Thrasher 2024-04-30 18:04:53 UTC
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary