February 2010 - openSUSE Autoinstall - openSUSE Mailing Lists

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] Repository Priority
by Tim Kirby 28 Sep '11

28 Sep '11

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] OT: Centralized patch management for OpenSuse 11.x
by Ivan De Masi 14 Jan '11

14 Jan '11

Hello, someone may start to laugh now for my (OT) question, but I can't find a satisfying solution :-/ How do you manage patches, updates, etc. for your running opensuse clients (not enterprise linux, just the "regular" opensuse distribution)? Is there a way like known from M$-World (WSUS)? As I know "Zend Management Server" is not open source (and not supported any more?!). Or can the complete management only be handled with self written scripts? Thanks! Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

[opensuse-autoinstall] Adding packages to profile triggers error message
by Isaac Hailperin 07 Nov '10

07 Nov '10

Hi, I try to install sles 11 via autoyast. I did an installation from dvd, and pulled an autoyast profile. This profile works, and can be installed via pxe. Now I want to add the following packages: findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server I do this via the gui. I have also tried to do it with an editor, as the gui messed up profiles in sles10sp2. In both cases, after the first reboot, I get the errormessage: "The package resolver run failed. Please check your software section in the aut" [oyast profile] (last part invisible, I guess it should be the software section in my autoyast profile :-)) This a real problem, as I have to confirm this message, thus it stops the autoinstall process. After confirming, the autoinstall process continues. Right bevor I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)" I confirm, and can log in. Theses messages are presistend after reboot. Its annoying, but not a stopper like the first problem. Why is this? Can I avoid this? Isaac -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] general rules question
by dutchguy69 26 Jul '10

26 Jul '10

I have a working autoyast install for 11.1 without using rules. Right now I would like to introduce rules but I do not seem to understand exactly how to make this work. The current install is done by supplying information for a linuxrc info file on the kernel command line info=nfs://<ip-address>/<path>/1055_init.linuxrc The info file has several parameters defined for network access, the install and the autoyast variable autoyast: nfs://<ip-address>/<path>/1055_init.autoyast <- this is my autoinst profile below the path I have created the rules directory which includes a rules .xml file with following content <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd">  <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> # CPU_TYPE on vm's is giving same result for CPU as on real hardware we have to extend to video to understand the difference between virtual and real CPU_TYPE=`cat /proc/cpuinfo|grep 'model name'|uniq|awk 'BEGIN {FS=":"};{print $2}'` VIDEO_TYPE=`/sbin/lspci | grep "VGA compatible controller"|awk 'BEGIN {FS=":"};{print $3}'` if [ "$CPU_TYPE" == " AMD Athlon(tm) 64 X2 Dual Core Processor 4400+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host1.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host1-virtualbox.xml" fi # information for scan64-3200 elif [ "$CPU_TYPE" == " AMD Athlon(tm) 64 Processor 3200+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host2.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host2-virtualbox.xml" fi fi </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>@custom1@</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom> <script> </script> <match>*</match> <match_type>exact</match_type> </custom> <result> <profile>1055_init.autoyast</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> I have tried to change the autoyast parameter in the info file with the following values autoyast: nfs://<ip-address>/<path>/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/rules.xml Above direct reference to rules file seems to work but not as expected. When I check the box I can see that in /tmp/profile/autoinst.xml I find a copy of my rules.xml file where I'm expecting a merged profile from my 1055_init.autoyast and host2.xml information I'm not sure exactly what I'm doing wrong and even after extensive check via google haven't found the right references. I've used http://forgeftp.novell.com/yast/doc/SL11.1/autoinstall/ for documentation but it is not giving me enough detail to solve above issue. Any input would be welcomed. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

[opensuse-autoinstall] /etc/sysconfig/network/dhcp der Parameter WRITE_HOSTNAME_TO_HOSTS von "yes" auf "no" SLES11
by Dirk.Lohmann＠Bertelsmann.de 26 Mar '10

26 Mar '10

