[opensuse-autoinstall] Adding updates to SLES 11 SP1 CD-ROM
Background: I have a basic CD-ROM autoinstall working for SLES 11
SP1. Now I am trying to add updates.
I have followed the instructions here:
http://www.suse.com/~ug/AutoYaST_FAQ.html#b8
...to create a custom CD-ROM with a properly constructed "updates"
directory. But I am having trouble figuring out what to use for the
I thought this was documented somewhere, but I could not find it easily. This comment from Uwe himself could help: http://ugansert.blogspot.com/2009/01/opensuse-111-sles11-and-add-ons.html?sh... It lead me to this (seemingly) complete overview here, but the docs say this is only for "autoyast=$url": http://www.suse.de/~ug/autoyast_doc/invoking_autoinst.html hth, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Thank you for the reply. But I am still having trouble. I gave up trying to use <add-on> in autoinst.xml, and I am trying to use add_on_products.xml instead. I am using the exact add_on_products.xml example from the blog post you referenced (thank you for the pointer), except with my own <url>: <url>relurl://updates</url> Now my installation is failing with: Error Unable to add product cd:///updates?devices=/dev/sr1,/dev/sr0. I suppose this is progress of a sort. But it sure would be nice if the error told me what the problem is... Is a more verbose error message being written in some log somewhere? I am pretty sure I followed the instructions at http://www.suse.com/~ug/AutoYaST_FAQ.html#b8 precisely, but perhaps something is wrong with my "updates" tree, so I will try building it again from the top. I am curious, though: Has anybody actually gotten this working on SLES 11 SP1? - Pat On Thu, Nov 18, 2010 at 1:06 PM, 686f6c6d <686f6c6d@googlemail.com> wrote:
I thought this was documented somewhere, but I could not find it easily.
This comment from Uwe himself could help: http://ugansert.blogspot.com/2009/01/opensuse-111-sles11-and-add-ons.html?sh...
It lead me to this (seemingly) complete overview here, but the docs say this is only for "autoyast=$url": http://www.suse.de/~ug/autoyast_doc/invoking_autoinst.html
hth, 686f6c6d
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Thu, Nov 18, 2010 at 23:09, Patrick J. LoPresti
Thank you for the reply. But I am still having trouble.
I gave up trying to use <add-on> in autoinst.xml, and I am trying to use add_on_products.xml instead.
Sorry, I have no experience with add_on_products.xml and it seems the former documentation location is no more: http://forgeftp.novell.com/yast/doc/SL11.1/tdg/installation_features.html
Error Unable to add product cd:///updates?devices=/dev/sr1,/dev/sr0.
IIRC, every single time I saw this error it was related to GPG problems (well, or a messed up network, which doesn't apply in your case). Braindump so you can hopefully help yourself a bit: Maybe it is related to this (i cannot access the bug): [bug] autoyast fails to add add-on product with iso image (bnc#484735) from here http://www.suse.com/~ug/autoyast_changes_SLES11SP1.html Also I found this: http://lists.opensuse.org/opensuse-autoinstall/2009-10/msg00008.html I don't know if there will be logs in your case, but you could check here: http://lists.opensuse.org/opensuse-autoinstall/2010-08/msg00007.html http://lists.opensuse.org/opensuse-autoinstall/2010-08/msg00008.html To check during install, y2confirm is helpful: http://ugansert.blogspot.com/2009/01/why-to-confirm.html http://ugansert.blogspot.com/2009/02/why-to-confirm-part-2.html tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
OK, I finally got it working. Here are some notes in case anyone else is struggling to add updates to their SLES 11 SP1 autoinstall. First, when you get "Error: failed to add add-on product", press CTRL-ALT-F2 to get to the shell prompt. Examine /var/log/YaST2/y2log. Somewhere among the last ~100 lines you will find more details about the failure. Second, "relurl://" is only supported by add_on_products.xml; it simply does not work in the <add-on> section of autoinst.xml. Neither does "file://", since it does not refer to the installation source. "cd:///updates" does work, but I am leaning towards sticking with add_on_products.xml because I like the idea of "relurl:". Third, I was completely unable to get the various <signature-handling> options to work. (I only tried it in the <global> section, not as part of the add-on.) No matter what I tried, my updates repository was rejected because of signature failures. So I had to do the Full Monty: I created a GPG key, used it to sign the updates/content and SHA1SUMS files, and added the key to the initrd. These steps are documented in different places: http://ugansert.blogspot.com/2009/01/opensuse-111-sles11-and-add-ons.html (SHA1SUMS) http://www.suse.com/~ug/AutoYaST_FAQ.html#bB (updates/content) I automated this entire process, from generating the GPG key to signing the files to adding the key to the initrd... It is a single Makefile that I would be happy to clean up and share if anybody thinks that might be useful. Is there someplace I could upload it? A wiki or something? One last war story and a suggestion. The messages in y2log are verbose, yet not entirely complete... At one point, the "failed to add add-on product" error was caused by a failure to add my GPG key (from the initrd) to the trusted keyring. y2log showed the complete "gpg2 --import ..." command, and it showed that gpg2 had exited non-zero, but it did not contain the actual error message from gpg2. I had to run the full gpg2 command by hand to see the error. It was a time conflict; my key was rejected because its self-signature appeared to be from the future. (I am doing a fresh installation on new hardware, so the CMOS clock was off by a few days, and I had just created the key on a system with an accurate clock.) I would suggest that during an automated installation, the "--ignore-time-conflict" option to gpg2 is appropriate. There is no reason to expect the system clock to be sane until *after* the system is installed... And this failure mode is not exactly pretty. Anyway, thanks for all of the feedback and references. They helped a lot. - Pat -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Fri, Nov 19, 2010 at 19:38, Patrick J. LoPresti
Third, I was completely unable to get the various <signature-handling> options to work. (I only tried it in the <global> section, not as part of the add-on.) No matter what I tried, my updates repository was rejected because of signature failures. So I had to do [...]
The really really nasty thing about the signature handling is that the
syntax for the general case vs. the per-repo case is different:
- On the *global/general level*, you can ONLY use true/false to
enable/disable certain options globally for the repos.
ex.:
I automated this entire process, from generating the GPG key to signing the files to adding the key to the initrd... It is a single Makefile that I would be happy to clean up and share if anybody thinks that might be useful. Is there someplace I could upload it? A wiki or something?
I was gonna ask the same thing. I think that would also help improving the documentation; there are many items that aren't easily found or misleading/confusing, some examples are just wrong etc. I would really like a wiki (with priv. write access, maybe) or a git repo or *anything* I can do to contribute back to the main docs that is not email. (; I know Uwe has been busy the last few days (and possibly will be some more), but he didn't forget us, he will read and answer in time, he promised. (; tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Saturday 20 November 2010 686f6c6d wrote:
I automated this entire process, from generating the GPG key to signing the files to adding the key to the initrd... It is a single Makefile that I would be happy to clean up and share if anybody thinks that might be useful. Is there someplace I could upload it? A wiki or something?
I was gonna ask the same thing. I think that would also help improving the documentation; there are many items that aren't easily found or misleading/confusing, some examples are just wrong etc.
I wanted to start a wiki on http://en.opensuse.org//YaST_AutoYaST but then I did not find the time to really make it useable. I like the Idea of a wiki and will give it another try as soon as I find the time.
I know Uwe has been busy the last few days (and possibly will be some more),
yes :( -- 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@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
686f6c6d -
Patrick J. LoPresti -
Uwe Gansert