On Mon, Aug 24, 2015 at 8:24 AM, Peter Schiffer [email protected]
wrote:

Any tips for more info, how to debug, or how to fix?

First thing to fix is to remove the plugin version of vagrant-libvirt.
You've already got the system version installed!
Try again after fixing that.

from oh-my-vagrant.

I think that plugin was auto-updated at some point. I had to remove user installed plugin manually by removing gem and gemspec. Now:

$ vagrant plugin list
vagrant-hostmanager (1.5.0)
  - Version Constraint: 1.5.0
vagrant-libvirt (0.0.24, system)

But without success. Created new VM with atomic host and it had eth1 turned off.

from oh-my-vagrant.

Any other idea?

from oh-my-vagrant.

Run vlog up ... and see what it says. Also look at /etc/sysconfig/network-scripts/ifcfg-eth1 and paste that file here after it doesn't come up.

from oh-my-vagrant.

Thanks for the tip, I have same updates:
I found out, that there is a new atomic guest plugin in the latest Vagrant. I'm on Fedora 21, and Vagrant packaged there is old (1.7.2), so I've updated to the latest upstream Vagrant rpm (1.7.4). Now, Vagrant detects the atomic guest and correctly configures the second network interface, so after provisioning it's up. But after a reboot, it stays down :-( I've checked rhel-7.1 box and the second iface there stays up after a reboot. The network configuration looks the same in the vagrant.log file from vlog up command. Maybe there's some issue in the atomic OS, not sure.

from oh-my-vagrant.

On Wed, Sep 2, 2015 at 3:59 AM, Peter Schiffer [email protected]
wrote:

Thanks for the tip, I have same updates:
I found out, that there is a new atomic guest plugin in the latest
Vagrant. I'm on Fedora 21, and Vagrant packaged there is old (1.7.2), so
I've updated to the latest upstream Vagrant rpm (1.7.4). Now, Vagrant
detects the atomic guest and correctly configures the second network
interface, so after provisioning it's up. But after a reboot, it stays down
:-( I've checked rhel-7.1 box and the second iface there stays up after a
reboot. The network configuration looks the same in the vagrant.log file
from vlog up command. Maybe there's some issue in the atomic OS, not sure.

Aha! Well now I can help a little bit... There was a bug in Vagrant, that
if the machine had a docker0 interface, things would be broken...
Eg: https://bugzilla.redhat.com/show_bug.cgi?id=1221006 Maybe it was
related?? I thought it was in F21...

Does this help your debugging a bit?

from oh-my-vagrant.

Unfortunately no, I was victim of that bug, but it's result was that the content of the /etc/sysconfig/network-scripts/ifcfg-eth1 file was placed in the /etc/sysconfig/network-scripts/ifcfg-eth0. Here, the content of these files is correct:

[vagrant@master ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 
DEVICE="eth0"
BOOTPROTO="dhcp"
ONBOOT="yes"
TYPE="Ethernet"
PERSISTENT_DHCLIENT="yes"

[vagrant@master ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1 
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.91.100
NETMASK=255.255.255.0
DEVICE=eth1
PEERDNS=no
#VAGRANT-END

from oh-my-vagrant.

Does this mean you figured out the issue?

On Wed, Sep 2, 2015 at 11:39 AM, Peter Schiffer [email protected]
wrote:

Unfortunately no, I was victim of that bug, but it's result was that the
content of the /etc/sysconfig/network-scripts/ifcfg-eth1 file was placed
in the /etc/sysconfig/network-scripts/ifcfg-eth0. Here, the content of
these files is correct:

[vagrant@master ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
BOOTPROTO="dhcp"
ONBOOT="yes"
TYPE="Ethernet"
PERSISTENT_DHCLIENT="yes"

[vagrant@master ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
#VAGRANT-BEGIN

The contents below are automatically generated by Vagrant. Do not modify.

NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.91.100
NETMASK=255.255.255.0
DEVICE=eth1
PEERDNS=no
#VAGRANT-END

—
Reply to this email directly or view it on GitHub
#117 (comment)
.

from oh-my-vagrant.

No, it means just that the content of the ifcfg files is correct and right after provisioning the networking works OK, but after reboot, the eth1 is down. This is on atomic host. RHEL works fine.

from oh-my-vagrant.

On Wed, Sep 2, 2015 at 11:45 AM, Peter Schiffer [email protected]
wrote:

No, it means just that the content of the ifcfg files is correct and right
after provisioning the networking works OK, but after reboot, the eth1 is
down. This is on atomic host. RHEL works fine.

Can you compare contents of ifcfg-eth1 before/after reboot?

Also look in the logs. Use vlog to do so...

from oh-my-vagrant.

The content of the ifcfg-eth1 file seems the same after reboot and there is nothing strange in the vagrant log. But I suspect the 7.1.0 version of the atomic OS, because in some cases, while doing upgrade, some configuration can be lost. This problem is fixed in newer versions, but I don't have newer vagrant box. So, I'm using workaround, which works pretty fine:

:shell:
- script: chkconfig network on
- script: ifup eth1

I'm closing this for now. I'll post an update if I find something relevant. Thanks for the help.

from oh-my-vagrant.