[opensuse-autoinstall] SLES10sp3 Autoyast Network configs being processed but lost later.
in SLES 10sp3.. My autoyast profile network configuration is being processed, but forgotten. It does not end up in the "installedSystem.xml", but is clearly being considered in 'y2log' (with no apparent reason for discarding it) Network Interfaces section contains: ------------------------------------------------------------- <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>192.168.50.33</ipaddr> <network>192.168.50.0</network> <broadcast>192.168.50.255</broadcast> <netmask>255.255.255.0</netmask> <startmode>onboot</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> ------------------------------------------------------------- Looks like, at least at SOME point along the way, AutoYast is finding the interface, setting up configuration data for a /etc/sysconfig/network/if file, but then later on seems to completely forget to write the file, or it gets removed. This worked in SLES9. - Should the above autoyast profile configuration work? - If so, what's going wrong? - If not, am i relegated to creating post install scripts to manually configure the sysconfig/network files and udev rules? thanks, --stephen y2log output (reformatted to be more readable) ------------------------------------------------------------- in3(11181) [YCP] network/complex.ycp:65 Devs=$["eth":$["id-00:26:b9:39:18:21":$["BOOTPROTO":"static" "BROADCAST":"" "ETHTOOL_OPTIONS":"" "IPADDR":"192.168.50.33" "MTU":"" "NAME":"Broadcom NetXtreme II BCM5709 Gigabit Ethernet" "NETMASK":"255.255.255.0" "NETWORK":"" "REMOTE_IPADDR":"" "STARTMODE":"auto" "UNIQUE":"rBUF.yy10jcgJwT2" "USERCONTROL":"no" "_aliases":$[] "_nm_name":"bus-pci-0000:01:00.0"]]] in3(11181) [YCP] NetworkDevices.ycp:609 << exact same output as above >> in3(12869) [YCP] Detection.ycp:235 IFCONFIG1: $["exit":0 "stderr":"" "stdout":"eth0 Link encap:Ethernet HWaddr 00:26:B9:39:18:21 \n inet addr:192.168.50.33 Bcast:192.168.50.255 Mask:255.255.255.0\n inet6 addr: fe80::226:b9ff:fe39:1821/64 Scope:Link\n UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1\n RX packets:32410 errors:0 dropped:0 overruns:0 frame:0\n TX packets:1483 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:1000 \n RX bytes:5966883 (5.6 Mb) TX bytes:603226 (589.0 Kb)\n Interrupt:58 Memory:d6000000-d6012800 \n\nlo Link encap:Local Loopback \n inet addr:127.0.0.1 Mask:255.0.0.0\n inet6 addr: ::1/128 Scope:Host\n UP LOOPBACK RUNNING MTU:16436 Metric:1\n RX packets:22 errors:0 dropped:0 overruns:0 frame:0\n TX packets:22 errors:0 dropped:0 overruns:0 carrier:0\n collisions:0 txqueuelen:0 \n RX bytes:1424 (1.3 Kb) TX bytes:1424 (1.3 Kb)\n\n"] in3(12869) [YCP] Detection.ycp:242 IFCONFIG2: $["exit":0 << exact same output as under IFCONFIG1 >> in3(12869) [YCP] NetworkDevices.ycp:505 config=$["BOOTPROTO":"static" "BROADCAST":"" "ETHTOOL_OPTIONS":"" "IPADDR":"192.168.50.33/24" "MTU":"" "NAME":"Broadcom NetXtreme II BCM5709 Gigabit Ethernet" "NETWORK":"" "REMOTE_IPADDR":"" "STARTMODE":"auto" "UNIQUE":"rBUF.yy10jcgJwT2" "USERCONTROL":"no" "_nm_name":"bus-pci-0000:01:00.0"] And Finally, last place i see it referenced: [wfm] Y2CCWFM.cc(createInLevel):149 Parsing finished [Interpreter] network/services/proxy.ycp:338 Calling YaST client lan_auto (arguments: ["Export"]) [YCP] clients/lan_auto.ycp:14 ---------------------------------------- [YCP] clients/lan_auto.ycp:15 Lan autoinst client started [YCP] clients/lan_auto.ycp:188 Adding: BOOTPROTO=static [YCP] clients/lan_auto.ycp:188 Adding: BROADCAST= [YCP] clients/lan_auto.ycp:188 Adding: ETHTOOL_OPTIONS= [YCP] clients/lan_auto.ycp:188 Adding: IPADDR=192.168.50.33 [YCP] clients/lan_auto.ycp:188 Adding: MTU= [YCP] clients/lan_auto.ycp:188 Adding: NAME=Broadcom NetXtreme II BCM5709 Gigabit Ethernet [YCP] clients/lan_auto.ycp:188 Adding: NETMASK=255.255.255.0 [YCP] clients/lan_auto.ycp:188 Adding: NETWORK= [YCP] clients/lan_auto.ycp:188 Adding: PREFIXLEN=24 [YCP] clients/lan_auto.ycp:188 Adding: REMOTE_IPADDR= [YCP] clients/lan_auto.ycp:188 Adding: STARTMODE=auto [YCP] clients/lan_auto.ycp:188 Adding: UNIQUE=rBUF.yy10jcgJwT2 [YCP] clients/lan_auto.ycp:188 Adding: USERCONTROL=no [YCP] clients/lan_auto.ycp:188 Adding: _nm_name=bus-pci-0000:01:00.0 [YCP] clients/lan_auto.ycp:337 Lan auto finished [YCP] clients/lan_auto.ycp:338 ---------------------------------------- [Interpreter] network/services/proxy.ycp:338 Called YaST client returned. [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Ldap) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Autologin) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Nsswitch) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (Pam) [wfm] Y2WFMComponent.cc(import):735 Y2WFMComponent::import (LdapPopup) [wfm] Y2CCWFM.cc(createInLevel):149 Parsing finished [Interpreter] clients/ldap_auto.ycp:104 Calling YaST client ldap_auto (arguments: ["GetModified"]) ------------------------------------------------------------- -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy@ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
The only difference i see with your profile is that we use the <name> section and <startmode> is set to auto. Works on SL9.3 , SL10.3 , SL 11.1 & SLES 11 BUT we use also a module_entry section within the networking section. <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.11.255.255</broadcast> <device>eth0</device> <ipaddr>HOSTIP</ipaddr> ---->>> <name>Ethernet Network Card</name> <netmask>255.255.0.0</netmask> <network>10.11.0.0</network> ---->>> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> So our whole network section looks like: $ cat TEMPLATE.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>ourdomain.org</domain> <hostname>NODENAME</hostname> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.11.255.255</broadcast> <device>eth0</device> <ipaddr>10.11.0.100</ipaddr> <name>Ethernet Network Card</name> <netmask>255.255.0.0</netmask> <network>10.11.0.0</network> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> </networking> </configure> </profile> .....
Network Interfaces section contains:
------------------------------------------------------------- <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>192.168.50.33</ipaddr> <network>192.168.50.0</network> <broadcast>192.168.50.255</broadcast> <netmask>255.255.255.0</netmask> <startmode>onboot</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> -------------------------------------------------------------
hth Hajo
I'm still not having a lot of joy on this. I'm at the point where i think i'm needing to specify the bus addresses of interfaces to get the config to stick, but i'd like to make this as generic as possible. (part of why i want to use 'autoyast' is my expectation that a lot of the hard-work in autoconfig will be done for me ;)) So, i'm currently using rules to specify hardware type match to pull in the right "modules" and <device> matches for specific hardware types. e.g. ------------------------------------------------------------------- [cf/rules/rules.xml] ... <!-- Network Card Configuration for R710s --> <rule> <product> <match>PowerEdge R710</match> <match_type>exact</match_type> </product> <result> <profile>ZORK-Dell11G.xml</profile> <!-- Dell 11th Gen systems --> <continue config:type="boolean">true</continue> </result> </rule> ..Rule for node type via 'custom' rule follows this ------------------------------------------------------------------- [ZORK-Dell11G] (i specify network, broadcast,netmask here because all systems have this in common) <interfaces config:type="list"> <interface> <name>Broadcom NetXtreme II BCM5709 Gigabit Ethernet</name> <prefixlen>24</prefixlen> <bootproto>static</bootproto> <device>eth0</device> <name>Internal Data Network</name> <network>192.168.50.0</network> <broadcast>192.168.50.255</broadcast> <netmask>255.255.255.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <name>Broadcom NetXtreme II BCM5709 Gigabit Ethernet</name> <prefixlen>24</prefixlen> <bootproto>static</bootproto> <device>eth1</device> <name>Heartbeat and DRBD network</name> <network>192.168.55.0</network> <broadcast>192.168.55.255</broadcast> <netmask>255.255.255.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <modules config:type="list"> <module_entry> <device>bus-pci-0000:01:00.0</device> <module>bnx2</module> <options></options> </module_entry> <module_entry> <device>bus-pci-0000:01:00.1</device> <module>bnx2</module> <options></options> </module_entry> </modules> ------------------------------------------------------------------- [ZORKnode-in1] <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <name>Internal Data Network</name> <ipaddr>192.168.50.31</ipaddr> <network>192.168.50.0</network> <broadcast>192.168.50.255</broadcast> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <name>Heartbeat and DRBD network</name> <ipaddr>192.168.55.1</ipaddr> <network>192.168.55.0</network> <broadcast>192.168.55.255</broadcast> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> ------------------------------------------------------------------- The end result of this after the profile merging is that i get /etc/sysconfig/network/ifcfg-eth-id-{MAC-ADDR} files, but they contain no IP info (i.e. something like: BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='Internal Data Network' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='rBUF.bBSepP2NetB' USERCONTROL='no' _nm_name='bus-pci-0000:01:00.0' (i thought i saved one, so this is an approximation. several items retained the values i had set for them, and other auto-generated values such as UNIQUE and _nm_name were set as expected.) So, any clues on what i'm doing wrong here? (gack, i do just notice now that i have <name> specified in the <interface> blocks in the 11G.xml file twice, but the resultant ifcfg-eth file shows the NAME i specified last. I'll remove the duplicate <name> entities and the network, broadast, netmask, prefixlen (are both of those needed?) from the 11G general profile and try again, but i do want to make sure that this type of network interface+module profile stacking (merge) is supported. thanks, --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy@ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Thursday 21 January 2010 Stephen Dowdy wrote:
So, any clues on what i'm doing wrong here?
you can test the merge process on the command line: /usr/bin/xsltproc --novalid --param replace "'false'" \ --param with "'a.xml'" --output out.xml \ /usr/share/autoinstall/xslt/merge.xslt base.xml does the out.xml contain the ip adresses? -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Uwe Gansert wrote, On 01/22/2010 02:04 AM:
you can test the merge process on the command line:
/usr/bin/xsltproc --novalid --param replace "'false'" \ --param with "'a.xml'" --output out.xml \ /usr/share/autoinstall/xslt/merge.xslt base.xml
does the out.xml contain the ip adresses?
Assuming i understand the exact nature of this xsltproc process, my rules/rules.xml essentially does: include ZORKbase.xml (matches product = "*", so unconditional) include ZORK-Dell8G.xml (matches product=~ "PowerEdge [12]850") include ZORKsite-zork0.xml (custom1 rule /proc/cmdline ZORKsite=zork0) include ZORKnode-in1.xml (custom2 rule /proc/cmdline ZORKnode=in1) $ grep -o 'setValue (tomerge@.*$' y2log setValue (tomerge@0x12d8320 = '[]') setValue (tomerge@0x12d8320 = '["ZORKbase.xml"]') setValue (tomerge@0x12d8320 = '["ZORKbase.xml", "ZORK-Dell8G.xml"]') setValue (tomerge@0x12d8320 = '["ZORKbase.xml", "ZORK-Dell8G.xml", "ZORKsite-umds0.xml"]') setValue (tomerge@0x12d8320 = '["ZORKbase.xml", "ZORK-Dell8G.xml", "ZORKsite-umds0.xml", "ZORKnode-in1.xml"]') setValue (tomerge@0x12d8320 = '["ZORKbase.xml", "ZORK-Dell8G.xml", "ZORKsite-umds0.xml", "ZORKnode-in1.xml"]') setValue (tomerge@0x12d8320 = '[]') setValue (tomerge@0x12d8320 = '["classes/Ingest/Partitioning.xml"]') setValue (tomerge@0x12d8320 = '["classes/Ingest/Partitioning.xml", "classes/Ingest/Software.xml"]') setValue (tomerge@0x12d8320 = '["classes/Ingest/Partitioning.xml", "classes/Ingest/Software.xml"]') setValue (tomerge@0x12d8320 = '["prefinal_autoinst.xml", "classes/Ingest/Partitioning.xml", "classes/Ingest/Software.xml"]') That looks like my expected merge stack ^^^^^ So, i think what you're asking me to do is: (Progressive merges) # xsltproc --novalid --param replace "'false'" --param with "'ZORK-Dell8G.xml'" --output out1.xml /usr/share/autoinstall/xslt/merge.xslt ZORKbase.xml # xsltproc --novalid --param replace "'false'" --param with "'ZORKsite-zork0.xml'" --output out2.xml /usr/share/autoinstall/xslt/merge.xslt out1.xml # xsltproc --novalid --param replace "'false'" --param with "'ZORKnode-in1.xml'" --output out3.xml /usr/share/autoinstall/xslt/merge.xslt out2.xml (ZORKbase + ZORK-Dell8g -> out1 out1 + ZORKsite-zork0 -> out2 out2 + ZORKnode-in1 -> out3 ) # md5sum out?.xml a834a533590495705b005e7343e69f46 out1.xml 4a8ffb0f624b2c5d555696ea62f74bce out2.xml 40879a7f42e71f60c31001631270aba6 out3.xml (yep, they're all different) # grep ipaddr out3.xml <ipaddr>192.168.50.31</ipaddr> <ipaddr>192.168.55.1</ipaddr> (And the IPADDRs stayed throughout the merge.) In this last round of installing, i note that my *hostname* has also been lost, but: in1:/cf # grep hostname out?.xml out1.xml: <dhclient_hostname_option>AUTO</dhclient_hostname_option> out1.xml: <dhcp_hostname config:type="boolean">false</dhcp_hostname> out2.xml: <ns1:dhclient_hostname_option>AUTO</ns1:dhclient_hostname_option> out2.xml: <ns1:dhcp_hostname config:type="boolean">false</ns1:dhcp_hostname> out3.xml: <ns1:dhclient_hostname_option>AUTO</ns1:dhclient_hostname_option> out3.xml: <ns1:dhcp_hostname config:type="boolean">false</ns1:dhcp_hostname> out3.xml: <hostname>in1</hostname> It's in there via xsltproc merging. And it's in the files getting handled by autoyast. ./YaST2-03146-sLGAEW/rules/ZORKnode-in1.xml: <hostname>in1</hostname> trying to debug the y2log with 'y2debug=1' is a bit overwhelming. (yeah, too much info better than not enough) but can you confirm, since i can't immediately see it, that the xsltproc isn't just merging the base_profile with each profile into a single result.xml file? # grep -o '.\{1,80\}result.xml.*base_profile.xml' y2log | uniq AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml mp/YaST2-03146-sLGAEW/rules/ZORK-Dell8G.xml'\" --output /tmp/YaST2-03146-sLGAEW/result.xml /usr/share/autoinstall/xslt/merge.xslt /tmp/YaST2-03146-sLGAEW/base_profile.xml ironment.cc(pushframe):78 Push frame AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml YaST2-03146-sLGAEW/rules/ZORKsite-zork0.xml'\" --output /tmp/YaST2-03146-sLGAEW/result.xml /usr/share/autoinstall/xslt/merge.xslt /tmp/YaST2-03146-sLGAEW/base_profile.xml ironment.cc(pushframe):78 Push frame AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml p/YaST2-03146-sLGAEW/rules/ZORKnode-in1.xml'\" --output /tmp/YaST2-03146-sLGAEW/result.xml /usr/share/autoinstall/xslt/merge.xslt /tmp/YaST2-03146-sLGAEW/base_profile.xml ironment.cc(pushframe):78 Push frame AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml GAEW/rules/classes/Ingest/Partitioning.xml'\" --output /tmp/YaST2-03146-sLGAEW/result.xml /usr/share/autoinstall/xslt/merge.xslt /tmp/YaST2-03146-sLGAEW/base_profile.xml ironment.cc(pushframe):78 Push frame AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml 6-sLGAEW/rules/classes/Ingest/Software.xml'\" --output /tmp/YaST2-03146-sLGAEW/result.xml /usr/share/autoinstall/xslt/merge.xslt /tmp/YaST2-03146-sLGAEW/base_profile.xml ironment.cc(pushframe):78 Push frame AutoInstallRules::XML_cleanup ((tmpdir + "/result.xml"), (tmpdir + "/base_profile.xml Here's the resultant interfaces section in full: (as you can see, i've got lots of commented stuff through testing) -------------------------------------------------------------- [ xsltproc MERGED output from profiles ] <ns1:interfaces config:type="list"> <ns1:interface> <!-- <name>Dell PRO/1000 MT Network Connection</name> --><!-- <name>Internal Data Network</name> --><ns1:bootproto>static</ns1:bootproto> <ns1:device>eth0</ns1:device> <name>Internal Data Network</name> <ipaddr>192.168.50.31</ipaddr> <network>192.168.50.0</network> <broadcast>192.168.50.255</broadcast> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <ns1:startmode>auto</ns1:startmode> <ns1:usercontrol>no</ns1:usercontrol> </ns1:interface> <ns1:interface> <!-- <name>Dell PRO/1000 MT Network Connection</name> --><!-- <name>Heartbeat and DRBD network</name> --><ns1:bootproto>static</ns1:bootproto> <ns1:device>eth1</ns1:device> <name>Heartbeat and DRBD network</name> <ipaddr>192.168.55.1</ipaddr> <network>192.168.55.0</network> <broadcast>192.168.55.255</broadcast> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <ns1:startmode>auto</ns1:startmode> <ns1:usercontrol>no</ns1:usercontrol> </ns1:interface> </ns1:interfaces> <ns1:managed config:type="boolean">false</ns1:managed> <modules config:type="list"> <module_entry> <device>bus-pci-0000:06:07.0</device> <module>e1000</module> <options/> </module_entry> <module_entry> <device>bus-pci-0000:07:08.0</device> <module>e1000</module> <options/> </module_entry> </modules><!-- <modules config:type="list"> <module_entry> <device>eth0</device> <module></module> <options></options> </module_entry> <module_entry> <device>eth1</device> <module></module> <options></options> </module_entry> </modules> --> <!-- <module_entry> <device>bus-pci-0000:04:00.0</device> <module>bnx2</module> <options></options> </module_entry> <module_entry> <device>bus-pci-0000:08:00.0</device> <module>bnx2</module> <options></options> </module_entry> --> <!-- <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> --> -------------------------------------------------------------- -------------------------------------------------------------- Here's what i see for this machine if i 'yast2 network' and configure it manually after install, then do a 'yast2 autoyast' (Tools->Create Reference): in1:/var/lib/autoinstall/repository # sed -ne '/<interfaces/,/<\/interfaces/p;/<modules/,/<\/modules>/p' CRONKY.xml <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth-id-00:14:22:20:3d:3f</device> <ipaddr>192.168.50.31</ipaddr> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth-id-00:14:22:20:3d:40</device> <ipaddr>192.168.55.1</ipaddr> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>bus-pci-0000:06:07.0</device> <module>e1000</module> <options></options> </module_entry> <module_entry> <device>bus-pci-0000:07:08.0</device> <module>e1000</module> <options></options> </module_entry> </modules> -------------------------------------------------------------- And finally, here's what comes up in the autoyast install: in1:/var/adm/autoinstall/cache # sed -ne '/<interfaces/,/<\/interfaces/p;/<modules/,/<\/modules>/p' installedSystem.xml <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>bus-pci-0000:06:07.0</device> <module>e1000</module> </module_entry> <module_entry> <device>bus-pci-0000:07:08.0</device> <module>e1000</module> </module_entry> </modules> -------------------------------------------------------------- If i haven't specified the "modules" entries as i have done, for the ZORK-Dell8G.xml (8th Gen poweredge) using the known pci bus addresses, i get NO interface configuration AT ALL, in this case i'm getting it, it just doesn't have any interface specific addressing information -------------------------------------------------------------- Finally, here's the exact interfaces+modules sections from all 4 profile files in1:/cf # sed -ne '/<interfaces/,/<\/interfaces/p;/<modules/,/<\/modules>/p' ZORKbase.xml in1:/cf # sed -ne '/<interfaces/,/<\/interfaces/p;/<modules/,/<\/modules>/p' ZORK-Dell8G.xml <interfaces config:type="list"> <interface> <!-- <name>Dell PRO/1000 MT Network Connection</name> --> <!-- <name>Internal Data Network</name> --> <bootproto>static</bootproto> <device>eth0</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <!-- <name>Dell PRO/1000 MT Network Connection</name> --> <!-- <name>Heartbeat and DRBD network</name> --> <bootproto>static</bootproto> <device>eth1</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>bus-pci-0000:06:07.0</device> <module>e1000</module> <options></options> </module_entry> <module_entry> <device>bus-pci-0000:07:08.0</device> <module>e1000</module> <options></options> </module_entry> </modules> in1:/cf # sed -ne '/<interfaces/,/<\/interfaces/p;/<modules/,/<\/modules>/p' ZORKsite-zork0.xml in1:/cf # sed -ne '/<interfaces/,/<\/interfaces/p;/<modules/,/<\/modules>/p' ZORKnode-in1.xml <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <name>Internal Data Network</name> <ipaddr>192.168.50.31</ipaddr> <network>192.168.50.0</network> <broadcast>192.168.50.255</broadcast> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <name>Heartbeat and DRBD network</name> <ipaddr>192.168.55.1</ipaddr> <network>192.168.55.0</network> <broadcast>192.168.55.255</broadcast> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> <module></module> <options></options> </module_entry> <module_entry> <device>eth1</device> <module></module> <options></options> </module_entry> </modules> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy@ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Stephen Dowdy wrote, On 01/22/2010 07:29 PM:
trying to debug the y2log with 'y2debug=1' is a bit overwhelming. (yeah, too much info better than not enough) but can you confirm, since i can't immediately see it, that the xsltproc isn't just merging the base_profile with each profile into a single result.xml file?
Sorry, What i should clarify is, "last merge wins?" as i don't see anything like 'cp result.xml base_profile.xml', run next merge... --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy@ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Hans-Joachim Ehlers -
Stephen Dowdy -
Uwe Gansert