1
0
-1
2 answers
- 210
This is weird. I am using openstack and never saw this issue. What is the outout of console log?
virsh dumpxml <domain> | grep console
cat <console.log>
What installation are you using. I have seen Ubuntu-16.04 images with cloud-init problems. You may have to download a new stable image.
There is no need to change interface name to eth0, eth1 alike. There are few scripts will look for eth0 value by default such as asdc_vm_init.sh. So, it all depends on installation type.
if [ -e /opt/config/public_ip.txt ]
then
IP_ADDRESS=$(cat /opt/config/public_ip.txt)
else
IP_ADDRESS=$(ifconfig eth0 | grep "inet addr" | tr -s ' ' | cut -d' ' -f3 | cut -d':' -f2)
fiAdd your comment... - 10-1
I upgraded my 16.04 image and everything worked. Thanks for your help!
- kranthi guttikonda
Glad to know
Add your comment...
Hi, after running the init script on the Ubuntu 16.04 VMs (SDC, ROBOT, MSO), the VMs reboot to solidify the network changes. I am unable to ping the instances after this happens. I get a Destination Host Unreachable error for each of them while the 14.04 Ubuntu VMs are fine.
Is it necessary to execute these changes the 16.04 VMs?
Thanks,
Eli Williams
__________________________________________________________________________________
# Rename network interface in openstack Ubuntu 16.04 images. Then, reboot the VM to pick up changes
if [[ $CLOUD_ENV != "rackspace" ]]
then
sed -i "s/GRUB_CMDLINE_LINUX=.*/GRUB_CMDLINE_LINUX=\"net.ifnames=0 biosdevname=0\"/g" /etc/default/grub
grub-mkconfig -o /boot/grub/grub.cfg
sed -i "s/ens[0-9]*/eth0/g" /etc/network/interfaces.d/*.cfg
sed -i "s/ens[0-9]*/eth0/g" /etc/udev/rules.d/70-persistent-net.rules
echo 'network: {config: disabled}' >> /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
echo "APT::Periodic::Unattended-Upgrade \"0\";" >> /etc/apt/apt.conf.d/10periodic
reboot
fi
_________________________________________________________________________________