Could you check this and confirm there is no permission issue:
If this doesnt fix the problem then logs should show us why vcenter stooped collection and what happened to custom groups.
Could you confirm one thing: after upgrading to 6.7 did you happen to see custom groups working good ?
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
Did you run the upgrade Assessment Tool before the upgrade? It will help you to define your upgrade readiness and will evaluate and mitigate the impact of your custom content in previous versions.
Also check the configuration of the vCenter Adapter Instance itself and the configured credentials for making connection to vCenter. Perform a test connection of the adapter as well.
yes ... after upgradation to v6.7 my environment was running fine for around 1 month. All of the sudden this issue happened. Its not the roles and the permissions issue because earlier I was able to see all my custom groups with the same credentials( same roles and permissions).
yes RickVerstegen, I have had run the pre-upgrade assessment tool and worked accordingly. My environment was behaving perfectly fine before this issue.
Also, I have checked the configuration of the vCenter Adapter Instances and the configured credentials for making connection to vCenter. Performed a test connection of the adapter as well. But unfortunately nothing worked yet...:(
There are chances that if custom groups are created with a respective account and if that account is deleted , respective custom groups also gets deleted.
You can test one thing. create custom groups now and try to log off and log in back and check .
Also check with some specific test user and delete it post creation of custom group .
No the account is still in use. Rest everything with this account is working fine.
I have created some new custom groups in order to test it and then logged it out. When i logged in back all custom groups were there. And i have tried it with the new user created for test as well.