Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Highlighted
Outstanding Contributor.. Mayur_Khardikar Outstanding Contributor..
Outstanding Contributor..
110 views

OBM cdf-apiserver not starting

Hello,

We've implemented OBM CDF 2018.11 with three master and worker nodes. The cdf-apiserver pod is in CrashLoopBackOff state on all the servers. Below error is observered in the container logs

Warning Unhealthy 7m (x71 over 22m) kubelet, <FQDN> Readiness probe failed: Get http://172.16.41.12:8080/urest/v1.1/healthz: dial tcp 172.16.41.12:8080: connect: connection refused
Warning BackOff 2m (x46 over 19m) kubelet, <FQDN> Back-off restarting failed container

The 'vault status' command results in below error:

Error checking seal status: Get https://127.0.0.1:8200/v1/sys/seal-status: x509: certificate is valid for 172.17.17.1, 10.5.4.140, 10.5.4.141, not 127.0.0.1

I suspect this could be the root cause for cdf-apiserver pod to be in CrashLoopBackOff state. I'd like to hear from the experts!

Thanks in advance!

Mayur

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.