on Friday 21 May 2010 Lonni J Friedman wrote:

I'm trying to get SLED-11-SP1 installing via autoyast, but the install (for both i686 & x86_64) fails as soon as it reaches the 'Create partition plans' step with a pop-up error stating: These packages could not be found in the software repositories: autoyast2-installation

I'm rather puzzled by this, as I've got that very RPM on my installation server under $OS/suse/noarch

Anyone have any suggestions?

you should make autoyast stop in the proposal screen by either passing "y2confirm" on the kernel commandline or by setting to true in the <general><mode> section (see http://www.suse.de/~ug/autoyast_doc/configuration.html#CreateProfile.General ) then, when it stops, click on the "Software" link and try to select autoyast2- installation manually to see a more verbose error message of the resolver. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Pest" by :Wumpscut: -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

On Wed, May 26, 2010 at 4:23 PM, Lonni J Friedman wrote:

On Fri, May 21, 2010 at 3:00 AM, Uwe Gansert wrote:

...

on Friday 21 May 2010 Lonni J Friedman wrote:

...

I'm trying to get SLED-11-SP1 installing via autoyast, but the install (for both i686 & x86_64) fails as soon as it reaches the 'Create partition plans' step with a pop-up error stating: These packages could not be found in the software repositories: autoyast2-installation

I'm rather puzzled by this, as I've got that very RPM on my installation server under $OS/suse/noarch

Anyone have any suggestions?

you should make autoyast stop in the proposal screen by either passing "y2confirm" on the kernel commandline or by setting to true in the <general><mode> section (see http://www.suse.de/~ug/autoyast_doc/configuration.html#CreateProfile.General ) then, when it stops, click on the "Software" link and try to select autoyast2- installation manually to see a more verbose error message of the resolver.

Thanks for your input.  I tried passing the y2confirm option, and then the installation fails with a different error:

Unable to create repository from URL 'http://10.31.40.58/distros/suse/os/SLED11-SP1/x86'. Details: [|] Valid metadata not found at specified URL(s) History: - /var/cache/zypp/raw/SUSE-Linux-Enterprise-Desktop-11-SP1 11.1.1-1.133xZEGet: No metadata checksums in content file.

I'm not sure what this error is about, as the URL that its referencing is definitely valid, and has the full contents of the SLED11-SP1-i586 DVDs copied into it.

I should note that the my original problem went away for x86_64 when I switched to the final version of SLED11-SP1.  Its only i586 that continues to cause problems.

After googling, I found quite a few others with the same error in assorted versions of SUSE products, including this one, but no solutions: http://ugansert.blogspot.com/2009/03/minimum-profile.html -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

On Thu, May 27, 2010 at 1:37 AM, Uwe Gansert wrote:

on Thursday 27 May 2010 Lonni J Friedman wrote:

...

Unable to create repository from URL 'http://10.31.40.58/distros/suse/os/SLED11-SP1/x86'. Details: [|] Valid metadata not found at specified URL(s) History: - /var/cache/zypp/raw/SUSE-Linux-Enterprise-Desktop-11-SP1 11.1.1-1.133xZEGet: No metadata checksums in content file.

that error is not raised by autoyast itself but by the resolver. Can you do manual installations with that inst-source (remove the autoyast=.... parameter to switch to a non-autoyast installation)? It should trigger the same error.

...

I'm not sure what this error is about, as the URL that its referencing is definitely valid, and has the full contents of the SLED11-SP1-i586 DVDs copied into it.

do you see anything more verbose in the /var/log/YaST2/y2log file? The error message "No metadata checksums in content file" is about missing checksum in the "content" file in the root of the installation source. Those checksum lines start with: META SHA1 295ba7b97cafc....... HASH SHA1 8ae426e9f4505a0 ... If you just copied that file from the original inst-source I have no explanation. Maybe you can send me the y2log file when you see that error.

...

I should note that the my original problem went away for x86_64 when I switched to the final version of SLED11-SP1.  Its only i586 that continues to cause problems.

are you 100% sure you did not accidently use a content file from another release candidate or so?

This is truly bizarre. Now that I knew why the the error was happening, I looked at the the content file on the server, and it was missing all the checksum lines. I ran a diff between it and the one on the install media, and literally, that was the only thing that was different between the two. I'm completely puzzled how this happened. I copied (again) the content file from the install media onto the server, and now the OS install via autoyast works fine. Many thanks for your prompt help, I doubt that I would have figured this out on my own. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org