Return
-
Title
VMware agent stops collecting data due to disassociated lockbox/credentials -
Description
VMware agent stops collecting data due to disassociated lockbox/credentials. An entry similar to below is logged in the logs:
INFO [Quartz[0]-9125] com.quest.agent.esx.task.util.VIServiceUtils - Attempting to connect to ConnectionInfo [host=VC_name, urlPath=sdk, port=443, ssl=true], user: null, Trust All Certificates: true
OR
ERROR [Quartz[0]-250393] com.quest.vmware.api.connection.VIService - Null argument passed to login() for parameter: username
-
Cause
missing credentials -
Resolution
Starting with VMware cartridge 5.6.16, user credentials for VMware agent are stored in a Lockbox and that Lockbox should be released to Agent Manager that hosting VMware agent.
To verify that valid user credentials are assigned to VMware agent:
- Navigate to VMware environment dashboard
- Click on Administration tab
- Click in Edit Properties column for the specific VMware agent that is encountering an issue and then validate the accuracy of usr\pwd under Edit Credential Password column
- Edit the username format from username@vsphere.local to vsphere.local\username
- Release Lockbox to Client
- Restart the agent
-
Additional Information
If vCenter is configured to use LDAP authentication for validating usr\pwd then use only the username instead domain\username in the Credentials.