Hi everyone,
sorry for asking such a general question, but what is the state of AutoYast for OpenSUSE 13.1?
I converted a completely working XML from a 12.3 installation to 13.1.
The autoinstallation finishes, but the installed system is - missing Sysconfig configuration from <sysconfig> section - has not run any of the <post-scripts> and <init-scripts> - does not accept the root password configured in the <users> section - is missing all files installed from the <files> section of the XML - misses LDAP and KRB config from <ldap> and <kerberos> - services are not configured as in <services> and many more problems.
To me it looks like the complete second stage is missing, as all those things are done there.
Is this a known problem? Or are there known problems for 13.1?
Did anyone succeed with AutoYast and 13.1 with any of the above mentioned XML sections?
The y2log file from second stage is very small and does not show any errors...
Best regards, Joschi Brauchle
On Thu, Jan 30, 2014 at 10:40 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Is this a known problem? Or are there known problems for 13.1?
This is a known bug (BNC# below), it was discussed on this ML a few weeks back. You need to remove your <add-on> section completely.
It is "fixed" already, but fixed in the case of AutoYAST sadly always means "only fixed in the next release", even for crippling bugs like this, that affects every single user. For that particular problem I'm using the following <post-script>:
---------- 8< ---------- <!-- workaround for BNC#846011 (fixed for 13.2 since ~2014-01-26) --> <script> <network_needed config:type="boolean">true</network_needed> <filename>post-manual-repos</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/bash # doesn't work in pre: read-only fs.
# install repo is added by install= cmdline param.
echo "[suse_update] name=SUSE updates (13.1) enabled=1 autorefresh=1 baseurl=http://repohost/suse/update/13.1/ type=rpm-md gpgcheck=1 gpgkey=http://repohost/suse/update/13.1/repodata/repomd.xml.key" >> /etc/zypp/repos.d/update.repo
echo "[something_stable] name=something (13.1) enabled=1 autorefresh=1 baseurl=http://repohost/acmecorp/something:/stable/openSUSE_13.1/ type=rpm-md gpgcheck=1 gpgkey=http://repohost/acmecorp/something:/stable/openSUSE_13.1/repodata/repomd.xml..."
/etc/zypp/repos.d/something.repo
]]></source> </script> ---------- >8 ----------
I don't remember any new problems in 13.1 from the top of my head right now (maybe the problem with empty resolv.conf I had in 12.x now happens in an earlier stage, not sure). Will post if I find something, our profiles are quite huge nowaways.
Hi Joschi,
On Thu, Jan 30, Joschi Brauchle wrote:
Hi everyone,
sorry for asking such a general question, but what is the state of AutoYast for OpenSUSE 13.1?
I converted a completely working XML from a 12.3 installation to 13.1.
The autoinstallation finishes, but the installed system is
- missing Sysconfig configuration from <sysconfig> section
- has not run any of the <post-scripts> and <init-scripts>
- does not accept the root password configured in the <users> section
- is missing all files installed from the <files> section of the XML
- misses LDAP and KRB config from <ldap> and <kerberos>
- services are not configured as in <services>
and many more problems.
To me it looks like the complete second stage is missing, as all those things are done there.
Is this a known problem? Or are there known problems for 13.1?
From the description it sound like bnc#846011 .
If you have repositorities configured in the <add-on> section, there is a bug in the client handling these that leads to a creash of yast late in the first stage of installation. This crash prevents the file with setup information for second stage to be written, and therefore all configuration steps happening in second stage are not done.
In bnc#846011 I attached a driver update disk, the fix itself is in brnanch openSUSE-13_1 of git@github.com:yast/yast-add-on.git
Tschuess, Thomas Fehr
Am 30.01.2014 11:26, schrieb 686f6c6d:
On Thu, Jan 30, 2014 at 10:40 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Is this a known problem? Or are there known problems for 13.1?
This is a known bug (BNC# below), it was discussed on this ML a few weeks back. You need to remove your <add-on> section completely.
It is "fixed" already, but fixed in the case of AutoYAST sadly always means "only fixed in the next release", even for crippling bugs like this, that affects every single user.
Hello,
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. ;-)
Regards, Ivan
Hi Ivan,
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.
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.
Bye, Thomas Fehr
Thank you so much for the info!
In the mentioned BNC 846011, there is a DUD provided that is supposed to fix the problem.
Unfortunately, I can *NOT* confirm that the DUD fixes the problem. I can see it gets fetched at the very start of AutoYast, but then everything is then same.
Should there be any sign of the DUD in y2log(-1) ? Because there is nothing there...
On 01/30/2014 11:26 AM, 686f6c6d wrote:
On Thu, Jan 30, 2014 at 10:40 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Is this a known problem? Or are there known problems for 13.1?
This is a known bug (BNC# below), it was discussed on this ML a few weeks back. You need to remove your <add-on> section completely.
It is "fixed" already, but fixed in the case of AutoYAST sadly always means "only fixed in the next release", even for crippling bugs like this, that affects every single user. For that particular problem I'm using the following <post-script>:
---------- 8< ---------- <!-- workaround for BNC#846011 (fixed for 13.2 since ~2014-01-26) --> <script> <network_needed config:type="boolean">true</network_needed> <filename>post-manual-repos</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/bash # doesn't work in pre: read-only fs.
# install repo is added by install= cmdline param.
echo "[suse_update] name=SUSE updates (13.1) enabled=1 autorefresh=1 baseurl=http://repohost/suse/update/13.1/ type=rpm-md gpgcheck=1 gpgkey=http://repohost/suse/update/13.1/repodata/repomd.xml.key" >> /etc/zypp/repos.d/update.repo
echo "[something_stable] name=something (13.1) enabled=1 autorefresh=1 baseurl=http://repohost/acmecorp/something:/stable/openSUSE_13.1/ type=rpm-md gpgcheck=1 gpgkey=http://repohost/acmecorp/something:/stable/openSUSE_13.1/repodata/repomd.xml..."
/etc/zypp/repos.d/something.repo
]]></source> </script> ---------- >8 ----------
I don't remember any new problems in 13.1 from the top of my head right now (maybe the problem with empty resolv.conf I had in 12.x now happens in an earlier stage, not sure). Will post if I find something, our profiles are quite huge nowaways.
Hello Thomas,
sorry for my multiple simultaneous answers.
So my first try with the DUD was not successful. I can see a line at the very start of the installation process about it being loaded. But then there is no change and no sign in y2log(-1) anywhere that the DUD was successfully applied.
How can I check or test during stage 1/2, if the DUD was correctly applied?
Thanks for your help, Joschi
On 01/30/2014 12:01 PM, Thomas Fehr wrote:
Hi Joschi,
On Thu, Jan 30, Joschi Brauchle wrote:
Hi everyone,
sorry for asking such a general question, but what is the state of AutoYast for OpenSUSE 13.1?
I converted a completely working XML from a 12.3 installation to 13.1.
The autoinstallation finishes, but the installed system is
- missing Sysconfig configuration from <sysconfig> section
- has not run any of the <post-scripts> and <init-scripts>
- does not accept the root password configured in the <users> section
- is missing all files installed from the <files> section of the XML
- misses LDAP and KRB config from <ldap> and <kerberos>
- services are not configured as in <services>
and many more problems.
To me it looks like the complete second stage is missing, as all those things are done there.
Is this a known problem? Or are there known problems for 13.1?
From the description it sound like bnc#846011 .
If you have repositorities configured in the <add-on> section, there is a bug in the client handling these that leads to a creash of yast late in the first stage of installation. This crash prevents the file with setup information for second stage to be written, and therefore all configuration steps happening in second stage are not done.
In bnc#846011 I attached a driver update disk, the fix itself is in brnanch openSUSE-13_1 of git@github.com:yast/yast-add-on.git
Tschuess, Thomas Fehr
Hi Joschi,
On Thu, Jan 30, Joschi Brauchle wrote:
Thank you so much for the info!
In the mentioned BNC 846011, there is a DUD provided that is supposed to fix the problem.
Unfortunately, I can *NOT* confirm that the DUD fixes the problem. I can see it gets fetched at the very start of AutoYast, but then everything is then same.
Hmm strange, I had the problem reproduceably here and adding the DUD fixed it for me. Unless you added insecure=1 also to kernel command line you should see a popup message with:
------------------------------------------------------ http://10.120.4.28/bnc_846011_131.dud: file not signed
If you really trust yor repository you may continue in an insecure mode ------------------------------------------------------
Of course you need to selecd "Ok" here. You can suppress this message by adding "insecure=1" to the kernel boot command line.
During package installation you should see a additional Repository called "DriverUpdate0" which is the driver update disk. If you have y2log files you could grep for "DriverUpdate0".
Maybe the the DUD got corrupted. I just downloaded it and it still has md5sum e2a9f347c784e4872192cd0800c38b4e which is the same as expected.
You can also check the content with: wotan:~ > zcat bnc_846011_131.dud | cpio -itv drwxr-xr-x 3 root root 0 Jan 28 13:27 . drwxr-xr-x 3 root root 0 Jan 28 13:27 linux drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/ia64-13.1 -> x86_64-13.1 drwxr-xr-x 4 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1 drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/install -rw-r--r-- 1 root root 37167 Jan 28 13:27 linux/suse/x86_64-13.1/install/yast2-add-on-3.0.3-4.1.noarch.rpm -rwxr-xr-x 1 root root 909 Jan 28 13:27 linux/suse/x86_64-13.1/install/update.pre -rwxr-xr-x 1 root root 190 Jan 28 13:27 linux/suse/x86_64-13.1/install/update.post2 drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr drwxr-xr-x 4 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/applications drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/applications/YaST2 -rw-r--r-- 1 root root 541 Jan 20 13:09 linux/suse/x86_64-13.1/inst-sys/usr/share/applications/YaST2/vendor.desktop -rw-r--r-- 1 root root 648 Jan 20 13:09 linux/suse/x86_64-13.1/inst-sys/usr/share/applications/YaST2/add-on.desktop drwxr-xr-x 5 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2 drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema/autoyast drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema/autoyast/rnc -rw-r--r-- 1 root root 1490 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema/autoyast/rnc/add-on.rnc drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include/add-on -rw-r--r-- 1 root root 2547 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include/add-on/misc.rb -rw-r--r-- 1 root root 60671 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include/add-on/add-on-workflow.rb drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients -rw-r--r-- 1 root root 3382 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/inst_add-on_software.rb -rw-r--r-- 1 root root 10570 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/vendor.rb -rw-r--r-- 1 root root 12845 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/inst_language_add-on.rb -rw-r--r-- 1 root root 2479 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/add-on_proposal.rb -rw-r--r-- 1 root root 4310 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/inst_add-on.rb -rw-r--r-- 1 root root 9799 Jan 17 16:51 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/add-on_auto.rb -rw-r--r-- 1 root root 4931 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/add-on.rb -rw-r--r-- 1 root root 30 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/.update.d92d43be-cc4f-4aac-ac8f-64db2ab0c14d -rw-r--r-- 1 root root 137 Jan 28 13:27 linux/suse/x86_64-13.1/dud.config lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/ppc64-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/i386-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/s390-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/s390x-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/ppc-13.1 -> x86_64-13.1 312 blocks wotan:~ >
Tschuess, Thomas Fehr
On Thu, Jan 30, Joschi Brauchle wrote:
Hello Thomas,
sorry for my multiple simultaneous answers.
I just replied to your first mail...
Tschuess, Thomas Fehr
Am 30.01.2014 12:18, schrieb Thomas Fehr:
Hi Ivan,
Hello Thomas,
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
For some reason I did not get the DUD to work correctly. It may be my fault... Anyways, I unpacked the DUD and copied all files into my OSS repository on the NFS server, leading to the equivalent effect of the DUD.
Now, Autoyast stage 2 works perfectly again! Thanks!
I have a quick followup question: --------------------- <runlevel> <default>5</default> <services config:type="list"> <service> <service_name>rpcbind</service_name> <service_status>enable</service_status> </service> </services> </runlevel> --------------------- does not work, i.e. rpcbind.service is disabled in the installed system.
In y2log I see an error message saying something like "rpcbind service does not exist, creating it" (or something along these lines, dont have the log available currently). Same happens e.g. for "xinetd", but not for "sshd", "nfs" and many others.
So why does AutoYast think that the rpcbind.service does not exist and why is it not enabled?
Thanks!
On 01/30/2014 02:33 PM, Thomas Fehr wrote:
Hi Joschi,
On Thu, Jan 30, Joschi Brauchle wrote:
Thank you so much for the info!
In the mentioned BNC 846011, there is a DUD provided that is supposed to fix the problem.
Unfortunately, I can *NOT* confirm that the DUD fixes the problem. I can see it gets fetched at the very start of AutoYast, but then everything is then same.
Hmm strange, I had the problem reproduceably here and adding the DUD fixed it for me. Unless you added insecure=1 also to kernel command line you should see a popup message with:
http://10.120.4.28/bnc_846011_131.dud: file not signed
If you really trust yor repository you may continue in an insecure mode
Of course you need to selecd "Ok" here. You can suppress this message by adding "insecure=1" to the kernel boot command line.
During package installation you should see a additional Repository called "DriverUpdate0" which is the driver update disk. If you have y2log files you could grep for "DriverUpdate0".
Maybe the the DUD got corrupted. I just downloaded it and it still has md5sum e2a9f347c784e4872192cd0800c38b4e which is the same as expected.
You can also check the content with: wotan:~ > zcat bnc_846011_131.dud | cpio -itv drwxr-xr-x 3 root root 0 Jan 28 13:27 . drwxr-xr-x 3 root root 0 Jan 28 13:27 linux drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/ia64-13.1 -> x86_64-13.1 drwxr-xr-x 4 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1 drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/install -rw-r--r-- 1 root root 37167 Jan 28 13:27 linux/suse/x86_64-13.1/install/yast2-add-on-3.0.3-4.1.noarch.rpm -rwxr-xr-x 1 root root 909 Jan 28 13:27 linux/suse/x86_64-13.1/install/update.pre -rwxr-xr-x 1 root root 190 Jan 28 13:27 linux/suse/x86_64-13.1/install/update.post2 drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr drwxr-xr-x 4 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/applications drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/applications/YaST2 -rw-r--r-- 1 root root 541 Jan 20 13:09 linux/suse/x86_64-13.1/inst-sys/usr/share/applications/YaST2/vendor.desktop -rw-r--r-- 1 root root 648 Jan 20 13:09 linux/suse/x86_64-13.1/inst-sys/usr/share/applications/YaST2/add-on.desktop drwxr-xr-x 5 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2 drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema/autoyast drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema/autoyast/rnc -rw-r--r-- 1 root root 1490 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/schema/autoyast/rnc/add-on.rnc drwxr-xr-x 3 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include/add-on -rw-r--r-- 1 root root 2547 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include/add-on/misc.rb -rw-r--r-- 1 root root 60671 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/include/add-on/add-on-workflow.rb drwxr-xr-x 2 root root 0 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients -rw-r--r-- 1 root root 3382 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/inst_add-on_software.rb -rw-r--r-- 1 root root 10570 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/vendor.rb -rw-r--r-- 1 root root 12845 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/inst_language_add-on.rb -rw-r--r-- 1 root root 2479 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/add-on_proposal.rb -rw-r--r-- 1 root root 4310 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/inst_add-on.rb -rw-r--r-- 1 root root 9799 Jan 17 16:51 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/add-on_auto.rb -rw-r--r-- 1 root root 4931 Jan 9 14:10 linux/suse/x86_64-13.1/inst-sys/usr/share/YaST2/clients/add-on.rb -rw-r--r-- 1 root root 30 Jan 28 13:27 linux/suse/x86_64-13.1/inst-sys/.update.d92d43be-cc4f-4aac-ac8f-64db2ab0c14d -rw-r--r-- 1 root root 137 Jan 28 13:27 linux/suse/x86_64-13.1/dud.config lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/ppc64-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/i386-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/s390-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/s390x-13.1 -> x86_64-13.1 lrwxrwxrwx 1 root root 11 Jan 28 13:27 linux/suse/ppc-13.1 -> x86_64-13.1 312 blocks wotan:~ >
Tschuess, Thomas Fehr
On Thu, Jan 30, Joschi Brauchle wrote:
For some reason I did not get the DUD to work correctly. It may be my fault... Anyways, I unpacked the DUD and copied all files into my OSS repository on the NFS server, leading to the equivalent effect of the DUD.
Now, Autoyast stage 2 works perfectly again! Thanks!
I have a quick followup question:
<runlevel> <default>5</default> <services config:type="list"> <service> <service_name>rpcbind</service_name> <service_status>enable</service_status> </service> </services> </runlevel> --------------------- does not work, i.e. rpcbind.service is disabled in the installed system.
In y2log I see an error message saying something like "rpcbind service does not exist, creating it" (or something along these lines, dont have the log available currently). Same happens e.g. for "xinetd", but not for "sshd", "nfs" and many others.
Could be that with migration to systemd some services have been renamed. In theory these renames could be mapped to corresponding systemd names in Import/Export code of yast2-runlevel. So it would probably be worth a bug report. Unfortunately I cannot guarantee that anyone really fixes it.
In general the "migration" (if one would call it that, usurpation would bet a much better term) to systemd is one of the worst nightmares since I work in linux area.
So why does AutoYast think that the rpcbind.service does not exist and why is it not enabled?
Tschuess, Thomas Fehr
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 de_masi@asta.tu-darmstadt.de:
Am 30.01.2014 12:18, schrieb Thomas Fehr:
Hi Ivan,
Hello Thomas,
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: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hello everyone,
basically, one took this email and replaced "13.1" with "13.2":
I converted a completely working XML from a 13.1 installation to 13.2.
The autoinstallation finishes, but the installed system is
- missing Sysconfig configuration from <sysconfig> section
- has not run any of the <post-scripts> and <init-scripts>
- does not accept the root password configured in the <users> section
- is missing all files installed from the <files> section of the XML
Version 13.2 will be released in a couple of days and it looks like the autoinstalled is broken once again on the (to be) released medium.
Hence, auto-installing will not work correctly for the complete lifetime of 13.2. This was the case for 12.x and 13.1 already,
This is pretty frustrating... :-(
Joschi
On 01/30/2014 10:40 AM, Joschi Brauchle wrote:
Hi everyone,
sorry for asking such a general question, but what is the state of AutoYast for OpenSUSE 13.1?
I converted a completely working XML from a 12.3 installation to 13.1.
The autoinstallation finishes, but the installed system is
- missing Sysconfig configuration from <sysconfig> section
- has not run any of the <post-scripts> and <init-scripts>
- does not accept the root password configured in the <users> section
- is missing all files installed from the <files> section of the XML
- misses LDAP and KRB config from <ldap> and <kerberos>
- services are not configured as in <services>
and many more problems.
To me it looks like the complete second stage is missing, as all those things are done there.
Is this a known problem? Or are there known problems for 13.1?
Did anyone succeed with AutoYast and 13.1 with any of the above mentioned XML sections?
The y2log file from second stage is very small and does not show any errors...
Best regards, Joschi Brauchle
On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Version 13.2 will be released in a couple of days and it looks like the autoinstalled is broken once again on the (to be) released medium.
Hence, auto-installing will not work correctly for the complete lifetime of 13.2. This was the case for 12.x and 13.1 already,
This is pretty frustrating... :-(
Meh. Damn. Does any bnc# exist for this?
On 10/20/2014 02:21 PM, 686f6c6d wrote:
On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Version 13.2 will be released in a couple of days and it looks like the autoinstalled is broken once again on the (to be) released medium.
Hence, auto-installing will not work correctly for the complete lifetime of 13.2. This was the case for 12.x and 13.1 already,
This is pretty frustrating... :-(
Meh. Damn. Does any bnc# exist for this?
No, I am currently trying to sort out the problems and analyze.
So far it looks like a 13.1 XML used for 13.2 results in a broken installation (i.e. all second stage steps are missing). I'll provide more information as soon as I know whats going wrong.
Possibly, Thomas Fehr could comment on how the second stage works in 13.2 and what steps are needed to get it working, as it looks like it was dropped from the regular installer?
Also, is there any updated documentation on AutoYast for 13.2? I couldnt find anything really,...
Thanks for any hints and suggestions! -Joschi Brauchle
Hi,
On Mon, Oct 20, Joschi Brauchle wrote:
On 10/20/2014 02:21 PM, 686f6c6d wrote:
On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Version 13.2 will be released in a couple of days and it looks like the autoinstalled is broken once again on the (to be) released medium.
Hence, auto-installing will not work correctly for the complete lifetime of 13.2. This was the case for 12.x and 13.1 already,
This is pretty frustrating... :-(
Meh. Damn. Does any bnc# exist for this?
No, I am currently trying to sort out the problems and analyze.
So far it looks like a 13.1 XML used for 13.2 results in a broken installation (i.e. all second stage steps are missing). I'll provide more information as soon as I know whats going wrong.
Possibly, Thomas Fehr could comment on how the second stage works in 13.2 and what steps are needed to get it working, as it looks like it was dropped from the regular installer?
I am currently on a sabattical for a year that started 1.4.2014 . Therefore my knowledge about developments that happened in the last some months is quite limited.
Autoyast maintainer is Stefan Schubert schubi@suse.de. I forwarded this thread to him.
Tschuess, Thomas Fehr
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr:
Hi,
On Mon, Oct 20, Joschi Brauchle wrote:
On 10/20/2014 02:21 PM, 686f6c6d wrote:
On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Version 13.2 will be released in a couple of days and it looks like the autoinstalled is broken once again on the (to be) released medium.
Hence, auto-installing will not work correctly for the complete lifetime of 13.2. This was the case for 12.x and 13.1 already,
This is pretty frustrating... :-(
Meh. Damn. Does any bnc# exist for this?
No, I am currently trying to sort out the problems and analyze.
So far it looks like a 13.1 XML used for 13.2 results in a broken installation (i.e. all second stage steps are missing). I'll provide more information as soon as I know whats going wrong.
Possibly, Thomas Fehr could comment on how the second stage works in 13.2 and what steps are needed to get it working, as it looks like it was dropped from the regular installer?
I am currently on a sabattical for a year that started 1.4.2014 . Therefore my knowledge about developments that happened in the last some months is quite limited.
Autoyast maintainer is Stefan Schubert schubi@suse.de. I forwarded this thread to him.
Tschuess, Thomas Fehr
Hello Stefan,
I am currently trying to figure out what is going wrong with the 13.1 xml profile in 13.2. The installation is completely broken without any (gui) errors during the process.
But if I create a new profile for 13.2 from scratch, auto installation works fine. Thus, I'd like to revise my statement about Autoyast being broken, it is clearly not!
One question: Is there an up-to-date website that lists the changes from AY 13.1 to 13.2?
Google results: 1) http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3 (which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto... the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
There seem to be a lot of changes to the installer (plus new modules like yast2-auth-client to configure sssd) but no documentation to be found (easily) for users...
Thanks, Joschi Brauchle
On 10/21/2014 09:26 AM, Stefan Schubert wrote:
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr:
Hi,
On Mon, Oct 20, Joschi Brauchle wrote:
On 10/20/2014 02:21 PM, 686f6c6d wrote:
On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Version 13.2 will be released in a couple of days and it looks like the autoinstalled is broken once again on the (to be) released medium.
Hence, auto-installing will not work correctly for the complete lifetime of 13.2. This was the case for 12.x and 13.1 already,
This is pretty frustrating... :-(
Meh. Damn. Does any bnc# exist for this?
No, I am currently trying to sort out the problems and analyze.
So far it looks like a 13.1 XML used for 13.2 results in a broken installation (i.e. all second stage steps are missing). I'll provide more information as soon as I know whats going wrong.
Possibly, Thomas Fehr could comment on how the second stage works in 13.2 and what steps are needed to get it working, as it looks like it was dropped from the regular installer?
I am currently on a sabattical for a year that started 1.4.2014 . Therefore my knowledge about developments that happened in the last some months is quite limited.
Autoyast maintainer is Stefan Schubert schubi@suse.de. I forwarded this thread to him.
Tschuess, Thomas Fehr
Am 21.10.2014 um 09:55 schrieb Joschi Brauchle:
- http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3
(which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto... the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
Hi, there is a new documentation for SLES12. I will ask the docu team for update the online docu. Thanks !
Greetings Stefan
On https://www.suse.com/documentation/sles-12/book_autoyast/data/book_autoyast....
is the latest documentation.
Greetings Stefan
Am 21.10.2014 um 09:55 schrieb Joschi Brauchle:
Hello Stefan,
I am currently trying to figure out what is going wrong with the 13.1 xml profile in 13.2. The installation is completely broken without any (gui) errors during the process.
But if I create a new profile for 13.2 from scratch, auto installation works fine. Thus, I'd like to revise my statement about Autoyast being broken, it is clearly not!
One question: Is there an up-to-date website that lists the changes from AY 13.1 to 13.2?
Google results:
- http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3
(which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto... the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
There seem to be a lot of changes to the installer (plus new modules like yast2-auth-client to configure sssd) but no documentation to be found (easily) for users...
Thanks, Joschi Brauchle
On 10/21/2014 09:26 AM, Stefan Schubert wrote:
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr:
Hi,
On Mon, Oct 20, Joschi Brauchle wrote:
On 10/20/2014 02:21 PM, 686f6c6d wrote:
On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle joschi.brauchle@tum.de wrote:
Version 13.2 will be released in a couple of days and it looks like the autoinstalled is broken once again on the (to be) released medium.
Hence, auto-installing will not work correctly for the complete lifetime of 13.2. This was the case for 12.x and 13.1 already,
This is pretty frustrating... :-(
Meh. Damn. Does any bnc# exist for this?
No, I am currently trying to sort out the problems and analyze.
So far it looks like a 13.1 XML used for 13.2 results in a broken installation (i.e. all second stage steps are missing). I'll provide more information as soon as I know whats going wrong.
Possibly, Thomas Fehr could comment on how the second stage works in 13.2 and what steps are needed to get it working, as it looks like it was dropped from the regular installer?
I am currently on a sabattical for a year that started 1.4.2014 . Therefore my knowledge about developments that happened in the last some months is quite limited.
Autoyast maintainer is Stefan Schubert schubi@suse.de. I forwarded this thread to him.
Tschuess, Thomas Fehr
Thank you very much for the documentation.
Some more information on the broken installation: It looks like it is the *same* problem that existed for 13.1: the add-on section.
I did two installations, with this diff between xmls: ------- --- test.xml 2014-10-21 17:05:15.000000000 +0200 +++ test.xml.broken 2014-10-21 17:05:04.000000000 +0200 @@ -4,7 +4,14 @@ <add-on> - <add_on_products config:type="list"/> + <add_on_products config:type="list"> + <listentry> + <media_url><![CDATA[http://download.opensuse.org/repositories/home:/lnt-sysadmin:/tools/openSUSE_13.2/]]></media_url> + <name>OpenSUSE13.2_HTTP_OBS:lnt-sysadmin:tools</name> + <product>OpenSUSE13.2 HTTP OBS:lnt-sysadmin:tools</product> + <product_dir>/</product_dir> + </listentry> + </add_on_products> </add-on> ------- The installation *with* the add-on section specified is broken!
This looks pretty identical to https://bugzilla.novell.com/show_bug.cgi?id=846011
Shall I reopen or create new report?
As there are only 13 days to release, is there any chance to get this fixed before GM?
-Joschi Brauchle
On 10/21/2014 11:28 AM, Stefan Schubert wrote:
On https://www.suse.com/documentation/sles-12/book_autoyast/data/book_autoyast....
is the latest documentation.
Greetings Stefan
Am 21.10.2014 um 09:55 schrieb Joschi Brauchle:
Hello Stefan,
I am currently trying to figure out what is going wrong with the 13.1 xml profile in 13.2. The installation is completely broken without any (gui) errors during the process.
But if I create a new profile for 13.2 from scratch, auto installation works fine. Thus, I'd like to revise my statement about Autoyast being broken, it is clearly not!
One question: Is there an up-to-date website that lists the changes from AY 13.1 to 13.2?
Google results:
- http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3
(which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto... the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
There seem to be a lot of changes to the installer (plus new modules like yast2-auth-client to configure sssd) but no documentation to be found (easily) for users...
Thanks, Joschi Brauchle
On 10/21/2014 09:26 AM, Stefan Schubert wrote:
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr:
Hi,
On Mon, Oct 20, Joschi Brauchle wrote:
On 10/20/2014 02:21 PM, 686f6c6d wrote:
On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle joschi.brauchle@tum.de wrote: > Version 13.2 will be released in a couple of days and it looks like > the > autoinstalled is broken once again on the (to be) released medium. > > Hence, auto-installing will not work correctly for the complete > lifetime of > 13.2. This was the case for 12.x and 13.1 already, > > This is pretty frustrating... :-( Meh. Damn. Does any bnc# exist for this?
No, I am currently trying to sort out the problems and analyze.
So far it looks like a 13.1 XML used for 13.2 results in a broken installation (i.e. all second stage steps are missing). I'll provide more information as soon as I know whats going wrong.
Possibly, Thomas Fehr could comment on how the second stage works in 13.2 and what steps are needed to get it working, as it looks like it was dropped from the regular installer?
I am currently on a sabattical for a year that started 1.4.2014 . Therefore my knowledge about developments that happened in the last some months is quite limited.
Autoyast maintainer is Stefan Schubert schubi@suse.de. I forwarded this thread to him.
Tschuess, Thomas Fehr
I figured it is NOT the same problem, as y2log of the second stage clearly shows a segmentation fault!
I filed: http://bugzilla.opensuse.org/show_bug.cgi?id=902086
Best regards, Joschi Brauchle
On 10/21/2014 05:40 PM, Joschi Brauchle wrote:
Thank you very much for the documentation.
Some more information on the broken installation: It looks like it is the *same* problem that existed for 13.1: the add-on section.
I did two installations, with this diff between xmls:
--- test.xml 2014-10-21 17:05:15.000000000 +0200 +++ test.xml.broken 2014-10-21 17:05:04.000000000 +0200 @@ -4,7 +4,14 @@ <add-on>
<add_on_products config:type="list"/>
<add_on_products config:type="list">
<listentry><media_url><![CDATA[http://download.opensuse.org/repositories/home:/lnt-sysadmin:/tools/openSUSE_13.2/]]></media_url>
<name>OpenSUSE13.2_HTTP_OBS:lnt-sysadmin:tools</name><product>OpenSUSE13.2 HTTP OBS:lnt-sysadmin:tools</product><product_dir>/</product_dir></listentry></add_on_products> </add-on>
The installation *with* the add-on section specified is broken!
This looks pretty identical to https://bugzilla.novell.com/show_bug.cgi?id=846011
Shall I reopen or create new report?
As there are only 13 days to release, is there any chance to get this fixed before GM?
-Joschi Brauchle
On 10/21/2014 11:28 AM, Stefan Schubert wrote:
On https://www.suse.com/documentation/sles-12/book_autoyast/data/book_autoyast....
is the latest documentation.
Greetings Stefan
Am 21.10.2014 um 09:55 schrieb Joschi Brauchle:
Hello Stefan,
I am currently trying to figure out what is going wrong with the 13.1 xml profile in 13.2. The installation is completely broken without any (gui) errors during the process.
But if I create a new profile for 13.2 from scratch, auto installation works fine. Thus, I'd like to revise my statement about Autoyast being broken, it is clearly not!
One question: Is there an up-to-date website that lists the changes from AY 13.1 to 13.2?
Google results:
- http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3
(which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto...
the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
There seem to be a lot of changes to the installer (plus new modules like yast2-auth-client to configure sssd) but no documentation to be found (easily) for users...
Thanks, Joschi Brauchle
On 10/21/2014 09:26 AM, Stefan Schubert wrote:
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr:
Hi,
On Mon, Oct 20, Joschi Brauchle wrote:
On 10/20/2014 02:21 PM, 686f6c6d wrote: > On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle > joschi.brauchle@tum.de wrote: >> Version 13.2 will be released in a couple of days and it looks like >> the >> autoinstalled is broken once again on the (to be) released medium. >> >> Hence, auto-installing will not work correctly for the complete >> lifetime of >> 13.2. This was the case for 12.x and 13.1 already, >> >> This is pretty frustrating... :-( > Meh. Damn. Does any bnc# exist for this? No, I am currently trying to sort out the problems and analyze.
So far it looks like a 13.1 XML used for 13.2 results in a broken installation (i.e. all second stage steps are missing). I'll provide more information as soon as I know whats going wrong.
Possibly, Thomas Fehr could comment on how the second stage works in 13.2 and what steps are needed to get it working, as it looks like it was dropped from the regular installer?
I am currently on a sabattical for a year that started 1.4.2014 . Therefore my knowledge about developments that happened in the last some months is quite limited.
Autoyast maintainer is Stefan Schubert schubi@suse.de. I forwarded this thread to him.
Tschuess, Thomas Fehr
Thanks ! I will have a look on it.
Greetings Stefan Schubert Am 21.10.2014 um 18:44 schrieb Joschi Brauchle:
I figured it is NOT the same problem, as y2log of the second stage clearly shows a segmentation fault!
I filed: http://bugzilla.opensuse.org/show_bug.cgi?id=902086
Best regards, Joschi Brauchle
On 10/21/2014 05:40 PM, Joschi Brauchle wrote:
Thank you very much for the documentation.
Some more information on the broken installation: It looks like it is the *same* problem that existed for 13.1: the add-on section.
I did two installations, with this diff between xmls:
--- test.xml 2014-10-21 17:05:15.000000000 +0200 +++ test.xml.broken 2014-10-21 17:05:04.000000000 +0200 @@ -4,7 +4,14 @@ <add-on>
<add_on_products config:type="list"/>
<add_on_products config:type="list">
<listentry><media_url><![CDATA[http://download.opensuse.org/repositories/home:/lnt-sysadmin:/tools/openSUSE_13.2/]]></media_url>
- <name>OpenSUSE13.2_HTTP_OBS:lnt-sysadmin:tools</name>
<product>OpenSUSE13.2 HTTP OBS:lnt-sysadmin:tools</product><product_dir>/</product_dir></listentry></add_on_products> </add-on>
The installation *with* the add-on section specified is broken!
This looks pretty identical to https://bugzilla.novell.com/show_bug.cgi?id=846011
Shall I reopen or create new report?
As there are only 13 days to release, is there any chance to get this fixed before GM?
-Joschi Brauchle
On 10/21/2014 11:28 AM, Stefan Schubert wrote:
On https://www.suse.com/documentation/sles-12/book_autoyast/data/book_autoyast....
is the latest documentation.
Greetings Stefan
Am 21.10.2014 um 09:55 schrieb Joschi Brauchle:
Hello Stefan,
I am currently trying to figure out what is going wrong with the 13.1 xml profile in 13.2. The installation is completely broken without any (gui) errors during the process.
But if I create a new profile for 13.2 from scratch, auto installation works fine. Thus, I'd like to revise my statement about Autoyast being broken, it is clearly not!
One question: Is there an up-to-date website that lists the changes from AY 13.1 to 13.2?
Google results:
- http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3
(which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto...
the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
There seem to be a lot of changes to the installer (plus new modules like yast2-auth-client to configure sssd) but no documentation to be found (easily) for users...
Thanks, Joschi Brauchle
On 10/21/2014 09:26 AM, Stefan Schubert wrote:
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr:
Hi,
On Mon, Oct 20, Joschi Brauchle wrote:
> On 10/20/2014 02:21 PM, 686f6c6d wrote: >> On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle >> joschi.brauchle@tum.de wrote: >>> Version 13.2 will be released in a couple of days and it looks >>> like >>> the >>> autoinstalled is broken once again on the (to be) released >>> medium. >>> >>> Hence, auto-installing will not work correctly for the complete >>> lifetime of >>> 13.2. This was the case for 12.x and 13.1 already, >>> >>> This is pretty frustrating... :-( >> Meh. Damn. Does any bnc# exist for this? > No, > I am currently trying to sort out the problems and analyze. > > So far it looks like a 13.1 XML used for 13.2 results in a broken > installation (i.e. all second stage steps are missing). > I'll provide more information as soon as I know whats going wrong. > > Possibly, Thomas Fehr could comment on how the second stage > works in > 13.2 > and what steps are needed to get it working, as it looks like it > was > dropped from the regular installer? I am currently on a sabattical for a year that started 1.4.2014 . Therefore my knowledge about developments that happened in the last some months is quite limited.
Autoyast maintainer is Stefan Schubert schubi@suse.de. I forwarded this thread to him.
Tschuess, Thomas Fehr
Just FYI: Current workaround is blacklisting the "libproxy1-config-kde4" package... ------------- <software> <remove-packages config:type="list"> <package>libproxy1-config-kde4</package> </remove-packages> </software> -------------
Best regards, Joschi Brauchle
On 10/22/2014 09:33 AM, Stefan Schubert wrote:
Thanks ! I will have a look on it.
Greetings Stefan Schubert Am 21.10.2014 um 18:44 schrieb Joschi Brauchle:
I figured it is NOT the same problem, as y2log of the second stage clearly shows a segmentation fault!
I filed: http://bugzilla.opensuse.org/show_bug.cgi?id=902086
Best regards, Joschi Brauchle
On 10/21/2014 05:40 PM, Joschi Brauchle wrote:
Thank you very much for the documentation.
Some more information on the broken installation: It looks like it is the *same* problem that existed for 13.1: the add-on section.
I did two installations, with this diff between xmls:
--- test.xml 2014-10-21 17:05:15.000000000 +0200 +++ test.xml.broken 2014-10-21 17:05:04.000000000 +0200 @@ -4,7 +4,14 @@ <add-on>
<add_on_products config:type="list"/>
<add_on_products config:type="list">
<listentry><media_url><![CDATA[http://download.opensuse.org/repositories/home:/lnt-sysadmin:/tools/openSUSE_13.2/]]></media_url>
- <name>OpenSUSE13.2_HTTP_OBS:lnt-sysadmin:tools</name>
<product>OpenSUSE13.2 HTTP OBS:lnt-sysadmin:tools</product><product_dir>/</product_dir></listentry></add_on_products> </add-on>
The installation *with* the add-on section specified is broken!
This looks pretty identical to https://bugzilla.novell.com/show_bug.cgi?id=846011
Shall I reopen or create new report?
As there are only 13 days to release, is there any chance to get this fixed before GM?
-Joschi Brauchle
On 10/21/2014 11:28 AM, Stefan Schubert wrote:
On https://www.suse.com/documentation/sles-12/book_autoyast/data/book_autoyast....
is the latest documentation.
Greetings Stefan
Am 21.10.2014 um 09:55 schrieb Joschi Brauchle:
Hello Stefan,
I am currently trying to figure out what is going wrong with the 13.1 xml profile in 13.2. The installation is completely broken without any (gui) errors during the process.
But if I create a new profile for 13.2 from scratch, auto installation works fine. Thus, I'd like to revise my statement about Autoyast being broken, it is clearly not!
One question: Is there an up-to-date website that lists the changes from AY 13.1 to 13.2?
Google results:
- http://doc.opensuse.org/projects/autoyast/ is about SLES11SP3
(which is strange as it is hosted by opensuse.org). 2) https://www.suse.com/documentation/sles11/singlehtml/book_autoyast/book_auto...
the same 3) http://users.suse.com/~ug/ is outdated as of 12.2.
There seem to be a lot of changes to the installer (plus new modules like yast2-auth-client to configure sssd) but no documentation to be found (easily) for users...
Thanks, Joschi Brauchle
On 10/21/2014 09:26 AM, Stefan Schubert wrote:
Hi Joschi, please open a bug report and attach the logfiles and autoinst.xml Thanks !
Greetings Stefan Am 20.10.2014 um 23:58 schrieb Thomas Fehr: > Hi, > > On Mon, Oct 20, Joschi Brauchle wrote: > >> On 10/20/2014 02:21 PM, 686f6c6d wrote: >>> On Mon, Oct 20, 2014 at 9:38 AM, Joschi Brauchle >>> joschi.brauchle@tum.de wrote: >>>> Version 13.2 will be released in a couple of days and it looks >>>> like >>>> the >>>> autoinstalled is broken once again on the (to be) released >>>> medium. >>>> >>>> Hence, auto-installing will not work correctly for the complete >>>> lifetime of >>>> 13.2. This was the case for 12.x and 13.1 already, >>>> >>>> This is pretty frustrating... :-( >>> Meh. Damn. Does any bnc# exist for this? >> No, >> I am currently trying to sort out the problems and analyze. >> >> So far it looks like a 13.1 XML used for 13.2 results in a broken >> installation (i.e. all second stage steps are missing). >> I'll provide more information as soon as I know whats going wrong. >> >> Possibly, Thomas Fehr could comment on how the second stage >> works in >> 13.2 >> and what steps are needed to get it working, as it looks like it >> was >> dropped from the regular installer? > I am currently on a sabattical for a year that started 1.4.2014 . > Therefore my knowledge about developments that happened in the last > some months is quite limited. > > Autoyast maintainer is Stefan Schubert schubi@suse.de. > I forwarded this thread to him. > > Tschuess, > Thomas Fehr
bnc#902086 is marked as fixed, but the fix did not make it into 13.2 (or, to be more precise, the 13.2 install medium/repo), correct?
I'm asking because what I see is that 1. Once I add an <add-on> section to my 13.2 profile, the installation grinds to a halt[0]. 2. The fix for #902086 isn't in /usr/lib/systemd/system/YaST2-Second-Stage.service outside the chroot. 3. When I add the fix for #902086 as a workaround pre-script to my profile to change /usr/lib/systemd/system/YaST2-Second-Stage.service outside the chroot and re-include my <add-on> section in the profile, the problem still occurs, that is, the installation grinds to a halt. 4. When I try to add the fix to the chroot, either as postpartitioning-script or chroot-script with chrooted=false, the problem still occurs. (The postpartitioning-script seems to be too early, the chroot-script too late.)
[0]: It stops during the step "Performing installation", showing an empty package list pane and empty "Actions performed" pane. The upper progress bar says "Adding entry for mount point / to /etc/fstab" (which finishes sucessfully AFAICT, but the message isn't changed to reflect what the current step really is) and the lower, "Installing packages" progress bar halts at or somewhere near the 27% mark, depending on the specifics of my AutoYAST profile. When I wait some time between 15 and 60 minutes (I did not time this), YaST (y2base) is killed with an OOM.
I'm going to fall back to the 13.1 workaround for bnc#846011 that we used, which manually adds the add-ons later.
Before I report this as a new bug or add it to bnc#902086: Has anybody encountered this issue? (Joschi: Your <remove-packages> workaround doesn't work for me either. )c; )
autoinstall@lists.opensuse.org
-
686f6c6d -
Erico Mendonça -
Ivan De Masi -
Joschi Brauchle -
Stefan Schubert -
Thomas Fehr