- openSUSE Autoinstall

[opensuse-autoinstall] Ask for Installation Server
by Stephens, Bill {PBSG} 10 Feb '10

10 Feb '10

Is it possible to either ask for just the installation server (I don't want to query the user for ip info), or provide a list of installation servers and have autoyast automatically pick the fastest mirror? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[Fwd: Re: [opensuse-autoinstall] Question: yast autoyast command line alternative]
by Simon Loewenthal/NL/Tele2 09 Feb '10

09 Feb '10

Uwe Gansert wrote: > on Friday 05 February 2010 Simon Loewenthal/NL/Tele2 wrote: > > >> I've been looking on Google for a day for this command. This makes >> my life so much easier. Thank-you. >> >> I notice that it starts a ASCII UI but I intend to call this via ssh. >> e.g ssh root@t2prd33 'yast2 clone_system' >> Is there a parameter I can specify to have it fall back to a dumb tty, >> or will it attempt to detect this automatically? >> > > I did not test it but something like this might do the trick: > ssh --batch root@t2prd33 "screen -D -m yast clone_system" > but it's untested by me > > Morning everyone, A continuation from a thread last Friday: Thanks. Tried it but it hung. I ran it interactively but got this message, which explains why it did not work: Error │ │ The storage subsystem is locked by the application "y2base" (30478). │ │ You must quit that application before you can continue. │ │ │ │ [Continue] [Cancel] I am unsure what this means. I do not rememver adding this. On another system I saw a similar message about some scsi subsystem not beong installed. Simon. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Question: yast autoyast command line alternative
by Simon Loewenthal/NL/Tele2 05 Feb '10

05 Feb '10

Dear all, I wish to create autoinstall files from several SLES and OpenSuse machine. About 40 in total. These systems were installed by someone else in the past. Some would have used autoyast and other would have been installed from an ISO image. I know that I can run the yast autoyast command to clone the system configuration into an .xml file, which I would like to use as a profile in case of system destruction (!). Is there a command line alternative to the yast UI so that I can kick all of these at the same time? Regards, Simon. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4

[opensuse-autoinstall] configuring NFS mounts in autoyast *disables* NFSv4
by Andrew Daugherity 03 Feb '10

03 Feb '10

(Platform: SLES 11 amd64) I have run into some strange interaction between autoyast and NFSv4. If I don't put an NFS section in my profile, it apparently keeps things at their defaults, including NFS4_SUPPORT="yes" in /etc/sysconfig/nfs, without any sysconfig entries for this. However, if I include an nfs client section which configures an NFSv4 mountpoint, somehow that sysconfig setting gets set to "no", which means idmapd fails to start on boot. I tried overriding that with a sysconfig entry in my autoyast profile, but apparently whatever is incorrectly configuring NFS runs after the sysconfig settings, as the only difference adding the sysconfig setting does is generate some messages in the y2log. It appears to apply those sysconfig settings, but near the end of installation, there's this: 2010-02-01 12:11:08 <1> test(3957) [YCP] clients/installation.ycp:58 === installation === 2010-02-01 12:11:08 <1> test(3957) [ncurses] YNCursesUI.cc(~YNCursesUI):113 Stop YNCursesUI 2010-02-01 12:11:08 <1> test(3957) [ui-macro] YCPMacroRecorder.cc(closeMacroFile):109 Macro recording done. 2010-02-01 12:11:08 <1> test(3957) [ncurses] NCurses.cc(~NCurses):149 Shutdown NCurses... 2010-02-01 12:11:08 <1> test(3957) [ncurses] NCurses.cc(~NCurses):168 NCurses down 2010-02-01 12:11:08 <1> test(3957) [wfm] WFMSubAgent.cc(~WFMSubAgent):41 Deleting SubAgent: 0 scr 2010-02-01 12:11:08 <1> test(3957) [wfm] WFMSubAgent.cc(~WFMSubAgent):41 Deleting SubAgent: 1 scr 2010-02-01 12:11:08 <1> test(3957) [liby2] Y2ProgramComponent.cc(result):159 Sending result: `result (nil) 2010-02-01 12:11:08 <1> test(3957) [liby2] Y2ProgramComponent.cc(result):159 Sending result: `result (nil) 2010-02-01 12:11:08 <1> test(3957) [liby2] Y2ProgramComponent.cc(result):159 Sending result: `result (nil) 2010-02-01 12:11:08 <2> test(3957) [agent-ini] IniParser.cc(UpdateIfModif):906 Data file '/etc/sysconfig/nfs' was changed externaly! 2010-02-01 12:11:08 <1> test(3957) [liby2] Y2ProgramComponent.cc(result):159 Sending result: `result (nil) 2010-02-01 12:11:08 <1> test(3957) [wfm] WFMSubAgent.cc(~WFMSubAgent):41 Deleting SubAgent: -1 ag_system 2010-02-01 12:11:08 <1> test(3957) [liby2] genericfrontend.cc(main):777 Finished YaST2 component 'y2base' 2010-02-01 12:11:08 <1> test(3957) [liby2] genericfrontend.cc(main):782 Exiting with client return value '`next' Apparently the "external" change to that file is my autoyast sysconfig setting, as I don't get that message without it. The things just before this in the y2log are running my post-install scripts (which include [ab]using Perl to set the domain in idmapd.conf, since there's apparently no autoyast or sysconfig setting for that) and then SuSEconfig. Since that "changed externaly [sic]" message occurs after post-scripts, I have a feeling trying to set the sysconfig value with "perl -pi -e 's/^(NFS4_SUPPORT=).*/\1"yes"/' /etc/sysconfig/nfs" in a post-script would get overriden also. Is there a setting I am missing somewhere, or have I just hit a bug? I didn't find any "enable NFSv4" settings in autoyast docs or the schemas. Note: I am not installing via NFSv4, just attempting to configure mountpoints. The installation source and autoyast are both over http. autoyast profile: ==== <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <classes config:type="list"> <class> <class_name>std</class_name> <configuration>files.xml</configuration> </class> [more classes snipped] <class> <class_name>zope</class_name> <configuration>nfs.xml</configuration> </class> <class> <class_name>zope</class_name> <configuration>software.xml</configuration> </class> <class> <class_name>std</class_name> <configuration>sysconfig.xml</configuration> </class> </classes> </profile> ==== classes/zope/nfs.xml (generated via 'yast2 autoyast') : ==== <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <nfs config:type="list"> <nfs_entry> <mount_point>/nfs/zope</mount_point> <nfs_options>defaults</nfs_options> <server_path>nfs.vpr.int:/zope</server_path> <vfstype>nfs4</vfstype> </nfs_entry> </nfs> </profile> ==== classes/std/sysconfig.xml: ==== <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>DAILY_TIME</sysconfig_key> <sysconfig_path>/etc/sysconfig/cron</sysconfig_path> <sysconfig_value>04:00</sysconfig_value> </sysconfig_entry>  <sysconfig_entry> <sysconfig_key>WRITE_HOSTNAME_TO_HOSTS</sysconfig_key> <sysconfig_path>/etc/sysconfig/network/dhcp</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>NFS4_SUPPORT</sysconfig_key> <sysconfig_path>/etc/sysconfig/nfs</sysconfig_path> <sysconfig_value>yes</sysconfig_value> </sysconfig_entry> </sysconfig> </profile> ==== The other sysconfig settings are applied correctly. As mentioned earlier, if I leave out the NFS section, /etc/sysconfig/nfs is correct. Thanks, Andrew Daugherity Systems Analyst Division of Research & Graduate Studies Texas A&M University -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [opensuse-autoinstall] NIC disappears on PXE booted suse client after TFTP.
by Colin Topliss 01 Feb '10

