Bug 490490
| Summary: | Using boot.iso leads to looking for repodata on boot.iso and failing | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> | ||||||||||
| Component: | yum | Assignee: | Seth Vidal <skvidal> | ||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | low | ||||||||||||
| Version: | rawhide | CC: | caillon, d.annesi, dcantrell, ffesti, james.antill, petersen, pjones, pmatilai, rmaximo, tim.lauridsen, tmraz, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2009-03-18 18:33:02 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 476774 | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 335381 [details]
storage log
Created attachment 335382 [details]
syslog
Created attachment 335383 [details]
program log
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 updates=http://caillon.fedorapeople.org/updates-490490.img 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 ? |
Created attachment 335380 [details] anaconda log 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.