Data Infrastructure Insights VMware collectors not polling vCenters...Test connection is almost OK.

[hollow ibex]

Hi all,

I discovered by myself this morning in Data Infrastructure Insights (no alerts have been configured yet...) that our VMware vSphere collectors were not polling our vCenters anymore.
The origin of the error was pretty clear: " Failed to instantiate a connection to VirtualCenter at xxx.xxx.xxx.xxx ", " Failed to login to server at xxx.xxx.xxx.xxx " & " Invalid login credentials ".
---> As a test, it was not possible to log on to vCenters with credentials configured in VMware vSphere collectors.
---> Password of the account used by VMware vSphere collectors configuration has expired.
---> A reset of the password and following this procedure (https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.authentication.doc/GUID-4FBEA58E-9492-409B-B584-C18477F041D8.html) did the trick, quite simple.

However, when the password was expired, I tested the connection from the collector to the vCenter, it was partially successful, it is a bit confusing as you can see in the attached screenshot:
What connection (to what) is successful and what connection is not ?

By the way, does Data Infrastructure Insights threads would not deserve their own " channel " in Discord such as other NetApp products, instead of being part of BlueXP ?

Thanks in advance.
Regards.

[latent rampart]

Could you trigger an error report for this collector so we can look into this?

Basically, we think there might be a loophole in the test code that doesn't account for new features that were recently added. Something like (as a guess), we might be thinking the logs are ok and aren't actually testing the REST API login for logs.

let me know when it was sent, and if possible, the collector name.

[hollow ibex]

Hello,

Thank you for your feedback.
The only way I found to trigger an error report is by clicking on the " Send Error Report " button in the collector configuration page, see below the screenshot, is it what you are looking for ?

If I click on that button, I got the following warning so I guess it was useless to send that error report, am I right ?

Anyway, I sent the report around half an hour ago ( =~ 03:15 PM CET).
I will send you the collector name in another message.

Regards.

[latent rampart]

That's it, thanks. We do try to look at them but without a case there's no guarantee someone will have the cycles.

[hollow ibex]

OK I understand ... Thank you in advance for any help provided.

[latent rampart]

I have a bug submitted to engineering for this issue. You can keep a record of the number, but it's not available publicly. ICI-15472

[latent rampart]

@hollow ibex I don't have the full answer here, but engineering did find some things to fix for the test and this issue should be fixed the next time we update the collectors.
If you need it fixed sooner, let me know and I can have them patch it for you.

[hollow ibex]

Good morning,

Thanks for the feedback and investigations.
I can wait for sure, I guess collectors are updated on a regular basis ?