VECO - VCO - DR synch failing for FIPS enabled VCO - 5.2.3.6

Products

• VMware Edge Cloud Orchestrator

Issue/Introduction

 DR synch failing for FIPS enabled VCO/VECO that is on 5.2.3.6

Environment

VECO that is on 5.2.3.6 and that is FIPS enabled 

Cause

There is a bug in the FIPS mode VCO where certain password with special characters were not being read correctly. This led to some services to not initialize properly and cause downstream replication issues that expected the initialization to have completed. Provided below is the workaround that must be applied through the Bash on both primary and secondary VCOs. This defect is tracked through #151844. 

 

Resolution

This issue is fixed on 5.2.3.7, provided below is the workaround 

 

Perform steps 1-4 on both active and standby VCOs

Step 1. To fix missing dbs: `sed -i 's/\"//g' /etc/*.env`
Step 2. systemctl restart cws-service search-service ztnad-service
Step 3. wait 2  - 5 minutes for the services to re-establish:

 

Step 4. create password and update password value on both vcreplication.cnf and replication_mysql_conf.yml

-- command to be used on CLI to provide the password, the password that is generated on the VCO is what will be used to update the password parameters mentioned below

perl -e 'print map{("a".."z","A".."Z",0..9)[int(rand(62))]}(1..16)' && printf "\n"

--use a text editor to update password value within the following files 

/etc/mysql/vcreplication.cnf

/etc/replication_mysql_conf.yml

--enter mysql and update password with the same password as well

mysql --defaults-extra-file=/etc/mysql/velocloud.cnf 

use velocloud;

 

-- use exchange password displayed below with the password generated from the perl command

ALTER USER 'vcreplication'@'localhost' identified WITH mysql_native_password BY 'password';

-- restart mysql service on both active and secondary VCOs

systemctl restart mysql

5. restart DR and attempt to establish DR once more