SDC,MSO & Robot VM are inaccessible after reboot 11/4611/1
authorArun Arora <aroraarun@vmware.com>
Fri, 2 Jun 2017 06:41:49 +0000 (12:11 +0530)
committerArun Arora <aroraarun@vmware.com>
Fri, 2 Jun 2017 07:04:42 +0000 (12:34 +0530)
commita8a9fec9dd7ab059c46a686d81a9b2c41537d6b8
treeb92f28084ed4d06ebac231f22ac779053b63cba9
parent8227785db0f52adbf3444dd7d493d5e9df5f4e68
SDC,MSO & Robot VM are inaccessible after reboot

Install scripts (/opt/<VM Name>_install.sh) of SDC, MSO & Robot VMs
change the Interface name from ensX to eth0 in the interface
configuration file.
Same changes are needed in /etc/udev/rules.d/70-persistent-net.rules
else IP address is not configured in these VMs post-reboot due to which
these VMs become inaccessible.

Change-Id: Ic139943579347253c9c051ff0a8451906d0e8017
Signed-off-by: Arun Arora <aroraarun@vmware.com>
boot/asdc_install.sh
boot/mso_install.sh
boot/robot_install.sh