Cannot connect vCenter 7.0.2 to OpenNebula

Community Support General
1

Hi Experts!

I’m having some trouble connecting a newly installed vCenter instance to a newly installed OpenNebula (vOneCloud)

When clicking on “Hosts” and “+” sign and enter the following info;

Type: vCenter
Hostname: vcenter.domain.local
User: administrator@vsphere.local
Pass: XXXXXX

Clicking “Get cluster” lists my cluster without any issues

Markes the cluster and clicking “Import”

Host created successfully. ID: 1

And then my cluster status is ERROR
Status: error

Information
ID 1
Name HPCluster
Cluster HPCluster
State ERROR
IM MAD vcenter
VM MAD vcenter

vCenter information
VCENTER_CCR_REF domain-c8019
VCENTER_HOST vcenter.domain.local
VCENTER_INSTANCE_ID aa4f6b1c-b0dd-4258-9082-5e88206328b5
VCENTER_PASSWORD JKCqyHsEESWhItq3/O19How==
VCENTER_USER administrator@vsphere.local
VCENTER_VERSION 7.0.2.0

No change if I try to “Offline” & “Enable”

Attributes
ERROR Sun May 2 10:29:30 2021 : Error monitoring Host HPCluster (1): Could not get hosts information - [one.host.info] User couldn’t be authenticated, aborting call.

User & pass is NOT incorrect as I can login to the vCenter without issues with the same user/pass.

