Highlighted
Super Contributor.. Madddy Super Contributor..
Super Contributor..
491 views

Suite installation is getting Failed

Jump to solution

Hi Team,

we are using mixed mode SMA-SM Service Portal (SMA-SM SP) suite, where Service Portal and Smart Analtics on CDF. I am posting my issue here because I could not see any CDF/Sute deployment post in the SMA-SM community, please let me know if I have to post it their.
Version:Service Manager 9.52

We are using 1 master ,2 worker,External DB & NFS server for our development, we had installed 2018.02 version and decided to unisntall and reinstall with 2018.08.

We have followed all the instruction as per the document by clearing the DB and Username, Also validated all the prerequsites too but our deployment is failing at IDM.

 

[root@bt-vld-itsma-01 tmp]# systemctl status kubelet
● kubelet.service - Kubernetes Kubelet
Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-12-30 15:44:07 AST; 19h ago
Docs: https://github.com/GoogleCloudPlatform/kubernetes
Main PID: 8451 (kubelet)
CGroup: /system.slice/kubelet.service
‣ 8451 /usr/bin/kubelet --authentication-token-webhook --read-only-port=0 --anonymous-auth=false --client-ca-file=/opt/kubernetes/ssl/ca.crt --cluster-dns=172.17.17.78 --clust...

Dec 31 07:47:44 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 07:47:44.379865 8451 remote_runtime.go:278] ContainerStatus "552854488dbd97425d3089b08128b23027e21a8cf57...533bedd80e
Dec 31 07:47:44 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 07:47:44.379896 8451 kuberuntime_container.go:420] ContainerStatus for 552854488dbd97425d3089b08128b2302...533bedd80e
Dec 31 07:47:44 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 07:47:44.379906 8451 kuberuntime_manager.go:874] getPodContainerStatuses for pod "idm-8d9f8db54-5vrll_co...533bedd80e
Dec 31 07:47:44 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 07:47:44.379929 8451 generic.go:241] PLEG: Ignoring events for pod idm-8d9f8db54-5vrll/core: rpc error: ...533bedd80e
Dec 31 07:47:44 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 07:47:44.380011 8451 pod_workers.go:186] Error syncing pod 7cbaaf5b-0c3c-11e9-a3eb-005056b26389 ("idm-8d9f8db54-5v...
Dec 31 09:39:24 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 09:39:24.428024 8451 remote_runtime.go:278] ContainerStatus "08ff72ea8b1dc411dff7418540a0fb1149fe0c30e10...ac8c8b7744
Dec 31 09:39:24 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 09:39:24.429133 8451 kuberuntime_container.go:420] ContainerStatus for 08ff72ea8b1dc411dff7418540a0fb114...ac8c8b7744
Dec 31 09:39:24 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 09:39:24.429153 8451 kuberuntime_manager.go:874] getPodContainerStatuses for pod "idm-8d9f8db54-5vrll_co...ac8c8b7744
Dec 31 09:39:24 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 09:39:24.429193 8451 generic.go:241] PLEG: Ignoring events for pod idm-8d9f8db54-5vrll/core: rpc error: ...ac8c8b7744
Dec 31 09:39:24 bt-vld-itsma-01.qatar2022.local kubelet[8451]: E1231 09:39:24.429241 8451 pod_workers.go:186] Error syncing pod 7cbaaf5b-0c3c-11e9-a3eb-005056b26389 ("idm-8d9f8db54-5v...
Hint: Some lines were ellipsized, use -l to show in full.

0 Likes
1 Solution

Accepted Solutions
Super Contributor.. Madddy Super Contributor..
Super Contributor..

Re: Suite installation is getting Failed

Jump to solution

Hi All,

Issue is resolved.

Solution: we uninstalled and re-installed by celaring the Database  and users.

Regards,

Madhan

3 Replies
Super Contributor.. Levent Super Contributor..
Super Contributor..

Re: Suite installation is getting Failed

Jump to solution

Hi,

 

you can check on all hosts :

#systemctl status rpcbind

if inactive

#systemctl start rpcbind

 

 

0 Likes
Misaq Acclaimed Contributor.
Acclaimed Contributor.

Re: Suite installation is getting Failed

Jump to solution
0 Likes
Super Contributor.. Madddy Super Contributor..
Super Contributor..

Re: Suite installation is getting Failed

Jump to solution

Hi All,

Issue is resolved.

Solution: we uninstalled and re-installed by celaring the Database  and users.

Regards,

Madhan

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.