When a zone is configured under VCS control, each time the zone starts there is an attempt to create a session from the zone to the VCS engine (had) in the global zone. This is so that VCS commands can run OK in the local zone as this functionality is required for some agents.
Details for this session are taken from /.vcspwd in the local zone which caches session details such as an encrypted password. As such if the password in the global zone has changed then this file will be stale. In that case, we will see the following error message:
D229CCC@gbahev147# VCS_HOST=gbahex135
D229CCC@gbahev147# halogin z_z_pp2 vcs123
VCS ERRORV-16-1-53004 halogin can not be run to specify an alternative.
profile for localhost root user
Solution:
- Set the password to a known good value in the global zone "hauser -update"
- Boot the local zone
- Remove the corresponding entry for the user from the /.vcspwd file in the local zone
- SetVCS_HOST=name or IP of global zone where VCS is running (i.e. global zone of the machine where local zone is running)
- Establish a new session with the global zone by running 'halogin username password' in the local zone
This should update the /.vcspwd file and prevent the error. We might need to move the file:/.vcspwd and perform the last two steps once again in case of same issue.