Hello, we want to set in /etc/sysconfig/network/dhcp WRITE_HOSTNAME_TO_HOSTS from "yes" to "no" in SLES11 How can wie do that with xml ? Dirk Lohmann

7 14

[opensuse-autoinstall] openSUSE11.2: resize existing & create new partitions
by Guenther Haas 23 Feb '10

23 Feb '10

Hi all! Having a lot of notebooks with existing Windows installation on which I have to install openSUSE 11.2, I have tried to resize the Windows partition automatically with autoyast before creating the linux partitions. Is this possible? Using the following doesn't work and y2log doesn't really answer my question why: <partitions config:type="list">  <partition> <partition_nr config:type="integer">1</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">2</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">3</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <resize config:type="boolean">true</resize> <size>72GB</size> </partition>  <partition> <partition_nr config:type="integer">5</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext4</filesystem> <mountby config:type="device">id</mountby> <mount>/home</mount> <size>80GB</size> </partition> <partition> <partition_nr config:type="integer">6</partition_nr> <partition_id config:type="integer">130</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <mountby config:type="device">id</mountby> <mount>swap</mount> <size>4GB</size> </partition> <partition> <partition_nr config:type="integer">7</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext4</filesystem> <mountby config:type="device">id</mountby> <mount>/</mount> <size>max</size> </partition> </partitions> </drive> </partitioning> Using olny the first part works, although I thought, autoyast would complain about the missing linux partition. But it works, at least until starting the real installation: <partitions config:type="list">  <partition> <partition_nr config:type="integer">1</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">2</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">3</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <resize config:type="boolean">true</resize> <size>72GB</size> </partition> </partitions> </drive> </partitioning> As soon as I add an additional partition, which uses the new diskspace, won by resizing the existing Windows 7 partition, the whole installations stops with an error. Even if I only ad one partition of the three given above. Any idea? Next idea was, that I could only have the resizing part in the autoyast config, then manually add the linux partitions before starting the real installation and after that checking /var/adm/autoinstall/cache/installedSystem.xml so see, what I have to enter in my autoyast config. But this doesn't work. There, I can only find what already was given in the configuration, not what I changed later manually. So it's not really the config of the "installedSystem". :-( Regards, -- Guenther Haas, Uni Ulm, Institut TAIT, guenther.haas(a)gmx.de

2 5

[opensuse-autoinstall] package yum is not found by autoyast
by Magyari, Miklos 19 Feb '10

19 Feb '10

hi, I'm working with SLED11 and have an autoyast file containing (among lots of other stuff): <package>yum</package> it was working perfectly until I have added several new updates to my updatesource (there is no update for yum package itself). Since that autoyast complains that it cannot find the pacakge yum. Checking apache logs suggests that it doesn't even try to fetch it, just concludes that it does not exist at all. I'm lost on what went wrong. After copying the updates to updatesource, I have executed create_package_descr and create_sha1sums as usual (I have a script for this, completely unchanged). The only real change is that number of packages in updatesource increased as several packages has different versions/releases present paralelly. Do anyone has a pointer where to look for the problem? thanks in advance, Miki -- 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] ayast_setup and script status posibilities
by R.E. van Holk 19 Feb '10

19 Feb '10

Hi, We are currently developing a SLES 11 setup which is run on vmware. We do not install the systems by installserver but just deploy vmware templates (clones ) on the vm's. These clones have all needed rpm's and products installed, but do not have any configuration. So in the boot process of the clone , we call a scripts which collects a prepared autoyast profile from an webserver and runs the profile using the ayast_setup procedure. So far so good , it al works and the whole system and all components are configured properly. But to make all the configuration stuff work , we have added a bunch of scripts to the autoyast profile which needs to run at the end of the ayast_setup procedure. This also works fine. The problem we have is that the script processing might take a great deal of time, during that period the status bar of ayast_setup is at 100 % all of the time. There is no status at all shown on which script is run at the moment or what is happening. I know I could turn on the option which shows the stdin and stdout , but this also asks for user confirmation to continue. So my question is : Is there a way with SLES11 autoyast profiles to produces pop-ups or something similar , without any required user input ? ( we don't want any user input , the process should be fully unattendend ) We have about 20 scripts running from autoyast right now , the total time they take to complete is now 30 minutes, that's the reason why we would like to show somehow that there is something actually runnning. Any help is appreciated. Ron -- 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] How to remove a section using XSLT?
by Uwe Gansert 15 Feb '10

15 Feb '10

on Wednesday 10 February 2010 Erico Mendonça wrote: > >> I m using a <ask> dialog on my autoyast file to ask the user for the > >> desired profile. However, it will go into a loop (ask the same > >> information again) when it's reloaded by autoyast. > > > > why? has your chosen profile the same ask-list again? > > Oops. You're right. :) > > Anyway, removing a section via XSLT could be useful later on. Do you > have any ideas on that? I dont think you need that very often but here is how you can solve that with xslt. The problem in your xslt file was the missing namespace (I called it "y" here) <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet· xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:y="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" version="1.0"> · <xsl:template match="*|processing-instruction()|comment()"> <xsl:copy> <xsl:copy-of select="@*"/> <xsl:apply-templates/> </xsl:copy> </xsl:template> <xsl:template match="y:ask-list"> </xsl:template> </xsl:stylesheet> -- 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(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Installing SLES 10 SP3 from local disk does not work
by Enamul Haque 12 Feb '10

12 Feb '10

I am trying to install SLES 10 SP3 from local disk. Lilo gives following warning when I configure lilo to boot with the imaging kernel: Added Linux * Warning: The initial RAM disk is too big to fit between the kernel and the 15M-16M memory hole. It will be loaded in the highest memory as though the configuration file specified "large-memory" and it will be assumed that the BIOS supports memory moves above 16M. Added Reimaging ? The size of the initrd that comes with SLES 10 SP3 it 10585 kb. It is slightly larger than the initrd that comes with SLES 10 SP2. Installing SLES 10 SP2 from local disk works fine. Therefore, I think the issue is related to the size of the initrd. Does anyone a workaround of the issue? TIA, Enamul -- 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] SLES9 SP4 & autoyast - unable to configure static ip - end up with dhcp.
by Hans-Joachim Ehlers 12 Feb '10

