Hi,Wierzchowski
Thank you for your advice.
I recreated OCP environment and did not shutdown the cluster in the first 24h after installation.
As a result, the issue did not occured when I restart the cluster.
------------------------------
Yuji Ohashi
------------------------------
Original Message:
Sent: Mon June 19, 2023 01:47 AM
From: Witold Wierzchowski
Subject: CLB(Classic Load Balancer) to be anhelthy after created MAS Manage (Maximo 8.x) on SNO in AWS
It is most probably caused by expired internal OCP certificates. You cannot shutdown the cluster in the first 24h after installation (https://access.redhat.com/solutions/4271712).
Resolving this with SNO will be a bit tricky. You would have to log into the node using SSH key and accept pending CSRs
export KUBECONFIG=/etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/lb-int.kubeconfig
oc get csr -o name | xargs oc adm certificate approve
------------------------------
Witold Wierzchowski
Original Message:
Sent: Fri June 16, 2023 03:30 AM
From: Yuji Ohashi
Subject: CLB(Classic Load Balancer) to be anhelthy after created MAS Manage (Maximo 8.x) on SNO in AWS
I stoped EC2 after I created MAS Manage (Maximo 8.X) on SNO in AWS.
When I started EC2 after few days, I noticed CLB helthcheck status became unhelthy and I have never access to OCP Management Console and MAS Management Console.
This issue didn't occur when I restarted EC2 immediately after MAS created.
Any one has previous experience with resolving such issues?
------------------------------
Yuji Ohashi
------------------------------