20
Apr, 2020
20
Apr, 2020
The VMware Cloud Director appliance deployment fails when you enable the setting to expire the root password upon the first login
Cloud, VMware Cloud, vCloud DirectorAs I have been trying to deploy the vCloud Director 10.1 in my home lab, I have faced the below errors, and I wanted to share with others the resolution in case you are facing it and have missed it in the release notes.
“No nodes found in cluster, this likely means PostgreSQL is not running on this node. Consult the management UI from another node where PostgreSQL is running. Otherwise, check /opt/vmware/var/log/vcd/vcd_ova_ui_app.log if you think this is an error.”
The following error in the /opt/vmware/var/log/vcd/vcd_ova_ui_app.log file:
————–/opt/vmware/var/log/vcd/vcd_ova_ui_app.log Start———————
2020-04-19 13:23:52,026 | ERROR | uWSGIWorker1Core0 | ERROR: Command ‘[‘sudo’, ‘-n’, ‘-u’, ‘postgres’, ‘/opt/vmware/appliance/bin/api/replicationClusterStatus.py’]’ returned non-zero exit status 255.
2020-04-19 13:23:52,027 | ERROR | uWSGIWorker1Core0 | Return code: 255
2020-04-19 13:23:52,027 | DEBUG | uWSGIWorker1Core0 | Got cluster status: {}
2020-04-19 13:24:16,968 | DEBUG | uWSGIWorker1Core0 | Appliance is of type primary or standby
2020-04-19 13:24:16,969 | DEBUG | uWSGIWorker1Core0 | getting cluster status: [‘/opt/vmware/appliance/bin/api/replicationClusterStatus.py’]
2020-04-19 13:24:17,098 | ERROR | uWSGIWorker1Core0 | ERROR: Command ‘[‘sudo’, ‘-n’, ‘-u’, ‘postgres’, ‘/opt/vmware/appliance/bin/api/replicationClusterStatus.py’]’ returned non-zero exit status 255.
2020-04-19 13:24:17,099 | ERROR | uWSGIWorker1Core0 | Return code: 255
2020-04-19 13:24:17,099 | DEBUG | uWSGIWorker1Core0 | Got cluster status: {}
———–/opt/vmware/var/log/vcd/vcd_ova_ui_app.log End————————
Usually there is two common names for the above issue with vCloud Director 10.1 Virtual Appliance Deployment:
- Your NFS Share permissions were not accurate or not reachable
- You had left the “expire the root password upon first login” checked as you were completing the installation wizard of the vCD Appliance.
… Read More
…
19
Apr, 2020
How to Change VMware NSX-T Manager IP Address
VMware Network, VMware NSX
There is often the situation where you need to change the IP addresses of your NSX-T Managers. For example, you might be changing your IP schema as I am doing currently in my home lab. NSX-T does not have a field to change the IP address of it’s NSX Managers, but you will need to add new NSX Managers with the new desired IP, then gradually delete the old ones. Luckily the process is easy and straight forward as documented below.
Note: While I only have a single NSX-T Manager in my environment as it is a small home lab, usually in a production environment, you always want to maintain 3 NSX Managers active to sustain your NSX-T availability. Try to follow one of the below two approaches to maintain that.
-
Scenario A:
- Manager A has IP address 172.16.1.11.
- Manager B has IP address 172.16.1.12.
- Manager C has IP address 172.16.1.13.
- Add Manager D with a new IP address, for example, 192.168.55.11.
- Remove Manager A.
- Add Manager E with a new IP address, for example, 192.168.55.12.
- Remove Manager B.
- Add Manager F with a new IP address, for example, 192.168.55.13.
- Remove Manager C.
- Manager A has IP address 172.16.1.11.
-
Scenario B:
- Manager A has IP address 172.16.1.11.
… Read More
…
