- openSUSE Autoinstall

[opensuse-autoinstall] Install issues
by Anthony Hare 09 Mar '10

09 Mar '10

I have a couple issues - Installing Suse Ent 11. 1) My partitioning - <partitioning config:type=3D"list"> <drive> <use>all</use> </drive> </partitioning> On a Dell 2950 and an IBM x3250 it says creating 2gb (super long string) sw= ap.. Then creating raid partition (super long string for /) error code -3030.. I= t works for other newer sas drives in x3650's etc.. 2) On my x3650 it installs but during initial boot it doesn't start network= ing (fails configuring the correct NIC as eth0, it trys eth0_ncs) so it tri= es to get package sles release from my http://install location and fails due to lack of networking.. Anyway around this? 3) Trying to execute a custom .sh script to configure (hostname/static ip/e= tc). I have been unable using the post-script or init-script portion of aut= oyast.. Is there a way to insert the script for initial boot? Say /post.sh echo "/post.sh" >> /etc/init.d/boot.local -- 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] VNC, openSuSE 11.2
by Folkhard Mueller 09 Mar '10

09 Mar '10

Daer All, Can it be that I am the only one, who cannot remote install anymore via VNC in openSuSE 11.2 In openSuSE 10.3 it worked perfectly. In openSuSE 11.2 only VNC is anounced with slp, but no VNCserver will be started at the target machine to be installed. Any hints out there ? Best Regards, F.Mueller -- |\ _,,,---,,_ ZZZzz /,`.-'`' -. ;-;;,_ _______|,4- ) )-,_. ,\ (____-'_________________________________________ '---''(_/--' `-'\_) Best regards, *Folkhard Müller* Engineer Research & Development *EPCOS AG* A Group Company of TDK-EPC Corporation Research & Development · Systems, Acoustics, Waves Division Office: Anzinger Strasse 13 · 81671 Munich Post: P.O.Box 80 17 09 · 81617 Munich · Germany Telephone: +49-89-636 23316 Fax: +49-89-636 24339 mailto: folkhard.mueller(a)epcos.com <mailto:folkhard.mueller@epcos.com> www.tdk.co.jp <http://www.tdk.co.jp> · www.epcos.com <http://www.epcos.com> Headquarters: Munich · Commercial register of the local court (Amtsgericht): Munich · HRB 127250 Chairman of the Supervisory Board: Klaus Ziegler Management Board: Gerhard Pegam, President & CEO · Joachim Zichlarz · Dr. Werner Faber -- 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] 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