Hello @Hae  Thank you for reaching out on this It looks to be cdp key issue. You can confirm using the below If the below output is returning empty results then we might need to regenerate the same and it would be better to raise a support case to further check this as this will need further debugging >> Run the below command and look for cdp_keys.json # kubectl --kubeconfig ocp-kubeconfig.conf -n cdp get secrets/cm.creds -o yaml >> From the above copy the value of cdp_keys.json and pass below # echo "cdp_key.json" | base64 --decode   ... View more

Hello all, Finally found the root cause... /Etc/hosts 192.168.0.10 master1.customerdomain.com # Hostname Master1 This is the discrepancy, setting the hostname to the same as shown in /etc/hosts, the issue was solved. Command used: # hostnamectl set-hostname master1.customerdomain.com Then restarted the agent daemon and services in the cluster. Many thanks to the community for so many clues. ... View more

Hello @steinsgate  Thank you for your update Yes please ensure that the DNS configuration is correct on the nodes. I mean to say that it should adhere to our documentation. Also, try resolving the hostname manually using nslookup from the nodes and compare the output from the working nodes and see if that works ... View more

Hello @steinsgate  In case you want to completely remove the cluster. I would say we can think of the removing the namespace from the Openshift all together and then start fresh ... View more