I found problem in upgrade procedure in case of more than 3 NIC cards. I believe that this is critical for people an it is urgent to resolve before full production image. I Also found remedy to fix problem permanently.
- base version one of 1.1.7 or 1.1.8,
- target version one of: 1.2.0: rc10, rc11, EPA2,
- more than 3 NIC cards,
- tested on VMWARE ESXi 6.5 VYOS virtual machine,
- As baseline you can use virtual machine with VYOS version 1.1.7 or 1.1.8 or 1.1.7 upgraded to 1.1.8. with more than 3 virtual network VMXNET3 adapters. It may happen on other visualization or physical platforms as well.
- Upgrade from baseline to any VYOS version 1.2.0 rc10, rc11, EPA2. It may happen with other 1.2.0 versions I did not test. Upgrade with "add system image" command and then issue "poweroff now". Next step is to change OS definition to "Debian Jessie" in VMWARE VM definition under "VM Options" -> "General Options" and change "Guest OS" to "Other" and "Guest OS Version" to "Debian GNU/Linux 8 (64-bit)". Power on VM with VYOS.
- Wait that OS boots and login to VYOS. Everything should work as expected. Wait for additional 2 minutes (must) and again "poweroff now". Power on VM with VYOS.
- VYOS VM will stop working. Why, because strange error with mixing MAC addresses within VM.
I will show how to resolve this issue.
- Now you have to use console access to your VYOS VM because most likely you will completely loose access to VM on all interfaces. Login back to VYOS VM.
- At command prompt invoke vi editor with "vi /config/config.boot". Go to ethernet interfaces and you will notice strange behavior that line with "hw-id" configuration option is listed twice for each ethernet interface except for last one. First occurrence has MAC address in double apostrophes second occurrence without apostrophes. Line with "hw-id" configuration option and double apostrophes is original configuration second occurrence without apostrophes is added by VYOS because of bug (beyond scope of this document). This leads to mixture of MAC address and mixing of VMXNET3 interfaces and of course to nonfunctional state of VYOS VM.
- To resolve this situation:
- erase every line of "hw-id" configuration option without apostrophes (automatically added during upgrade),
- erase double apostrophes in every line with "hw-id" configuration option so there are no apostrophes (original configuration),
- double check that no other configuration lines were changed,
- save configuration,
- issue "reboot now" command.
- Congratulations you resolved problem. At least I saved my 2 VYOS VMs with this procedure. YMMW.
- I have to mention that PERFORM BACKUP OF VM AND CONFIGURATION BEFORE TOUCHING ANYTHING