We need to add support to the 'upgrade' keyword for specifying what the rootfs to upgrade is rather than just blindly assuming "first in the list". This can then get used by preupgrade so that the right rootfs gets upgraded.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fixing version to align with rawhide again. Sorry for the noise.
*** Bug 474304 has been marked as a duplicate of this bug. ***
*** Bug 473271 has been marked as a duplicate of this bug. ***
*** Bug 477509 has been marked as a duplicate of this bug. ***
This support will be included in the next build of anaconda and pykickstart.
This isn't working in anaconda-11.5.0.28; error dialog claims "Kickstart command upgrade does not take any arguments". Moving to pykickstart; I'm pretty sure that's where this message comes from.
Created attachment 335372 [details] git formatted patch anaconda's kickstart.py is still using the FC3_Upgrade.parse() method to parse the 'upgrade' command. Attached patch should fix that.
Well that was stupid of me. Thanks for the patch. I've pushed this to master and storage, so we'll make sure to have it regardless of what we do with the storage stuff.
Any idea when preupgrade will add support to generate --root-device to ks.cfg? I just checked trac and in preugprade/__init__.py@dev,286 generate_kickstart() still hard codes a simple "upgrade".
I noticed that the feature seem to be removed with anaconda storage rewrite (commit e1a7fe9887886044b07587b3ec2caa2ff53ebfb2).
Radek, QE is also planning to make use of this feature. Can you add it back to the code please.
Should appear in version 12.0-1 of anaconda. Supports partition name (e.g. 'sda1', or 'Volgroup00-LogVol00') and UUID specified via 'UUID=<uuid>' (as obtained by blkid command).
Can someone confirm that this is present and functional in rawhide? And if so, please close this bug out.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping