Bug 492634

Summary: anaconda doesn't handle repo=hd::/path (preupgrade special case)
Product: [Fedora] Fedora Reporter: Will Woods <wwoods>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: ben, mishu, pjones, rmaximo, tcallawa, vanmeeuwen+fedora, vpvainio
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-04-16 13:17:55 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 492516, 495965    

Description Will Woods 2009-03-27 15:09:28 EDT
In Fedora 10 and earlier, there's a special case in yuminstall.py (see line 401 in current git) for handling "repo=hd:device:/path" when the system is booted with "preupgrade" on the commandline:

      (device, fstype, path) = m[3:].split(":")

  if flags.cmdline.has_key("preupgrade"):
      self._baseRepoURL = "file:///mnt/sysimage/%s" % path

As you can see, the device name is discarded and yum is instructed to get its packages from the given path, on the mounted system. Hence preupgrades are booted with:
  
  preupgrade repo=hd::/var/cache/yum/preupgrade [etc]

The new anaconda storage code needs to handle this special case, or provide another way for preupgrade to specify that the upgrade should get its packages from a certain path on the filesystem being upgraded - for example, "repo=file:///..."
Comment 1 Chris Lumens 2009-03-27 15:18:04 EDT
dlehman had a plan for dealing with this that involved making an empty path resolve to a FileDevice.
Comment 2 David Lehman 2009-04-16 12:09:57 EDT
Can you retest with anaconda-11.5.0.40-1 or later?
Comment 3 Will Woods 2009-04-16 13:17:55 EDT
I have an upgrade from F10->Rawhide (anaconda 11.5.0.44 IIRC) at the "Finishing upgrade process step." Everything seems have worked as expected.