Discovery of vCenter fails

[klautrup]

Hi,
We are doing POC of Discovery and when trying to do a vCenter discovery it only manages to create the vCenter CI:

Hovering the cursor over 'Details' under 'Issues' says "No credentials found for types SSH Password, SSH Private...".

And under the Discovery Log tab we see a more than 7.000 warnings saying "Controller is empty for FC Port....":

So similar warnings as described in this other community thread (no solution):
https://community.servicenow.com/community?id=community_question&sys_id=60aeba65db58dbc01dcaf3231f961977&view_source=searchResult

We are running Jakarta Patch 8B, but I get the same result in my developer instance running Kingston patch 4.

We have created the VMware credentials using vCenter read-only credentials ('Test credential' is successful).

Regards,
Kristian

[Michael Skov2]

For the "Controller is empty for FC Port", try to disable the MID server script include named VMWarevCenterESXHostsStorageProbe and see if that helps on that part. 

For the permissions, are you using a domain account? If so, is the account entered as "user@domain.com"?

[klautrup]

Hi Michael,
If I disable that script include I get these warnings:

And still Discovery only manages to create the vCenter CI with the 'Details' complaining about SSH:

I think the VMware credentials uses port 443 (ssl) so I don't understand why it is complaining about SSH.

For the permissions we are using a local account on the vCenter server, so we have added the credentials like this:

Doing 'Test credential' it is successful connecting:

[Michael Skov2]

I suspect that it is using the wrong credentials. A couple of things:

1. Do you have multiple MID servers?

2. Check out the agent log on the MID server to see what happens and which credentials are used - it might be necessary to enable debug (parameter: mid.log.level, value: debug)

3. Can you log in to vsphere with the account?

[klautrup]

No only one MID server.

I tried disabling all other credentials to be sure it uses the vCenter credentials.
Yes we can log into vCenter using those credentials.

I enabled debug loggin on the MID server.
Looking at the agent.log (attached here) I don't see any errors and it tries to run the VMware probes.