From the /var/log/one/oned.log file:
un May 2 10:31:54 2021 [Z0][AuM][D]: _authenticate: -
Sun May 2 10:31:54 2021 [Z0][Lis][I]: Stopping
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:2336 UID:0 IP:127.0.0.1 one.zonepool.info invoked
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:2336 UID:0 one.zonepool.info result SUCCESS, “<ZONE_POOL><ID…”
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:3936 UID:0 IP:127.0.0.1 one.zone.raftstatus invoked
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:3936 UID:0 one.zone.raftstatus result SUCCESS, “<SERVER_ID>-1<…”
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:3232 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:3232 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL></VM_POOL>”
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:960 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:960 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL></VM_POOL>”
Sun May 2 10:31:54 2021 [Z0][AuM][D]: _authenticate: -
Sun May 2 10:31:54 2021 [Z0][Lis][I]: Stopping
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:2128 UID:0 IP:127.0.0.1 one.user.info invoked , 0, false
Sun May 2 10:31:54 2021 [Z0][ReM][D]: Req:2128 UID:0 one.user.info result SUCCESS, “0<GID…”
Sun May 2 10:31:55 2021 [Z0][AuM][D]: _authenticate: -
Sun May 2 10:31:55 2021 [Z0][Lis][I]: Stopping
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:9952 UID:0 IP:127.0.0.1 one.hostpool.info invoked
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:9952 UID:0 one.hostpool.info result SUCCESS, “<HOST_POOL><ID…”
Sun May 2 10:31:55 2021 [Z0][AuM][D]: _authenticate: -
Sun May 2 10:31:55 2021 [Z0][Lis][I]: Stopping
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:7440 UID:0 IP:127.0.0.1 one.user.info invoked , 0, false
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:7440 UID:0 one.user.info result SUCCESS, “0<GID…”
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:3792 UID:1 IP:127.0.0.1 one.documentpool.info invoked , -2, -1, -1, 100
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:3792 UID:1 one.documentpool.info result SUCCESS, “<DOCUMENT_POOL></DOC…”
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:7664 UID:1 IP:127.0.0.1 one.vmpool.monitoring invoked , -2, 0
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:7664 UID:1 one.vmpool.monitoring result SUCCESS, “<MONITORING_DATA></M…”
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:8080 UID:1 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1, “”
Sun May 2 10:31:55 2021 [Z0][ReM][D]: Req:8080 UID:1 one.vmpool.infoextended result SUCCESS, “<VM_POOL></VM_POOL>”
Sun May 2 10:31:57 2021 [Z0][ReM][D]: Req:5456 UID:0 IP:127.0.0.1 one.user.info invoked , 0, false
Sun May 2 10:31:57 2021 [Z0][ReM][D]: Req:5456 UID:0 one.user.info result SUCCESS, “0<GID…”
Sun May 2 10:31:57 2021 [Z0][ReM][D]: Req:8048 UID:0 IP:127.0.0.1 one.host.info invoked , 1, false
Sun May 2 10:31:57 2021 [Z0][ReM][D]: Req:8048 UID:0 one.host.info result SUCCESS, “1<NAM…”
Sun May 2 10:31:58 2021 [Z0][ReM][D]: Req:3616 UID:0 IP:127.0.0.1 one.vmpool.info invoked , -2, 0, -200, -1
Sun May 2 10:31:58 2021 [Z0][ReM][D]: Req:3616 UID:0 one.vmpool.info result SUCCESS, “<VM_POOL></VM_POOL>”
Sun May 2 10:32:00 2021 [Z0][ReM][D]: Req:3072 UID:-1 IP:127.0.0.1 one.host.info invoked , 1, true
Sun May 2 10:32:00 2021 [Z0][ReM][E]: Req:3072 UID:- one.host.info result FAILURE [one.host.info] User couldn’t be authenticated, aborting call.
Sun May 2 10:32:00 2021 [Z0][ReM][D]: Req:6288 UID:0 IP:127.0.0.1 one.host.info invoked , 1, false
Sun May 2 10:32:00 2021 [Z0][ReM][D]: Req:6288 UID:0 one.host.info result SUCCESS, “1<NAM…”
Sun May 2 10:32:00 2021 [Z0][ReM][D]: Req:752 UID:0 IP:127.0.0.1 one.host.status invoked , 1, 0
Sun May 2 10:32:00 2021 [Z0][ReM][D]: Req:752 UID:0 one.host.status result SUCCESS, 1
Sun May 2 10:32:00 2021 [Z0][ReM][D]: Req:448 UID:0 IP:127.0.0.1 one.host.info invoked , 1, false
Sun May 2 10:32:00 2021 [Z0][ReM][D]: Req:448 UID:0 one.host.info result SUCCESS, “1<NAM…”
Sun May 2 10:32:02 2021 [Z0][ReM][D]: Req:64 UID:0 IP:127.0.0.1 one.hostpool.info invoked
Sun May 2 10:32:02 2021 [Z0][ReM][D]: Req:64 UID:0 one.hostpool.info result SUCCESS, “<HOST_POOL><ID…”
Sun May 2 10:32:02 2021 [Z0][ReM][D]: Req:576 UID:0 IP:127.0.0.1 one.user.info invoked , 0, false
Sun May 2 10:32:02 2021 [Z0][ReM][D]: Req:576 UID:0 one.user.info result SUCCESS, “0<GID…”
Sun May 2 10:32:04 2021 [Z0][ReM][D]: Req:2576 UID:0 IP:127.0.0.1 one.user.info invoked , 0, false
Sun May 2 10:32:04 2021 [Z0][ReM][D]: Req:2576 UID:0 one.user.info result SUCCESS, “0<GID…”
Sun May 2 10:32:04 2021 [Z0][ReM][D]: Req:6016 UID:0 IP:127.0.0.1 one.host.info invoked , 1, false
Sun May 2 10:32:04 2021 [Z0][ReM][D]: Req:6016 UID:0 one.host.info result SUCCESS, “1<NAM…”
Sun May 2 10:32:09 2021 [Z0][ReM][D]: Req:4128 UID:0 IP:127.0.0.1 one.zone.raftstatus invoked
Sun May 2 10:32:09 2021 [Z0][ReM][D]: Req:4128 UID:0 one.zone.raftstatus result SUCCESS, “<SERVER_ID>-1<…”
Sun May 2 10:32:09 2021 [Z0][ReM][D]: Req:6592 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Sun May 2 10:32:09 2021 [Z0][ReM][D]: Req:6592 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL></VM_POOL>”
Sun May 2 10:32:09 2021 [Z0][ReM][D]: Req:8240 UID:0 IP:127.0.0.1 one.vmpool.infoextended invoked , -2, -1, -1, -1
Sun May 2 10:32:09 2021 [Z0][ReM][D]: Req:8240 UID:0 one.vmpool.infoextended result SUCCESS, “<VM_POOL></VM_POOL>”
Sun May 2 10:32:10 2021 [Z0][ReM][D]: Req:1904 UID:-1 IP:127.0.0.1 one.host.info invoked , 1, true
Sun May 2 10:32:10 2021 [Z0][ReM][E]: Req:1904 UID:- one.host.info result FAILURE [one.host.info] User couldn’t be authenticated, aborting call.

My versions:
OpenNebula 6.0.0.1 (vmware appliance)
vCenter 7.0 Update2a (7.0.2-17920168)

Any ideas??

2

This indicates an auth error from the vcenter driver to oned. Please check:

Known Issues — OpenNebula 6.0.4 documentation

3

It’s been 5 years and your shit still doesn’t work.

Tue Feb 8 12:08:36 2022 : Error monitoring Host 111 (2): Could not get hosts information - [one.host.info] User couldn’t be authenticated, aborting call.

4

The authorization info that your driver is using is not correct. This can be due to a number of factors:

  • wrong ONE_AUTH variable
  • wrong placement of one_auth
  • the login token problem introduced by FireEdge, that you can solve following my previous link.

I suggest starting from scratch, 5 years dealing with a misconfigured system is probably too much. OpenNebula 6.2 doesn’t feature the FireEdge login token batch, so you’ll be fine in that regard.

Also, please feel free to try out vOneCloud, which is a sandboxed OVA where all the configuration details have been already taken care of.