[Server-devel] ifcfg-eth# files in /etc/sysconfig/network-scripts generated by runansible

[Anna]

This morning, I was trying out a 2 dongle install from
https://github.com/XSCE/xsce.git.  The default in vars/default_vars.yml is
eth0 as WAN and eth1 as LAN.  Well, I forgot to edit that for my interfaces
(eth1 as WAN and eth2 as LAN).  So after ./runansible finished, I edited
vars/default_vars.yml accordingly and reran ./runansible.

After a reboot, I couldn't ssh back in.  Walked over to the XO 1.75 and
ifconfig indicated that eth1 and eth2 were both on 172.18.96.1.  On DXS,
whenever I've forgotten to edit default_vars.yml for my interfaces, I can
edit that file, rerun ./runansible, and everything gets sorted out.

What I discovered is that now runansible apparently generates an ifcfg file
for the LAN interface in /etc/sysconfig/network-scripts.  After attempt #1
with the default interfaces (eth0 for WAN and eth1 for LAN) and attempt #2
with my edits (eth1 for WAN and eth2 for LAN), now I had ifcfg-eth1 and
ifcfg-eth2 in there:

DEVICE=eth1
BOOTPROTO=static
DHCPCLASS=
HWADDR=00:1C:49:01:04:27
IPADDR=172.18.96.1
NETMASK=255.255.224.0
ONBOOT=yes

DEVICE=eth2
BOOTPROTO=static
DHCPCLASS=
HWADDR=00:E0:4C:53:44:58
IPADDR=172.18.96.1
NETMASK=255.255.224.0
ONBOOT=yes

Before I figured out what was going on, I rebooted a couple of times and
was perplexed that both eth1 and eth2 kept coming up on 172.18.96.1.

So, I deleted ifcfg-eth1, reran ./runansible, rebooted, and now networking
is fine.  WAN is eth1 on 192.168.1.11 and LAN is eth2 on 172.18.96.1, like
it's supposed to be.

What we should probably do is discard any ifcfg-eth# files first thing so
there aren't any old ones lingering about to muck up networking.

Anna
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/server-devel/attachments/20131025/ca4190cc/attachment.html>