Sorry for reviving an old topic, but there are still some serious problems with autoyast on 13.1.
I have converted a 12.3 profile to 13.1 and hit the exact "add-on" bug mentioned previously, but it was fixed by the DUD provided in the BNC mentioned. However, there are still issues regarding the sysconfig sections (null values) and user creation (the users are created with empty password fields, with or without using encryption in the XML), and possibly others. There's also the question of a broken second stage, which in some cases will not be executed at all.
I found a bug (845296) for the sysconfig problem back in RC2. I updated the version to GA, commented on it and provided the missing logs, but no one picked it up yet. For the other two problems, there is an open bug for SLES 12 beta autoinstall (888936).
So, if anyone else is working on getting a solution for these over here, please let me know, or update the bugs I mentioned above. Maybe we can do a joint effort to solve these?
2014-01-30 12:46 GMT-02:00 Ivan De Masi firstname.lastname@example.org:
Am 30.01.2014 12:18, schrieb Thomas Fehr:
On Thu, Jan 30, Ivan De Masi wrote:
wouldn't a independant autoyast-repository make sense for quicker fixing and updating?!
A OS 13.1 rollout of clients and servers with these bugs in autoyast is hard to do, when you always have to be aware if the tool that should help and ease a roolout needs "help" too. ;-)
The fix for this needs to be in installation media, so having the fixed package in a repository where it gets installed from would not help to avoid this bug.
OK, thanks for this explanation. I was wondering for a while...
As I already wrote in my answer to Joschi, there is a driver update disk attached to https://bugzilla.novell.com/show_bug.cgi?id=846011 which avoids the problem.
you just need to use e.g.
netsetup=dhcp autoyast=http://10.120.4.28/autoinst.xml dud=http://10.120.4.28/bnc_846011_131.dud
as kernel boot commandline (of course with URLs adapted ;-) and place the DUD where you get the autoyast control file from. Since I assume, most of you have means to avoid typing the parameters manually (e.g. PXE boot, modified isolinux.cfg on install medium, whatever) it ist just a one-time change in setup that can be used for all 13.1 based installations.
Also thanks for this! I will try it (hopefully soon) and report.
Regards, Ivan -- To unsubscribe, e-mail: email@example.com To contact the owner, e-mail: firstname.lastname@example.org