First, did you seriously take a picture of your screen with a camera? And you work for a software company? :smileylaugh:
You may need to check your system. Are all services registered? Data should definitely not be empty.
I am sure all services are registered correctly? It seems be healthy besides event subscription. Thanks a lot!
You'll need to share more information in that case.
I am also having the same issue, its fresh build and see all the services are showing up registered. Has anybody else encountered same issue ? and any resolution around this? Until vRA 7.3 it was seamless, did not had any problem getting this working.
Any help is much appreciated.
Note: attached screenshot
Reboot your appliance first and see if that clears it up.
We are having the same issue on both instances of our vRA 7.4 fresh installs. We have rebooted many times. We have also posted this issue on slack thinking it was a simple fix, but soon realized its a bigger issue with others as well. Supposedly there is a fix out there (by what I'm told on slack), but no one can provide a KB or link. We are working with our TAM to find it....hopefully soon...
If anyone has a link or how-article to resolve this issue, please share.
Thanks
This seems to be situational because I have done a couple deployments now with the schema loading perfectly fine. One thing to check is your appliance deployment settings to ensure you're using a FQDN and not short name (or, worse, IP).
Both of ours are using FQDN. One of them is on an internet connected domain, while the other is on a disconnected domain; same issue.
However I did get an message from @senk on slack just now: "a fix for the event broker subscription is out and KB article is in preparation. if it's urgent you should reference SR#18783186804 with GSS to get the details".
We will be doing this shortly. Hopefully this helps use and anyone else with this issue.
Good Luck
Can you post that KB article here as a response when it's published, please? That would help others out who come across the same issue.
Not sure if anyone else was able to get the solution but this is what VMware sent me for the same issue.