Red Hat Bugzilla – Bug 490490
Using boot.iso leads to looking for repodata on boot.iso and failing
Last modified: 2014-01-21 18:08:46 EST
Created attachment 335380 [details]
We don't seem to be falling back to network installs. This is just a simple boot of boot.iso and "next next next". Attaching logs.
Created attachment 335381 [details]
Created attachment 335382 [details]
Created attachment 335383 [details]
yum/__init__.py:341. yum thinks the repo config files should be in /mnt/sysimage/etc/anaconda.repos.d but anaconda puts them in /etc/anaconda.repos.d According to Seth in IRC, there used to be a test here that'd check the existence of the directory before reading the config files and that test needs to be added back.
fixed in upstream yum and I'll build a new rawhide build in a moment.
I'm nitpicky, putting this back into modified until it has actually been tagged for the beta.
Created an updates.img with the new yum python modules from http://koji.fedoraproject.org/koji/buildinfo?buildID=94362 and booted using
I can confirm this fixes this issue.
The today's rawhide boot.iso seems fixed in regards to this issue.
Fedora 11 on a Dell T610.
The boot do not work; it hang up with message "Press ENTER to begin installation".
I substitute vesamenu.c32 with the version on fedora 10 and resolve the boot.
After boot and partitioed with default hard disk ( Controller PERC/1, raid 5 )
i get the following error:
"Unable to read group information from repositories. This
is a problem with the generation of your install tree."
And now ?