01 Feb '10

Hi all, Under Unix (and Linux), // gets interpreted as a / so it shouldn't matter. Regards Colin. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 01 February 2010 11:37 To: opensuse-autoinstall(a)opensuse.org Subject: Re: [opensuse-autoinstall] NIC disappears on PXE booted suse client after TFTP. on Monday 01 February 2010 Simon Loewenthal/NL/Tele2 wrote: > When I try a PXE boot it DHCPs the address and downloads the SP3 > initrd, and now the network cards appear, but it falls back to an > "Activating manual install..." menu. I thought that it could not > download the autoinst.xml from the NFS share, no, if you see that message, AutoYaST has not even tried to read the XML profile. It can not read the installation system. > The PXE file contains: > /tftpboot/pxelinux.cfg/01-d8-d3-85-5a-83-38.sles10_SP3_x86_64: > > default SLES10_SP3_x86_64 > # install SLES10_SP3 - generic profile label SLES10_SP3_x86_64 > kernel sles10_sp3_x86_64/linux > append initrd=sles10_sp3_x86_64/initrd ramdisk_size=65536 > install=nfs://10.205.8.145/export//export/sles10sp3_x86_64 is the "export//export" really correct? -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Black Heart [alpha]" by Edge Of Dawn -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org Ericsson Limited Registered Office: Unit 4, Midleton Gate, Guildford Business Park, Guildford, Surrey, GU2 8SG Registered Number in England and Wales: 942215 This communication is confidential and intended solely for the addressee(s). Any unauthorised review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. Ericsson Limited does not enter into contracts or contractual obligations via electronic mail, unless otherwise agreed in writing between the parties concerned. E-mail including attachments is susceptible to data corruption, interruption, unauthorised amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

[opensuse-autoinstall] NIC disappears on PXE booted suse client after TFTP.
by Simon Loewenthal/NL/Tele2 01 Feb '10

01 Feb '10

