- openSUSE Autoinstall

[opensuse-autoinstall] Comments in XML
by Marcus Moeller 26 Mar '10

26 Mar '10

Hi all. Are comments allowed in AutoYaST's XML File (e.g. using heading #)? Best Regards Marcus -- 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] little bug in docu
by Marcus Moeller 26 Mar '10

26 Mar '10

Hi. There is a little bug in the documentation: http://www.suse.de/~ug/autoyast_doc/createprofile.scripts.html 4.16.2 The following elements must be between the <scripts><postpartitioning-scripts config:type="list"><script> ... </script></postpartitioning-sripts>...</scripts> tags should be: The following elements must be between the <scripts><postpartitioning-scripts config:type="list"><script> ... </script></postpartitioning-scripts>...</scripts> tags Best Regards Marcus -- 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] Command exited with status 127
by Marcus Moeller 26 Mar '10

26 Mar '10

Hi all. I have now set up the installation environment correctly but installation fails with an error: Command exited with status 127 Is there a way to debug which component fails? Best Regards Marcus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Installation Sources
by Marcus Moeller 25 Mar '10

25 Mar '10

Hi all, I am quite new to autoyast, but trying to deploy openSUSE 11.2 Just wanted to know if it's possible to define a set of installation repositories, e.g. initial installation should be done via an official oS mirror, and additional packages should be installed from buildservice repos. Best Regards Marcus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

RE: [opensuse-autoinstall] Installation Sources
by Hans-Joachim Ehlers 25 Mar '10

25 Mar '10

>> Current best practise for me: >> >> 1) Have a local mirror of the later used - external - repositories >> In case the external side has removed the repo ( like for OS 10.3) you have a local one :-) >> 2) During autoyast installation only the images from the official release incl. Updates is used >> So how do you mangage the install repo? oS provides a repo for the >> initial installation and one for updates. >Do you merge these packages to one directory which is then given as >install= parameter? I never mess around with the repros created from the DVD or with update repos because it must work every time .... Thus in conjunction with the base OS repro i added a update location to the autoinst.xml In the example the update was an mirror from a external side ( As of 2009/11/06) . For SLES versions i mirror novell and/or use the SP images as well Example: ..... <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <add-on> <add_on_products config:type="list"> <listentry> <media_url>http://10.1.1.13/export/mirror/20091106/ftp5.gwdg.de/pub/opensuse/update/11…</media_url> <product>SuSE-Linux-Updates</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> <bootloader> .... .... Cheers Hajo -- 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] Here, Surprise!
by naveen penumala 19 Mar '10

19 Mar '10

Here, Surprise! I know a company has a promotion now,so I hope to introduce it to you.RIC is a good company.Now you can purchase their products at 20% discount,but this activity only lasts 30 days.It only took 5 days for me to receive my product.If you need electronic products,please visit www.rictradeooo.info I guarantee you will get a satisfactory result. Have a good day! marine26 -- 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] multiple autoyast bugs in opensuse 11.2?
by Mike Coleman 17 Mar '10

17 Mar '10

Hi, I'm working on an autoyast install for opensuse 11.2, and running into what seems like a lot of bugs in autoyast. Am I doing something wrong? Here are the ones I can recall: * My 'services' block seems to be ignored entirely. In particular, I'm unable to start sshd this way. * For each kind of script, only the first one seems to be run. That is, if I provide two post-scripts, the second isn't being run. It seems like they all should be run. * The proposal page doesn't completely match what actually happens. For example, if I disable the firewall, it's still described as enabled there. (It also doesn't notice that I'm turning on sshd, though that could be due to some other problem.) * I've tried adding blocks for kerberos and samba configs, but these seem to be ignored completely. * The 'networking' block needs more documentation on how to set up static addresses. Are others seeing these problems? Should I be filing bug reports for them? Mike -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 13

[opensuse-autoinstall] Problems with mkinitrd
by 686f6c6d 16 Mar '10

16 Mar '10

Greetings, I'm having an issue with mkinitrd during autoyast installation (see attached screenshots for the error message). I'm installing on virtual machines, using an image of a bought 11.2 DVD to boot. The rest of the installation happens over a local HTTP-based repository[0], the autoyast files are on the same host. Weird thing is, the problem only appears during autoyast installation and not when doing a manual install from the same DVD image. (So the image should be fine.) The autoyast profile, on the other hand, is based on one that worked fine with 11.1 and broke the instant we installed 11.2 from it[1]. (So the profile should be fine.) I've been triple-and-more-checking it for errors but have found none so far (I will attach a made-anonymous version around tomorrow, I can't access the machines right now). I haven't found any clue in the log files as to where the problem is. I've been using "confirm", have switched to the second console when the error brings the install to a screeching halt, looked at the end of the log files, nothing. No errors at all. It seems the problem really is in the mkinitrd rpm (or the arguments it is being called with); however, it works fine after installing (IIRC, the version during and after install are the same), and even the autoinstalled files work fine after punching away those error messages. (Still, it's a nasty showstopper for an unattended installation.) I haven't found any bugs resembling the issue and couldn't find anybody on the internet having this problem (except some less-than-useful comments[2]). Is this a known issue? What can I do to isolate the problem? I'm thankful for ANY suggestion at this point. Otherwise my next, desperate attempt might be to create a postpartitioning-script or chroot-script to patch debug output into the mkinitrd-related shellscripts. tty, 686f6c6d 0: IIRC, I assumed it could be a local problem and verified that the versions are the same as in the official repos. I will check that again. 1: Of course, what I mean is we slighty modified our existing profile. After creating a fresh reference profile, we merged our old settings into the new profile. With a different incarnation with no differences in the relevant - bootloader etc. - sections whatsoever (IIRC, will check again), the problem does not occur. There, however, we boot over PXE, a scenario that is not practical with the setup where the problem occurs. 2: http://news.opensuse.org/2009/10/15/opensuse-11-2-on-its-way-to-become-fina… (search the page for "illegal option" or "Kazuya")

2 2

Re: [opensuse-autoinstall] sles 11 install - mount by UUID for has issues
by Andrew Daugherity 11 Mar '10

11 Mar '10

On Thu, 2010-03-11 at 16:53 +0100, Uwe Gansert wrote: > on Thursday 11 March 2010 D. Bahi wrote: > > please open bug reports for those, except for the one with the missing mountby > while cloning. That's already fixed > (https://bugzilla.novell.com/show_bug.cgi?id=557759) [somewhat OT] I can't see that bug, or many others for that matter. (Seems that any bug that applies to SLES, even if it also applies to OpenSUSE, is marked private.) Is there a way to gain (read) access to these bugs, or are they intentionally restricted to Novell employees only? I use my same Novell account at both bugzilla and Novell customer center, where I can see my SLES registration codes, license usage, etc., so I should have the "SLES access bit", if one exists. I realize some reports need to be private, e.g. if they contain confidential customer data, unreleased security patches, etc., but this does not apply to most bugs. It's frustrating to read a BNC# in zypper patch-info or rpm changelog and not be able to see what those are referring to. I think this one area handled better by RHEL, as most of their bugzilla is public, even security bugs (after they have released their advisory and updates, of course -- they are private before then). Andrew -- 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] sles 11 install - mount by UUID for has issues
by D. Bahi 11 Mar '10

11 Mar '10

hello all, note attached to avoid line wrapping. thank you, dbahi

2 1