dr_validate script error during Performance Management upgrade

Products

• CA Infrastructure Management
• CA Performance Management
• Network Observability

Issue/Introduction

When running dr_validate.sh script it's asking for dradmin password during DB connection testing and drinstall.properties value test/validation.

We see this from dr_validate.sh on the screen when running it.

Ensuring /etc/rc.local is executable. ...................................[ OK ]
Existing Vertica package discovered - need to perform database connectivity testing.
dradmin@Node0001's password:
Permission denied, please try again.
dradmin@Node0001's password:
Permission denied, please try again.
dradmin@Node0001's password:
Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
Database must be up and running to verify database connection properties in drinstall.properties! [FAIL]
Please start your database via admintools and re-execute this script.

Using the standard full root user install scenario without sudo configurations involved.

Both root and dradmin user are able to SSH from node to node throughout the cluster without being prompted for password.

The dradmin OS user password is valid and is not expired.

Environment

All supported Performance Management releases

Cause

The script has a defect where it is mistakenly attempting to use SSH to switch from root to dradmin user for database connectivity testing.

Resolution

The issue is being addressed through defect DE477938 which will be fixed in a future Performance Management release. No release ETA has been set yet. When one is available this information will be updated to show that ETA.

The issue is benign as long as the values specified in the /opt/CA/IMDataRepository_vertica<version>/drinstall.properties file are correct.

If that is the case, simply hit the Enter key once to complete the dr_validate.sh run. It's last step is the step that is failing, testing the drinstall.properties values for data base connection success. If we know the values are correct, the error can be ignored.

The "Ensuring /etc/rc.local is executable" step is the last change it checks or makes as needed. As long as it, and those that preceded it show OK messages the install can move forward. Some WARN messages in the validate output are acceptable. Only FAIL errors will prevent the install from proceeding.