Hi all,
Trying to install SMAX 2019.05, using the Walkthrough: Set up an on-premises demo environment guide.
The error I'm having is still while deploying CDF. All the pre-requisites seem to be in place, however I'm getting the following error:
2019-06-25T15:40:37 01:00 INFO : Wait for the cdf-apiserver ready...
[ FAILED ]
2019-06-25T15:56:32 01:00 FATAL : A timeout occurred while waiting for the cdf-apiserver to start. Refer to /tmp/install.20190625153034.log file for detail information. If need, please contact system administrator or Micro Focus support.
On the /tmp/install.20190625153034.log file:
2019-06-25T15:56:27.562880371 01:00 DEBUG cdf-apiserver is not running. Wait for 180 seconds and recheck: 179
2019-06-25T15:56:32.57316943 01:00 DEBUG exec_cmd # kubectl get svc suite-installer-svc -n core -o custom-columns=:.spec.clusterIP --no-headers 2>/dev/null
2019-06-25T15:56:32.57316943 01:00 DEBUG exit_code: 1
2019-06-25T15:56:32.796913235 01:00 DEBUG exec_cmd # curl --noproxy http://:8080/urest/v1.1/healthz
2019-06-25T15:56:32.796913235 01:00 DEBUG exec_msg :
curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information
2019-06-25T15:56:32.796913235 01:00 DEBUG exit_code: 2
2019-06-25T15:56:32.819105198 01:00 FATAL A timeout occurred while waiting for the cdf-apiserver to start. Refer to /tmp/install.20190625153034.log file for detail information. If need, please contact system administrator or Micro Focus support.
If I try to manually run the command:
# kubectl get svc suite-installer-svc -n core -o custom-columns=:.spec.clusterIP --no-headers
Error from server (NotFound): services "suite-installer-svc" not found
And running:
# kubectl get po --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
core itom-cdf-deployer-9jrp2 1/1 Running 0 13m
core itom-cdf-deployer-jnxxs 0/1 Error 0 148m
core itom-vault-8c747bfcc-rpflm 0/1 CrashLoopBackOff 41 148m
kube-system apiserver-smax.wmpromus.com 1/1 Running 1 148m
kube-system controller-smax.wmpromus.com 1/1 Running 2 149m
kube-system coredns-9jwrf 1/1 Running 1 148m
kube-system etcd-smax.wmpromus.com 1/1 Running 1 148m
kube-system kube-flannel-ds-amd64-b29cv 1/1 Running 1 149m
kube-system scheduler-smax.wmpromus.com 1/1 Running 1 149m
When checking the pod logs:
# kubectl logs -n core itom-vault-8c747bfcc-rpflm | less
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Trying to create a RIC root certs and key if not present...
Cannot find ca.key in local path /ssl/. Try to find it in the k8s secret ric-root-cert.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
^M 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0^M100 7181 0 7181 0 0 77113 0 --:--:-- --:--:-- --:--:-- 78054
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
^M 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0^M100 7181 0 7181 0 0 112k 0 --:--:-- --:--:-- --:--:-- 114k
Found ca.key in the k8s secret ric-root-cert. Saving ca.key & ca.crt from the k8s secret ric-root-cert into local path /ssl/
No existing server.key or server.crt in local path /ssl/. Generate a new server.key & a new server.crt
Generating RSA private key, 4096 bit long modulus
.....................................
.......................................................
e is 65537 (0x10001)
Signature ok
subject=/CN=itom
Getting CA Private Key
http_code:000: unknown error
try to start server
http_code:000: unknown error
Anyone came across this issue, or have any idea about debugging/fixing this error?
Thanks,
J.