1) How do you properly remove a nic added via HA wizard when it fails
2) Any details on what this PNID issue is
3) Any ideas on how to repair eth0 so it starts on boot
-> I don't have a baseline as I did the "destroy-vcha" command first, but the rename of "/etc/systemd/network/10-eth0.network.manual" to "/etc/systemd/network/10-eth0.network"
This may be correct.. .or partial. input or validation appreciated. The VM is now booting fine with eth0
I don't have the current time to validate this but I believe I realize the issue.
The point of "Override Managment Network on Failover" would be a design where you would have failover to another VLAN / network segment (example: Prod 172.20.13.0/24 and DR site 172.20.12.0/24
As such when we ran the wizard we did not think it would be an issue if we input the "override" target IP to be on the SAME network as what is the current vCenter IP. Example: current vCenter public IP 172.20.13.99/24 with "override IP" set to 172.20.13.101/24
We did this because that was the old IP we has on the second vCenter server, back in 5.x when HA was not around and it was more of a resource quick recovery methodology.
We did NOT check that box (after running noted cleanup of nic it created but did not remove upon script failure) and the HA built out as expected.
If the above assumptions are correct VMWare has the following bugs:
1) Need to run check that if "Overide" is selected, it does not allow VLAN to be same as current running user facing IP .. or does not fail and allows
2) The wizard needs to back out the nic add and binding commands if the deployment of HA fails
3) The management portal needs to add in function to unbind IP and remove a secondary nic from appliance.