Cloud Pak for Data

Cloud Pak for Data

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  ICP Installation Fails

    Posted Tue September 17, 2019 09:04 AM
    Hi,

    I'm trying to install ibm-cloud-private-3.2.0 on ubuntu machine with below specifications.

    Architecture: x86_64
    CPU op-mode(s): 32-bit, 64-bit
    Byte Order: Little Endian
    CPU(s): 4
    On-line CPU(s) list: 0-3
    Thread(s) per core: 2
    Core(s) per socket: 2
    Socket(s): 1
    NUMA node(s): 1
    Vendor ID: GenuineIntel
    CPU family: 6
    Model: 58
    Model name: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
    Stepping: 9
    CPU MHz: 1893.299
    CPU max MHz: 3300.0000
    CPU min MHz: 1200.0000
    BogoMIPS: 5188.09
    Virtualization: VT-x
    L1d cache: 32K
    L1i cache: 32K
    L2 cache: 256K
    L3 cache: 3072K
    NUMA node0 CPU(s): 0-3

    Getting below error while installing.

    FAILED - RETRYING: Waiting for MongoDB to start (1 retries left).
    Result was: changed=true
    attempts: 100
    cmd: kubectl -n kube-system get statefulset icp-mongodb -o=custom-columns=A:.status.readyReplicas,B:.status.replicas --no-headers=true | tr -s " " | awk '$1 == $2 {print "READY"}'
    delta: '0:00:03.919999'
    end: '2019-09-17 10:42:59.524845'
    rc: 0
    retries: 101
    start: '2019-09-17 10:42:55.604846'
    stderr: ''
    stderr_lines: <omitted>
    stdout: ''
    stdout_lines: <omitted>
    fatal: [localhost]: FAILED! => changed=true
    attempts: 100
    cmd: kubectl -n kube-system get statefulset icp-mongodb -o=custom-columns=A:.status.readyReplicas,B:.status.replicas --no-headers=true | tr -s " " | awk '$1 == $2 {print "READY"}'
    delta: '0:00:00.464318'
    end: '2019-09-17 10:44:00.205078'
    rc: 0
    start: '2019-09-17 10:43:59.740760'
    stderr: ''
    stderr_lines: <omitted>
    stdout: ''
    stdout_lines: <omitted>

    PLAY RECAP *********************************************************************
    192.168.97.31 : ok=141 changed=43 unreachable=0 failed=0
    localhost : ok=189 changed=66 unreachable=0 failed=1

    Would be better if anyone could suggest resolution for this.

    Thanks in advance!

    ------------------------------
    SUJADEVI R
    ------------------------------

    #CloudPakforDataGroup


  • 2.  RE: ICP Installation Fails

    Posted Tue September 17, 2019 09:55 AM

    Hi,

    Are you trying to deploy it to run Cloud Pak for Data ?
    Ubuntu is currently not supported (Docker issues), and you need at least 3 nodes for the setup.

    Anyhow, you can start the investigation by doing:

    kubectl -n kube-system get statefulset icp-mongodb

    check how many pods have started, then look at individual pods

    kubectl -n kube-system get po | grep icp-mongo

    and describe their status.

    Thanks



    ------------------------------
    TOMASZ HANUSIAK
    ------------------------------

    Original Message


  • 3.  RE: ICP Installation Fails

    Posted Wed September 18, 2019 07:57 AM
    Edited by System Admin Fri January 20, 2023 04:13 PM
    Hi,

    Thank you.

    I'm able to install ICP for integration now. I used single node for setup. But after installation when I try to open url https://xxx.xxx.xx.xx:8443 its opening a blank page.

    Below are the pod status:
    root@ubuntu:/opt/ibm-cloud-private-3.2.0/cluster# kubectl get pods -n kube-system
    NAME READY STATUS RESTARTS AGE
    auth-idp-mb6ph 4/4 Running 4 3h22m
    auth-pap-kw2kp 2/2 Running 1 3h22m
    auth-pdp-5mj6d 2/2 Running 0 3h22m
    calico-kube-controllers-6f775b85dd-nx78l 1/1 Running 0 3h26m
    calico-node-rs7lv 1/1 Running 0 3h26m
    catalog-ui-bw7v9 0/1 Pending 0 3h18m
    default-http-backend-5657949d5b-sj79m 1/1 Running 0 3h25m
    helm-api-5c76458dc5-jvcjr 3/3 Running 0 3h18m
    helm-repo-84fdfc6667-x7dqm 2/2 Running 0 3h21m
    iam-onboarding-dcvq6 0/1 Completed 0 3h17m
    ibmcloud-image-enforcement-69b698f647-44cw5 1/1 Running 0 3h20m
    icp-management-ingress-29fhn 1/1 Running 0 3h22m
    icp-mongodb-0 2/2 Running 0 3h25m
    image-manager-0 2/2 Running 0 3h26m
    image-manager-init-certs-5lc9s 1/1 Running 0 3h26m
    k8s-etcd-192.168.97.31 1/1 Running 0 3h28m
    k8s-kmsplugin-192.168.97.31 1/1 Running 0 3h27m
    k8s-master-192.168.97.31 3/3 Running 3 3h28m
    k8s-proxy-rhfpk 1/1 Running 0 3h27m
    key-management-api-5dfdcbc894-t9mhq 0/1 Pending 0 3h17m
    key-management-crypto-9f564cdc4-dnf75 0/1 Pending 0 3h17m
    key-management-lifecycle-675c578599-fn5cd 2/2 Running 0 3h17m
    key-management-onboarding-xztg6 0/1 Pending 0 3h17m
    key-management-pep-6687fb5dd7-7fhqs 0/1 Pending 0 3h17m
    key-management-persistence-5b4b54c9c-6c8xt 0/1 Pending 0 3h17m
    kube-dns-67j2t 1/1 Running 0 3h25m
    metering-dm-6d9f76d9c5-4t498 1/1 Running 0 3h19m
    metering-reader-h296x 1/1 Running 0 3h19m
    metering-ui-6d698cf77f-q8fml 1/1 Running 0 3h19m
    metrics-server-9746d99b8-46qtw 1/1 Running 0 3h24m
    mgmt-repo-67c8fd95b8-ngnvv 0/2 Pending 0 3h17m
    monitoring-grafana-b87c64bc4-9brnj 3/3 Running 0 3h19m
    monitoring-prometheus-7f9c7bf9c4-7jkvw 4/4 Running 0 3h19m
    monitoring-prometheus-alertmanager-6858d6cb5-98hsj 3/3 Running 0 3h19m
    monitoring-prometheus-collectdexporter-7d99698c97-z4snr 2/2 Running 0 3h19m
    monitoring-prometheus-elasticsearchexporter-7c9646f8f6-77h8b 2/2 Running 0 3h19m
    monitoring-prometheus-kubestatemetrics-77c9687b4-6f8ht 2/2 Running 0 3h19m
    monitoring-prometheus-nodeexporter-88pln 2/2 Running 0 3h19m
    multicluster-hub-console-mcmui-6f68847594-mdttf 0/1 Pending 0 3h17m
    multicluster-hub-console-mcmuiapi-5fcb46cb4f-kpgq6 1/1 Running 0 3h17m
    multicluster-hub-console-mcmuiapi-7bf578498d-ll8t2 0/1 Pending 0 3h17m
    multicluster-hub-ibm-mcm-prod-create-redis-secret-n5rmw 0/1 Completed 0 3h17m
    multicluster-hub-search-redisgraph-6964c6647f-x58n5 0/1 Pending 0 3h17m
    multicluster-hub-search-redisgraph-855f955684-xdh8p 0/1 Pending 0 3h17m
    multicluster-hub-search-search-aggregator-5756ff87c5-hvvf5 0/1 Pending 0 3h17m
    multicluster-hub-search-search-aggregator-fcfb97f8-7bwjl 0/1 Pending 0 3h17m
    multicluster-hub-search-search-collector-57585f98-zctct 0/1 Pending 0 3h17m
    multicluster-hub-search-search-collector-7b9d87b65f-bz5zt 0/1 Pending 0 3h17m
    nginx-ingress-controller-xtk96 1/1 Running 0 3h25m
    nvidia-device-plugin-2jc69 1/1 Running 0 3h25m
    oidc-client-registration-qgrq8 0/1 Completed 0 3h22m
    platform-api-568f8f55f4-wbcb2 2/2 Running 0 3h24m
    platform-header-xgshk 0/1 Pending 0 3h17m
    platform-ui-mqljf 0/1 Pending 0 3h17m
    secret-watcher-7cbc4b585d-r8h6j 1/1 Running 0 3h17m
    security-onboarding-2lrh7 0/1 Completed 0 3h17m
    service-catalog-apiserver-gw8tn 1/1 Running 0 3h25m
    service-catalog-controller-manager-5d95957df9-4pplj 1/1 Running 0 3h25m
    tiller-deploy-6b998d6844-xdnmv 1/1 Running 0 3h28m
    web-terminal-67c87777d5-5pjr4 1/1 Running 0 3h20m

    Any idea why page is not loading properly?

    Thanks


    ------------------------------
    SUJADEVI R
    ------------------------------

    Original Message


  • 4.  RE: ICP Installation Fails

    Posted Wed September 18, 2019 08:36 AM
    Hi,

    As mentioned before, this is not the right place to ask questions about single-node ICP installations, but let me suggest something:

    A lot of the pods are still Pending (most likely waiting for some resource), please describe the pods, and check what is the reason for Pending.

    Thanks

    ------------------------------
    TOMASZ HANUSIAK
    ------------------------------

    Original Message


Related Content