12 Feb '10

QEFsbCwNCkkgdHJ5aW5nIHRvIGluc3RhbGwgU0xFUzkgU1A0IGluIGFuIEVTWCAzLjUgVk0gLSBidXQgbmVpdGhlciBob3N0bmFtZSBub3IgSVAgYXJlIHNldCBidXQgdGhlIC9ldGMvc3lzY29uZmlnL25ldHdvcmsvZGhjcCBpcyBhY3RpdmUuDQoNCkJ1dCBkaGNwIGl0IG5vdCBjb25maWd1cmVkIGluIGFueSB4bWwgZmlsZSBub3Igb24gdGhlIGNvbW1hbmQgbGluZS4NCkkgY2FuIHNlZSBpbiB0aGUgeTJsb2cgdGhhdCB0aGUgbW9kdWxlICJuZXR3b3JrL2luc3RhbGwueWNwIiBjb25maWd1cmVzIHRoZSBESENQIGZvciBzb21lIHVua25vd24gcmVhc29uOg0KDQpFeHRyYWN0IGZyb20gdGhlIGxvZzoNCi4uLg0KTmV0d29yay9pbnN0YWxsLnlwOjEwNiBJbnN0YWxsSW5mKCRbYm9vdHByb3RvIjoiZGhjcCIsIC4uLi4uLg0KDQpTbyAgYXV0b3lhc3QgdHJpZXMgdG8gY29uZmlndXJlIHRoZSBuZXR3b3JrIGZvciBkaGNwLiA/Pz8/Pz8NCg0KSW5mbzoNCkluc3RhbGxhdGlvbiBjb21tYW5kIGxpbmUgKCBQWEUgQm9vdCkNCi4uLiANCiAga2VybmVsIHNsZXM5L2tlcm5lbA0KICBhcHBlbmQgaW5pdHJkPXNsZXM5L2luaXRyZCByYW1kaXNrX3NpemU9NjU1MzYgc3BsYXNoPXZlcmJvc2Ugc2hvd29wdHMgdGV4dG1vZGU9MSBpbnN0bW9kZT1odHRwIGluc3RhbGw9aHR0cDovLzEwLg0KMTEuOC4zL2V4cG9ydC9zdXNlL3NsZXM5LyBhdXRveWFzdD1odHRwOi8vMTAuMTEuOC4zL2V4cG9ydC9zdXNlL3NsZXM5L2F1dG9pbnN0YWxsLyBuZXRkZXZpY2U9ZXRoMA0KLi4uDQoNClRodXMgdGhlIHF1ZXN0aW9uLg0KQ2FuIHNvbWVib2R5IHN1cHBseSBhIHdvcmtpbmcgbWluaW1hbCBuZXR3b3JrIHNlY3Rpb24gZm9yIGF1dG95YXN0IGZvciBTTEVTOSBTUDQgPw0KDQpUaWENCkhham8NCg0KLS0NCiBIYW5zLUpvYWNoaW0gRWhsZXJzDQogVU5JWCBTeXN0ZW1zIEVuZ2luZWVyDQogRVVNRVRTQVQNCiBFdW1ldHNhdC1BbGxlZSAxDQogNjQyOTUsIERhcm1zdGFkdCwgR2VybWFueQ0KIFRlbCA6ICs0OSA2MTUxIDgwNy03MzA3DQogbWFpbHRvOmhhbnNqb2FjaGltLmVobGVyc0BldW1ldHNhdC5pbnQNCiBodHRwOi8vd3d3LmV1bWV0c2F0LmludA0KDQoNCg0K-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.orgFor additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

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

