Hello Stéphane,

sorry for the delayed answer - I thought someone from the Atomic team would reply (I'm only involved in developing the regular CentOS images for Vagrant, centos/6 and centos/7, not with atomic-host). I can reproduce the problem with centos/atomic-host, but not with centos/7.

I noticed that the Atomic Host images do not disable the consistent naming of network devices; I think this is what produces this error, since eth0 remains eth0, but eth1 becomes enp0s8. Please try to add 'biosdevname=0 net.ifnames=0' to the kernel command line in grub (you can add 'v.gui = true' to disable the headless mode, see the Vagrant docs, and press 'e' really fast when the grub menu appears), and then enable these parameters permanently via 'sudo grubby --update-kernel=ALL --args='biosdevname=0 net.ifnames=0', after the box boots for the first time. It worked for me.

Jason, any thoughts?

Best regards, Laurențiu

On 08/12/16 11:23, Stéphane Klein wrote:

Hi,

I have this error with my Vagrant config:

Job for network.service failed because the control process exited with
error code

My Vagrant file:

Vagrant.configure("2") do |config|
config.vm.box = "centos/atomic-host"
config.vm.hostname = "ceph-client-2"
config.vm.network "private_network", type: "dhcp"
end

full log: https://gist.github.com/harobed/84d275b30ab928e4753b2c772425feca

With `journalctl -xe' I have:

Dec 08 10:16:30 ceph-client-2 sshd[12198]: lastlog_openseek: Couldn't stat
/var/log/lastlog: No such file or directory

How can I fix that?

Best regards, Stéphane

---

CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel