[OpenNESS-dev] FW: Installing OpenNess Controller..

Ravindran, Ravi (Ravishankar) RavindraR2 at corning.com
Tue Mar 2 09:17:55 PST 2021


Hope someone can get back..

--

    I was able to resolve the issue below, the problem was with the system clock. But now stuck at installing the Harbour registry, this is the current state, tge kube-prox seems to be running at 127.0.0.1:30003, but don’t see the harbor.crt, any tips on what the reason could be ?, and how to test if the controller is fully up, once installed ?

    TASK [harbor_registry/node : get ca.crt from registry] *************************************************************************************************************************
    task path: /home/ravi/OpenNess/openness-experience-kits-master/roles/harbor_registry/node/tasks/main.yml:15
    FAILED - RETRYING: get ca.crt from registry (10 retries left).
    FAILED - RETRYING: get ca.crt from registry (9 retries left).
    FAILED - RETRYING: get ca.crt from registry (8 retries left).
    FAILED - RETRYING: get ca.crt from registry (7 retries left).
    FAILED - RETRYING: get ca.crt from registry (6 retries left).
    FAILED - RETRYING: get ca.crt from registry (5 retries left).
    FAILED - RETRYING: get ca.crt from registry (4 retries left).
    FAILED - RETRYING: get ca.crt from registry (3 retries left).
    FAILED - RETRYING: get ca.crt from registry (2 retries left).
    FAILED - RETRYING: get ca.crt from registry (1 retries left).
    fatal: [controller]: FAILED! => {
        "attempts": 10, 
        "changed": false, 
        "dest": "/etc/docker/certs.d/127.0.0.1:30003/harbor.crt", 
        "elapsed": 10, 
        "url": "https://127.0.0.1:30003/api/v2.0/systeminfo/getcert"
    }

    MSG:

    Request failed: <urlopen error timed out>

    PLAY RECAP *********************************************************************************************************************************************************************
    controller                 : ok=153  changed=29   unreachable=0    failed=1    skipped=195  rescued=0    ignored=1   


    Regards,
    Ravi


    On 2/26/21, 5:28 PM, "Ravindran, Ravi (Ravishankar)" <RavindraR2 at corning.com> wrote:

        Hi,

        I recently got access to the OpenNess git repo, and trying to install the K8S controller using the deploy_ne.sh script. 

        Running into issues with this particular rpm: 
        Installing the following packages: git2u-all,jq,vim-common,curl,yum-utils,python2-pip,python3,wget,bridge-utils,rsync,device-mapper-persistent-data,lvm2,moreutils,gcc,python-devel,createrepo,psmisc,bash-completion,patch

        TASK [machine_setup/os_setup : install IUS repository] *************************************************************************************************************************
        task path: /home/ravi/OpenNess/openness-experience-kits-master/roles/machine_setup/os_setup/tasks/install_base_os_packages.yml:8
        Error occurred. Will retry after 5 seconds. You can find details below:
        Failure downloading https://repo.ius.io/ius-release-el7.rpm, Request failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)>

        Looks like the server end certificate is outdated or has some issues...is this something known, how do I disable certificate check in the ansible script ?

        Regards,
        Ravi





More information about the Developer mailing list