Bug 175567

Summary:	Network Installation fails on "Initializing Catalogs"
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Justin Grote <justin>
Component:	Installation	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Stanislav Visnovsky <visnov>
Severity:	Blocker
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Justin Grote 2006-05-13 16:47:14 UTC

Attemping a network installation of 10.1 final using the mini ISO inside of VMWare Workstation 5.5.1-build-19175. Connection is established and it finds, downloads, and loads the network image (about 70MB) just fine. However, After Selecting language and leaving "Install Add-On's" unchecked and clicking next, the system will go to "Initializing Catalogs" for about 3 minutes and then completely lock up. When done through VNC, the VNC session gets killed and the system returns to the linuxrc screen with "An error has occured during installation". No other errors found.

Tried the following combinations:

* Using boot.iso file from the /boot directory (MD5SUM: c6d4ab88946ada7d16b22c00bf6e8f63)
* Using SUSE-Linux-10.1-GM-i386-mini.iso (MD5SUM: 48da4c0b94501f3bdeb830e7c6fd0c09)
* Using the ftp.osuosl.org mirror via HTTP (http://mirrors.kernel.org/opensuse/distribution/SL-10.1/inst-source/)
* Using the ftp.osuosl.org mirror via FTP
* Using VNC-based installation rather than local desktop
* Using the mirrors.kernel.org mirror via HTTP (http://ftp.osuosl.org/pub/opensuse/distribution/SL-10.1/inst-source/) 
* Using the mirrors.kernel.org mirror via FTP

CD-based install worked just fine. This problem can be replicated and demonstrated if necessary.

Thanks,

-Justin Grote

Comment 1 Justin Grote 2006-05-13 16:50:18 UTC

y2logs forthcoming after I try this again. This is also a possible duplicate of bug 170479.

Comment 2 Justin Grote 2006-05-13 16:54:03 UTC


*** This bug has been marked as a duplicate of 155354 ***

Comment 3 Justin Grote 2006-05-13 17:07:47 UTC

Resolved after upping the VMWare allocated RAM to 512MB from default of 256MB. Apparently processing the package list is too much for 256MB of RAM. Recommend a warning be added to the ISO file for next release if RAM is detected at 256M or lower.