[vRNI] [6.x] UI no longer accessible

Products

• VMware Aria Operations for Networks

Issue/Introduction

This article provides information about the steps to be implemented to fix "UI is no longer accessible" error on the vRNI Platform.

Symptoms:
1. UI is no longer accessible. When logging in, the UI spins forever.


2.  Browser web developer tools shows the state of the API capacity-reconfigure as Running :

Environment

VMware vRealize Network Insight 6.x

Cause

This issue may happen after customers reconfigured the brick size of their appliances.

Resolution

A. Verify the brick size of the the platforms is consistent (size should be the same) across all nodes and reflects what customer configured :
 ubuntu@platform1:~$ ./run_all.sh "sudo cat /home/ubuntu/build-target/deployment/brick-size.info"

If not consistent, please re-adjust based on customer's needs :
** How to change brick size **
https://docs.vmware.com/en/VMware-vRealize-Network-Insight/6.3/com.vmware.vrni.install.doc/GUID-E3D77266-E72E-49AF-B4A6-1810DD10C00F.html#GUID-E3D77266-E72E-49AF-B4A6-1810DD10C00F

** Brick size guidelines **
https://docs.vmware.com/en/VMware-vRealize-Network-Insight/6.3/com.vmware.vrni.install.doc/GUID-F4F34425-C40D-457A-BA65-BDA12B3ABE45.html

** To track history of the brick changes ** 
grep "Old Brick" laun*.log in launcher logs directory
grep "Found brick" laun*.log in launcher logs directory

** Check number of vcpu / memory assigned **
./run_all.sh "nproc --all"
./run_all.sh "free -g"

** check deployment id on all nodes **
./run_all.sh "sudo grep "id:" /etc/vnera/deployment/deployment.def"

Once you confirmed the brick size and deployment id is consistent on all nodes, please go to step B.

B. Delete lock files and change keys in rdb
1. Delete lock files with :
./run_all.sh "sudo rm -f /home/ubuntu/build-target/deployment/reconfigure.lock "

2. Confirm in rdb "DeploymentState" is set as "Running"
 - ubuntu@platform1:~$ rdb
 - arkin> key_val_tool -cid 0 -m get -key DeploymentState
 The get command should output "Running"
If the output is "Running", continue to the steps below, otherwise stop here, and ping @ktrinh on slack.

 - arkin> key_val_tool -cid 0 -m set -key DeploymentState -val "Done"
 - arkin> key_val_tool -cid 0 -m get -key DeploymentState
At this point, the get command should output "Done" and you should be able to access the UI again.