Dear all, I am trying to solve a strange networking problem with PXE boot and SUSE. Here follows a description with the strange ARP broadcast noted at the end: 1) PXE boot the 10.205.8.253 (new server to install) 2) DHCPOFFER to 10.205.8.253 and this then sends a DHCPACK. 3) 10.205.8.253 then TFTP downloads the linux and initrd and executes it successfully. 4) Afterwards 10.205.8.253 looses all the network information. 5) The final messages (Xensourc) shown in Ethereal are ARP requests that come from 10.205.8.253. This is the autoyast server ARPing for the MAC of 10.205.8.253 because it has disappeared from the network. No. Time Source Destination Protocol Info 15120 22.480085 Xensourc_33:3f:cc d8:d3:85:5a:00:b0 ARP Who has 10.205.8.253? Tell 10.205.8.145 At this point the PXE booted system 10.205.8.253 then reverts to the screen for starting a manual set-up programme. "Could not find ... the Installation Source. Activating manual setup program." When I use this to display the network interfaces then it only displays the loopback. This problem is not specific to one server. It happens on all servers. The servers consist of existing HP c-class blades, and some newer G6 blades. I tried a CD installation on the former blades and this works, but Suse does not see the NIC on the newer G6 blades. I do know that the firmware for the OA on the HP c7000 was upgraded this week, it all worked last week, but this is process of elimination because, as ever, one has to prove to others that this is or is not a cause because otherwise the firmware won't be rolled back. Does anyone know where I would start? Perhaps, I could load modules during the PXE boot for the server NIC? Unsure how or whether this is the right path to start down. Yours sincerely, s. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 6

[opensuse-autoinstall] Is there a Package Resolver pre-flight check
by Simon Loewenthal/NL/Tele2 27 Jan '10

27 Jan '10

Dear folks, Is there a programme I can run that will verify that the packages in a customised autoinst.xml file are correct and won't fail the package resolver? Best wishes, S. -- Simon Loewenthal/Tele2 GSM: +31 6 2000 5427 ******** IMPORTANT NOTICE ******** Please repect the X-Reply to klunky.co.uk. PGP available 0xD86A5A17. S/MIME PKCS12 key available for Lotus Notes: Please ask me for it. This e-mail (including any attachments) may contain information that is confidential or otherwise protected from disclosure and it is intended only for the addressees. If you are not the intended recipient, please note that any copying, distribution or other use of information contained in this e-mail (and its attachments) is not allowed. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message (including any attachments) from your system. Please note that e-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be subject of unauthorized interception or other interference without the knowledge of sender or recipient. Tele2 only send and receive e-mails on the basis that Tele2 is not responsible for any such computer viruses, corruption or other interference or any consequences thereof. It ought to be obvious that my views do not represent my employer's views. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 5

Re: [opensuse-autoinstall] Config question about autoinst.xml: Automatically generating the MAC address in net-udev
by Simon Loewenthal/NL/Tele2 25 Jan '10

25 Jan '10

There are usually two NICs on each server, but only one NIC [eth0] is required when jumpstarting it from autoyast. If I remove the entry, and there are two NICs, will it default to the first NIC it finds, which hopefully with be eth0. S Uwe Gansert wrote: > on Monday 25 January 2010 Simon Loewenthal/NL/Tele2 wrote: > > >> <net-udev config:type="list"> >> <rule> >> <name>eth0</name> >> <rule>ATTR{address}</rule> >> <value>00:1c:c4:a8:27:42</value> >> </rule> >> </net-udev> >> >> i) Can I remove the lines referencing n-etudev and let autoyast use the >> first interface it happens upon or, >> > > if you only have one interface, then you can remove the complete net-udev part > from the profile. > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Config question about autoinst.xml: Automatically generating the MAC address in net-udev
by Simon Loewenthal/NL/Tele2 25 Jan '10

25 Jan '10

Dear all, The autoinst.xml has this line in it and this is normal. <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>00:1c:c4:a8:27:42</value> </rule> </net-udev> This profile is being modified so that it can be used as a genericone for many systems, but all systems have different MAC addresses, so the line would not be useful in a generic profile. i) Can I remove the lines referencing n-etudev and let autoyast use the first interface it happens upon or, ii) have the newly build machine automatically add the MAC address with a line similar to: <value>auto</value> ? I have searched a little this morning and could not come up with a lot of ideas. Yours faithfully, SL -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] <match_type>regex</match_type> -- regex support?
by Stephen Dowdy 25 Jan '10

25 Jan '10

I'm wondering *which* regex system is used here and what the constraints on its use are. Google: [ autoyast "<match_type>regex</match_type>" ] And there's precious few examples to work from. The only official example shows: <rule> <board_vendor> <match>ntel</match> <match_type>regex</match_type> </board_vendor> <result> <profile>classes/largeswap.xml</profile> <continue config:type="boolean">true</continue> <dont_merge config:type="list"> <element>partition</element> </dont_merge> </result> </rule> and the value in the <match> element doesn't even have any regex pattern, wildcard, classes, etc. >From this example, all i can infer is that a <match> element value is used as a non-anchored match string. ("match anywhere") I have seen another example showing the use of the "^" begin-of-line anchor symbol e.g. "<match>^SUSE Linux Enterprise Server</match>". But what is the full-extent of what i can use here? for my needs right now, i'd like to use <product>PowerEdge [12]850</product> to match the Dell PE 1850 and PE 2850 systems. Will this work? (i imagine i may have to escape some patterns to fit XML specification, which i'm not very familiar with, but that's just a detail) thanks, --stephen -- Stephen Dowdy - Systems Administrator - NCAR/RAL 303.497.2869 - sdowdy(a)ucar.edu - http://www.ral.ucar.edu/~sdowdy/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5