This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 431132

Summary: hdiso installs fail due to "missing repodata" - isos not mounted
Product: [Fedora] Fedora Reporter: Will Woods <wwoods>
Component: anacondaAssignee: Chris Lumens <clumens>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: jane.lv
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: 2008-02-12 16:16:03 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 235706    
Attachments:
Description Flags
anaconda-hdiso.log none

Description Will Woods 2008-01-31 16:50:09 EST 
I attempted a hdiso install of Fedora 9 Alpha for i386. Booted the machine from
the Rescue image. The CD isos were on a (vfat-formatted) USB drive. 

Told loader to fetch images from sdb1, in the directory 9-Alpha/Fedora/i386/iso
and it happily loaded stage2 and continued into the GUI. anaconda.log has the
following message:

19:49:11 INFO    : Found hd stage2, copying /tmp/loopimage///images/stage2.img
in RAM as stage2

So the installer *did* find sdb1 and mounted disc1 just fine.

I did the normal steps - choose timezone, partition drive, etc. When it tried to
get repo metadata, the installer popped up a message like:

"Unable to read package metadata. ... Cannot retrieve repository metadata
(repomd.xml) for repository: anaconda-FedoraBase-$(datestamp).i386. Please
verify its path and try again. [Abort]"

Checked tty2 - /dev/sdb1 was not mounted, and neither were any of the ISO images.

I'm attaching the anaconda.log from that system.
Comment 1 Will Woods 2008-01-31 16:50:09 EST 
Created attachment 293654 [details]
anaconda-hdiso.log
Comment 2 Chris Lumens 2008-02-25 15:45:59 EST 
*** Bug 433269 has been marked as a duplicate of this bug. ***