[opensuse-autoinstall] net-udev and bonding
Hi all,
(please disregard my previous mail, some things where wrong, sorry.)
I am trying to rename and bond two eth with AY while installing over NFS. It fails in the second configure step because it can't setup networking.
SLES11 on a HP DL385 G5 with two internal NICs and one additional PCI dual-port NIC.
These are the relevant parts of my networking section:
<networking>
<net-udev config:type="list">
<rule>
<name>eth0</name>
<rule>ATTR{address}</rule>
<value>00:23:7d:25:5f:e4</value>
</rule>
<rule>
<name>eth1</name>
<rule>ATTR{address}</rule>
<value>00:23:7d:25:5f:e6</value>
</rule>
</net-udev>
<interfaces config:type="list">
<interface>
Hi,
These are the relevant parts of my networking section: <networking>
[... snip ...] </networking>
There seems to be nothing wrong with the profile, thus it is hard to say what went wrong at the end without seeing YaST logs from the autoinstallation. How does /etc/udev/rules.d/70-persistent-net.rules file look after the reboot? And what about ifcfg-ethX files (in /etc/sysconfig/network) - do these look sane? ("No configuration found for eth0 " suggests that they probably don't ...)
Or should I open a bugreport with Novell?
Yes, please do, even if it turns out not to be (auto)YaST bug at the end, at least YaST developer(s) can have a look at y2logs. Without them, it's just blind guessing ... the least of all, we can improve documentation if it happens so be some layer 8 issue :) B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi, On 02.06.2009 13:05 Katarina Machalkova wrote:
There seems to be nothing wrong with the profile, thus it is hard to say what went wrong at the end without seeing YaST logs from the autoinstallation.
Thanks for confirming this :) It also happens without bonding, just this: <net-udev config:type="list"> <rule> <name>eth1</name> <rule>ATTR{address}</rule> <value>00:23:7d:25:5f:e6</value> </rule> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth1</device> <startmode>auto</startmode> <ipaddr>1.2.3.4</ipaddr> <prefixlen>24</prefixlen> <netmask>255.255.255.0</netmask> </interface> </interfaces>
How does /etc/udev/rules.d/70-persistent-net.rules file look after the reboot?
It has all the settings as specified in the profile. I think this part works.
And what about ifcfg-ethX files (in /etc/sysconfig/network) - do these look sane? ("No configuration found for eth0 " suggests that they probably don't ...)
There is only ifcfg-eth2 with: BOOTPROTO='dhcp4' LLADDR='00:23:7d:25:5f:e6' STARTMODE='onboot' NAME='NetXtreme II BCM5708 Gigabit Ethernet' Which is not correct anymore, because :e6 has now been renamed to eth1. I guess it goes: 1) linuxrc boots from :e6 as eth2 2) main installation and reboot 3) udev renames :e6 from eth2->eth0 4) tries to bring up networking with pre-udev config (eth2) 5) yast needs some rpms (and fails) 6) network would get configured
Or should I open a bugreport with Novell? Yes, please do, even if it turns out not to be (auto)YaST bug at the end, at least YaST developer(s) can have a look at y2logs. Without them, it's just blind guessing ... the least of all, we can improve documentation if it happens so be some layer 8 issue :)
Ok, will do. Thanks again. Michael -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
And what about ifcfg-ethX files (in /etc/sysconfig/network) - do these look sane? ("No configuration found for eth0 " suggests that they probably don't ...)
There is only ifcfg-eth2 with: BOOTPROTO='dhcp4' LLADDR='00:23:7d:25:5f:e6' STARTMODE='onboot' NAME='NetXtreme II BCM5708 Gigabit Ethernet' Which is not correct anymore, because :e6 has now been renamed to eth1.
With your configuration, two files - ifcfg-eth0 and ifcfg-eth1 - should have been created, with the following content: BOOTPROTO=none STARTMODE=off + some more keys, mostly empty, not important anyway And one more - ifcfg-bond0 - for the bonding master device B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
And what about ifcfg-ethX files (in /etc/sysconfig/network) - do these look sane? ("No configuration found for eth0 " suggests that they probably don't ...)
There is only ifcfg-eth2 with: BOOTPROTO='dhcp4' LLADDR='00:23:7d:25:5f:e6' STARTMODE='onboot' NAME='NetXtreme II BCM5708 Gigabit Ethernet' Which is not correct anymore, because :e6 has now been renamed to eth1.
With your configuration, two files - ifcfg-eth0 and ifcfg-eth1 - should have been created, with the following content:
They would get created, but _after_ the RPM-installation-part of the "Post-Install and System Configuration" step (http://www.suse.com/~ug/autoyast_doc/System_Configuration.html#id2575942). That is what I meant by 6) in my previous mail:
1) linuxrc boots from :e6 as eth2 2) main installation and reboot 3) udev renames :e6 from eth2->eth0 4) tries to bring up networking with pre-udev config (eth2) 5) yast needs some rpms (and fails) 6) network would get configured
If I skip 5) it continues with "configuring lan". Then it goes out of yast and takes down the networking and starts it up again, now according to the profile. So networking and udev is done correctly, only in the wrong order. :) Regards, Michael -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Katarina Machalkova
-
Michael.Leu@mgb.ch