Tasks:
1. Get currently deployment status of pods and deploy.sh
2. Watch or review deploy.sh log
3. Gather a log bundle for VMware support engineer for a vRA cluster.
Task 1: Get Current Deployment Status
Note:
- Assumes the power on in vCenter or LCM as already been performed.
$ ssh root@mwvradev.mindwatering.net
<enter password>
root@mwvradev [ ~]# vracli status
<view result>
root@mwvradev [ ~]# vracli status deploy
<view deployment status - e.g. Deployment not complete (indicating pods are still being started by helm up-scripts>
root@mwvradev [ ~]# kubectl -n prelude get pods
<watch pods go from init to starting to running>
Task 2: Watch the actual deploy.sh log:
Note:
- The -f flag will watch the log being updated rather than just presenting the last few lines at the time of the command being run.
root@mwvradev [ ~]# tail -f /var/log/deploy.log
<watchresult>
Task 3: Gather a log bundle for VMware support:
With no VAMI, we generate by remote SSH into appliance.
1. Create the Log Bundle:
$ ssh root@vraappliance.mindwatering.net
<enter password>
root@vraappliance [ ~ ] vracli log-bundle
<wait for a few minutes, and view name output on last line>
...
The log bundle /home/root/log-bundle-20230101T112323.tar is now available.
2a. Using a file-transfer program, download the file to the local workstation.
2b. Delete the file from the appliance after transfer.
3. Upload to sftpsite.vmware.com, using the SR from the email.
With vRA 7.6:
# vcac-support
(This does a single node.)
# vcac-config log-bundle
(This one does a cluster gather. However, it's broken with the JNI VMware patch, and only returns partial logs. Since 7.6 was near end-of-life, it was "best effort" limited.)
previous page
|