Virtualization

 View Only
  • 1.  VIO 3.1 can't run CLI tools from OMS

    Posted Apr 13, 2017 12:40 PM

    When running any cli command from the OMS server I receive message:

    Authorization Failed: SSL exception connecting to https://50.0.0.2:5000/v3/tokens: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:509)

    I have soured the rc file both v2 and v3, used both the external and internal url, added all openstack vm's to the nsx exception list and still can't run and of the cli commands without this message. running env | grep "OS_" i see the environment looks good as well.

    Any help would be appreciated.  )



  • 2.  RE: VIO 3.1 can't run CLI tools from OMS

    Posted Apr 14, 2017 12:28 AM

    Have also set pubkeyauthentication to no in sshd_config and reloaded the sshd service

    still same msg



  • 3.  RE: VIO 3.1 can't run CLI tools from OMS

    Broadcom Employee
    Posted Apr 14, 2017 12:55 AM

    Have you tried using CLI with --insecure? You should use internal url on OMS.



  • 4.  RE: VIO 3.1 can't run CLI tools from OMS

    Posted Apr 14, 2017 04:03 PM

    using --insecure give the following output

    viouser@localhost:~/RC files/v3$ keystone --insecure token-get

    Authorization Failed: SSL exception connecting to https://172.20.10.103:5000/v3/tokens: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:590)

    Here is the ENV info as well

    viouser@localhost:~/RC files/v3$ env | grep "OS_"

    OS_PROJECT_ID=835f733971934b348234f33550cbb62d

    OS_REGION_NAME=nova

    OS_USER_DOMAIN_NAME=Default

    OS_PROJECT_NAME=admin

    OS_IDENTITY_API_VERSION=3

    OS_PASSWORD=VMware1!

    OS_AUTH_URL=https://172.20.10.103:5000/v3

    OS_USERNAME=admin

    OS_ENDPOINT_TYPE=internalURL

    OS_INTERFACE=internal

    Note command running cli commands from the OMS



  • 5.  RE: VIO 3.1 can't run CLI tools from OMS

    Broadcom Employee
    Posted Apr 17, 2017 02:13 AM

    I should mention this earlier. Due to the network setup on OMS, you should access Internal VIP with http protocol (then you don't need --insecure flag).

    Try set OS_AUTH_URL=http://172.20.10.103:5000/v3