11 Feb '10

Uwe Gansert wrote: > on Monday 08 February 2010 Simon Loewenthal/NL/Tele2 wrote: > > >> 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). │ >> >> I am unsure what this means. I do not rememver adding this. >> > > that means that a either a second yast is running that locks the storage > system. Is stage2 maybe still running? > > >> On another system I saw a similar message about some scsi subsystem not >> beong installed. >> > > that's a bug in autoyast2. That iscsi-client modules requires one or two > packes to be installed. Simply install those to suppress that message, even if > you dont need iscsi. > Not nice but fixed in the meantime. > > OK no problem then. I shall ignore it or install the module. Interestingly, on a OpenSUSE 11 server I had the message: # yast2 clone_system No such client module clone_system The search path follows. It does not include the current directory. /y2update/clients /root/.yast2/clients /usr/share/YaST2/clients Run 'yast2 -h' for help on usage # Does anyone know which package is missing? Additionally, on some systems the command produces: UI Syntax Error │ ──────────────────┐ │No widget with ID `contents│ │ The resulting autoy│ Check the log file! │ └────────────────────│ ──────────────────┘ └───────────────────────────┘ Odd. 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] How to remove a section using XSLT?
by Erico Mendonça 10 Feb '10

10 Feb '10

Hi there... I m using a <ask> dialog on my autoyast file to ask the user for the desired profile. However, it will go into a loop (ask the same information again) when it's reloaded by autoyast. So far I managed to avoid the loop by removing the <ask-list> section before the XML is reloaded by crude means (sed). However, I really would like to use xsltproc to do it. What should I use on my XSL file to accomplish that? I tried this code: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl=" http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes"/> <xsl:template match="node() | @*"> <xsl:copy> <xsl:apply-templates select="node() | @*"/> </xsl:copy> </xsl:template> <xsl:template match="ask-list"/> </xsl:stylesheet> But it appears to get confused by the "!DOCTYPE profile" and the main "profile" tags. If I remove those and add a generic tag, this stylesheet works. Any ideas? -- -- Erico -- 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] 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