DO180 - Persistent SSL Error When Starting OpenShift Lab – Environment Consumption Issue

[Flavio_2C]

 Persistent SSL Error When Starting OpenShift Lab – Environment Consumption Issue**

Hi everyone,

I'm encountering a recurring issue when starting labs in OpenShift using the `lab start <labName>` command. The error looks like this:

storage-classes:ERROR:utils.py(69) Error invoking condition HTTPSConnectionPool(host='console-openshift-console.apps.ocp4.example.com', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLZeroReturnError(6, 'TLS/SSL connection has been closed (EOF) (_ssl.c:1129)')))

This error typically resolves itself after about **30 minutes**, but I often have to retry the `lab start` command **multiple times** (usually it works on the third attempt). The problem is that during this waiting period, I lose valuable lab time.

Since the lab environment is billed **by the hour**, this behavior is unsustainable. For example, if I enter the lab 10 times and lose the first hour each time, that’s **10 hours wasted** without being able to work productively.

Has anyone experienced something similar? Is there a known workaround or fix for this SSL issue? Any help or insight would be greatly appreciated.

Thanks in advance!

[ARoumiantsev]

Hi @Flavio_2C 

I think that you meet with well known issue, it discussed many time here. Please, refer to https://learn.redhat.com/t5/Containers-DevOps-OpenShift/OCP-Cluster-takes-time-to-get-ready-in-OpenS... for example. I hope you find the solution there.

Good luck

[bchardim · Accepted solution]

This is one of the reasons to wait until the wait.sh finishes the execution before starting any lab. One of the things that wait.sh checks and waits for is the internal TLS autorenew process completion that OCP triggers internally to renew cluster TLS certificates ( that expires every 30 days). 

[Chetan_Tiwary_ · Accepted solution]

@Flavio_2C yes the OCP cluster takes time, 30 mins approx each time you start your labs ( or build a new lab ), to get ready before you can send any request to the API. 

Once it is ready - you can continue the lab work unless you stop the lab or rebuild the lab in which case you need to wait for 30 mins before doing any work.