Re: [cloud] #141: Vagrant-libvirt Failed for Fedora-Cloud-Atomic 23
#141: Vagrant-libvirt Failed for Fedora-Cloud-Atomic 23
---------------------+---------------------
Reporter: aalam | Owner:
Type: defect | Status: new
Priority: blocker | Milestone: Future
Component: --- | Resolution:
Keywords: meeting |
---------------------+---------------------
Comment (by dustymabe):
Hey aalam,
I think I know the problem here. I believe we have a problem because the
network device is not coming up as eth0 on atomic hosts. It actually comes
up often with a random name.. so on a subsequent reboot you could get
ens2,ens3 etc.. Which means you'll get a different IP from dhcp, which
means vagrant loses track of your ip and you can no longer get in to the
host.
We have /etc/udev/rules.d/80-net-setup-link.rules symlinked to /dev/null
though so it's not clear why this is happening.
-bash-4.3# ls -l /etc/udev/rules.d/80-net-setup-link.rules
lrwxrwxrwx. 1 root root 9 Oct 30 02:06 /etc/udev/rules.d/80-net-setup-
link.rules -> /dev/null
This page explains that having that symlink in place should be sufficient
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterf...
. I guess for now we could add the other disabler which is to have
net.ifnames=0 on the kernel command line.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/141#comment:1>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System