Bug 115488 - Cannot read package data from network installation media
Summary: Cannot read package data from network installation media
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 4
Hardware: PowerPC All
: P5 - None : Normal
Target Milestone: ---
Assignee: Michael Andres
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-06 19:04 UTC by Leah Cunningham
Modified: 2005-09-07 17:52 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2log from this system (208.19 KB, text/plain)
2005-09-06 19:05 UTC, Leah Cunningham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leah Cunningham 2005-09-06 19:04:53 UTC
I am starting a network installation using a boot command like:

install install=http://<server>/suse/ppc10

I set up the installation sources exactly as described in this article with
loopback ISO's and symlinks as described: 
http://www.opensuse.org/index.php/Network_Installation_Source

The installation starts fine, but when we get to the Installation Settings
screen, the Software selection reads "Cannot read package data fron installation
media. Media error?"
Comment 1 Leah Cunningham 2005-09-06 19:05:19 UTC
Created attachment 48990 [details]
y2log from this system
Comment 2 Leah Cunningham 2005-09-06 19:15:23 UTC
It appears that if I change the yast2 directory at the media root with the order
and instorder files to 'yast' the packages are detected correctly.  I made a
note on the doc page, but am unsure if the directory is supposed to be named
yast2 or if yast is correct...

cd <inst-srcdir>
mkdir yast
echo cd1 cd1 > yast2/instorder
echo cd1 cd1 > yast2/order
Comment 3 Leah Cunningham 2005-09-06 19:18:38 UTC
er, rather:

mkdir yast
echo cd1 cd1 > yast/instorder
echo cd1 cd1 > yast/order
Comment 4 Jiří Suchomel 2005-09-07 06:55:02 UTC
Michael, could you confirm this?
Comment 5 Klaus Kämpf 2005-09-07 07:01:25 UTC
I'm rather puzzled by comments #2 and #3. If you're doing an NFS install, the 
second column in the instorder file should be a directory path. 
Comment 6 Klaus Kämpf 2005-09-07 07:07:23 UTC
Sorry, it seems to be an HTTP install.   
The logs show that the installation source is not set up correctly. YaST cant   
read the package metadata files, e.g.:   
   
HTTP return code: 404   
(URL:http://10.255.0.27/suse/ppc10/suse/setup/descr/packages)   
   
I guess the "install=http://<server>/suse/ppc10" boot parameter should read 
"install=http://<server>/suse/ppc10/cd1" 
                                   ^^^^ 
 
Leah, please check the directory layout of your HTTP server. 
Comment 7 Leah Cunningham 2005-09-07 17:03:37 UTC
According to the document at
http://www.opensuse.org/index.php/Network_Installation_Source if you put a
yast2/order file containing the line "cd1 cd1" yast should check the cd1
directory for the package info.  As I mentioned above, this did not work, but
changing the name of the directory from yast2 to yast1 the order file did work
and it was not a problem.

This may not even be valid as it might be a mistake in that document, but if it
used to be yast2 and now the installer uses yast for that directory name, then
maybe yast should look at both for backwards compatibility.  Or, maybe the
document was just wrong, I just wasn't sure.
Comment 8 Michael Andres 2005-09-07 17:52:40 UTC
The document is wrong. The order file is retrieved and evaluated by
Packages.ycp. It's 'yast/order' and AFAIK nothing else (neiter yast2 nor yast1).

Fixed http://www.opensuse.org/index.php/Network_Installation_Source.