I'm using autoyast to deploy a new Opensuse 13.1 X64 system.
After the autoyast installation finishes, there's is no network active on the deployed system. i can manually enter yast --> network settings and switch it to dhcp and then it's working
but i'm puzzled. because in the xml in the networking --> interface segment it clearly states DHCP
from what i can see in the xml networking segment.
there is a new sub-segment generated:
which might be causing the issues. could i simply remove it.? i'm not sure what it's used for anyway.
Anyway i'm pretty confused about predictablenetworknames. since it becomes pretty unpredictable when you have multiple systems with different hardware configurations, which is our reality at my work :-(
After the autoyast installation finishes, there's is no network active on the deployed system. i can manually enter yast --> network settings and switch it to dhcp and then it's working
but i'm puzzled. because in the xml in the networking --> interface segment it clearly states DHCP
Code:
<interface>
<bootproto>dhcp</bootproto>
<device>eno1</device>
<name>Intel Ethernet controller</name>
<startmode>auto</startmode>
<usercontrol>no</usercontrol>
</interface>
there is a new sub-segment generated:
Code:
<net-udev config:type="list">
<rule>
<name>eno1</name>
<rule>ATTR{address}</rule>
<value>08:2e:5f:0b:8e:4d</value>
</rule>
</net-udev>Anyway i'm pretty confused about predictablenetworknames. since it becomes pretty unpredictable when you have multiple systems with different hardware configurations, which is our reality at my work :-(