Cloud Pak for Data

 View Only
  • 1.  ICP4D StandAlone Installation Fails Step 06 (install ICP)

    Posted Thu September 19, 2019 10:10 AM
    Hi,
    I am trying to install ICP4D StandAlone in Linux RHEL 7.5.
    During the installation process on step 06(ICP Install) I get an error stating the following:



    TASK [master : Checking if cluster_vip can work or not] ************************^M
    ^[[0;32mok: [192.168.178.158]^[[0m^M
    ^[[0;31mfatal: [192.168.178.163]: FAILED! => changed=false ^[[0m^M
    ^[[0;31m elapsed: 600^[[0m^M
    ^[[0;31m msg: Seems cluster_vip(192.168.178.21) was not properly set, please correct it and try again.^[[0m^M
    ^[[0;31mfatal: [192.168.178.62]: FAILED! => changed=false ^[[0m^M
    ^[[0;31m elapsed: 600^[[0m^M
    ^[[0;31m msg: Seems cluster_vip(192.168.178.21) was not properly set, please correct it and try again.^[[0m^M
    ^M
    NO MORE HOSTS LEFT *************************************************************^M
    ^M
    PLAY RECAP *********************************************************************^M
    ^[[0;33m192.168.178.158^[[0m : ^[[0;32mok=129 ^[[0m ^[[0;33mchanged=30 ^[[0m unreachable=0 failed=0 ^M
    ^[[0;31m192.168.178.163^[[0m : ^[[0;32mok=136 ^[[0m ^[[0;33mchanged=35 ^[[0m unreachable=0 ^[[0;31mfailed=1 ^[[0m^M
    ^[[0;31m192.168.178.62^[[0m : ^[[0;32mok=128 ^[[0m ^[[0;33mchanged=30 ^[[0m unreachable=0 ^[[0;31mfailed=1 ^[[0m^M
    ^[[0;33mlocalhost^[[0m : ^[[0;32mok=20 ^[[0m ^[[0;33mchanged=6 ^[[0m unreachable=0 failed=0 ^M
    ^M
    Playbook run took 0 days, 0 hours, 17 minutes, 41 seconds^M
    ^M
    2019-09-19 13:15:58 UTC -

    [
    "192.168.178.163",
    "FAILED",
    "InstallICP : Install ICP",
    {
    "_ansible_no_log": false,
    "_ansible_parsed": true,
    "changed": true,
    "cmd": "echo -e \"\\n\\033[1mStarting the ICP Install this will take around 1-2 hours depending on your system.\\033[0m\" > /dev/tcp/localhost/4000 2>&1\n cd /ibm/InstallPackage/ibm-cp-app/cluster\n log_file=$(basename /wdp/InstallPackage/tmp/wdp.2019_09_19__10_26_33.log)\n docker run --net=host -t -e LICENSE=accept -v \"$(pwd)\":/installer/cluster:Z ibmcom/icp-inception-amd64:3.1.2-ee install 2>&1 | tee -a /ibm/InstallPackage/tmp/${log_file} > /dev/tcp/localhost/4000\n exit ${PIPESTATUS[0]}",
    "delta": "0:17:43.941170",
    "end": "2019-09-19 15:15:58.481902",
    "invocation": {
    "module_args": {
    "_raw_params": "echo -e \"\\n\\033[1mStarting the ICP Install this will take around 1-2 hours depending on your system.\\033[0m\" > /dev/tcp/localhost/4000 2>&1\n cd /ibm/InstallPackage/ibm-cp-app/cluster\n log_file=$(basename /wdp/InstallPackage/tmp/wdp.2019_09_19__10_26_33.log)\n docker run --net=host -t -e LICENSE=accept -v \"$(pwd)\":/installer/cluster:Z ibmcom/icp-inception-amd64:3.1.2-ee install 2>&1 | tee -a /ibm/InstallPackage/tmp/${log_file} > /dev/tcp/localhost/4000\n exit ${PIPESTATUS[0]}",
    "_uses_shell": true,
    "argv": null,
    "chdir": null,
    "creates": null,
    "executable": "bash",
    "removes": null,
    "stdin": null,
    "warn": true
    }
    },
    "msg": "non-zero return code",
    "rc": 2,
    "start": "2019-09-19 14:58:14.540732",
    "stderr": "",
    "stderr_lines": [],
    "stdout": "",
    "stdout_lines": []
    }
    ]
    2019-09-19 13:15:58 UTC - Installer is waiting for user input from command line


    I have tried everything so far without success..
    Please help.
    Thanks,
    Ricardo.

    ------------------------------
    Ricardo Corigliano
    ------------------------------

    #CloudPakforDataGroup


  • 2.  RE: ICP4D StandAlone Installation Fails Step 06 (install ICP)

    Posted Fri September 20, 2019 01:50 AM
    Hi Ricardo - it appears your Virtual IP address(es) are not set up properly. Can you confirm that they are available IP addresses and haven't been allocated already?

    ------------------------------
    IMRAN HOSSAIN
    ------------------------------



  • 3.  RE: ICP4D StandAlone Installation Fails Step 06 (install ICP)

    Posted Fri September 20, 2019 06:47 AM
    Hi Imran, thanks for your reply.
    Yes, I have checked the ip. It was not allocated at all. I even tried to change the VIP to other ip just to make sure, yet the issue persists.
    This other run gave the same issue.
    here is the log:

    TASK [master : Checking if cluster_vip can work or not] ************************^M
    ^[[0;32mok: [192.168.178.62]^[[0m^M
    ^[[0;31mfatal: [192.168.178.163]: FAILED! => changed=false ^[[0m^M
    ^[[0;31m elapsed: 600^[[0m^M
    ^[[0;31m msg: Seems cluster_vip(192.168.178.1) was not properly set, please correct it and try again.^[[0m^M
    ^[[0;31mfatal: [192.168.178.158]: FAILED! => changed=false ^[[0m^M
    ^[[0;31m elapsed: 600^[[0m^M
    ^[[0;31m msg: Seems cluster_vip(192.168.178.1) was not properly set, please correct it and try again.^[[0m^M
    ^M
    NO MORE HOSTS LEFT *************************************************************^M
    ^M
    PLAY RECAP *********************************************************************^M
    ^[[0;31m192.168.178.158^[[0m : ^[[0;32mok=151 ^[[0m ^[[0;33mchanged=90 ^[[0m unreachable=0 ^[[0;31mfailed=1 ^[[0m^M
    ^[[0;31m192.168.178.163^[[0m : ^[[0;32mok=156 ^[[0m ^[[0;33mchanged=93 ^[[0m unreachable=0 ^[[0;31mfailed=1 ^[[0m^M
    ^[[0;33m192.168.178.62^[[0m : ^[[0;32mok=152 ^[[0m ^[[0;33mchanged=90 ^[[0m unreachable=0 failed=0 ^M
    ^[[0;33mlocalhost^[[0m : ^[[0;32mok=20 ^[[0m ^[[0;33mchanged=15 ^[[0m unreachable=0 failed=0 ^M
    ^M
    Playbook run took 0 days, 1 hours, 17 minutes, 14 seconds^M
    ^M
    2019-09-20 10:20:17 UTC -


    [
    "192.168.178.163",
    "FAILED",
    "InstallICP : Install ICP",
    {
    "_ansible_no_log": false,
    "_ansible_parsed": true,
    "changed": true,
    "cmd": "echo -e \"\\n\\033[1mStarting the ICP Install this will take around 1-2 hours depending on your system.\\033[0m\" > /dev/tcp/localhost/4000 2>&1\n cd /ibm/InstallPackage/ibm-cp-app/cluster\n log_file=$(basename /wdp/InstallPackage/tmp/wdp.2019_09_20__09_53_48.log)\n docker run --net=host -t -e LICENSE=accept -v \"$(pwd)\":/installer/cluster:Z ibmcom/icp-inception-amd64:3.1.2-ee install 2>&1 | tee -a /ibm/InstallPackage/tmp/${log_file} > /dev/tcp/localhost/4000\n exit ${PIPESTATUS[0]}",
    "delta": "1:17:20.908723",
    "end": "2019-09-20 12:20:17.760795",
    "invocation": {
    "module_args": {
    "_raw_params": "echo -e \"\\n\\033[1mStarting the ICP Install this will take around 1-2 hours depending on your system.\\033[0m\" > /dev/tcp/localhost/4000 2>&1\n cd /ibm/InstallPackage/ibm-cp-app/cluster\n log_file=$(basename /wdp/InstallPackage/tmp/wdp.2019_09_20__09_53_48.log)\n docker run --net=host -t -e LICENSE=accept -v \"$(pwd)\":/installer/cluster:Z ibmcom/icp-inception-amd64:3.1.2-ee install 2>&1 | tee -a /ibm/InstallPackage/tmp/${log_file} > /dev/tcp/localhost/4000\n exit ${PIPESTATUS[0]}",
    "_uses_shell": true,
    "argv": null,
    "chdir": null,
    "creates": null,
    "executable": "bash",
    "removes": null,
    "stdin": null,
    "warn": true
    }
    },
    "msg": "non-zero return code",
    "rc": 2,
    "start": "2019-09-20 11:02:56.852072",
    "stderr": "",
    "stderr_lines": [],
    "stdout": "",
    "stdout_lines": []
    }
    ]

    ------------------------------
    Ricardo Corigliano
    ------------------------------



  • 4.  RE: ICP4D StandAlone Installation Fails Step 06 (install ICP)

    Posted Mon September 23, 2019 09:54 AM
    Issue solved after changing the overlay_network address. It seems that the default was conflicting with another network the cluster was connecting.

    ------------------------------
    Ricardo Corigliano
    ------------------------------