Created attachment 514207 [details] yum log Description of problem: new install isos for qa validation result in being uninstallable. it seems that no repos are enabled and the only option given is to exit the installer. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 514209 [details] anaconda log
Created attachment 514210 [details] screen shot of how anaconda ends
It seems this is because anaconda was told that this isn't a beta ... # cat /.buildstamp [Main] Product=Fedora Version=16-test-20110721 BugURL=https://bugzilla.redhat.com IsBeta=False UUID=201107211254.x86_64 So it's not displaying the 'rawhide' repo ... [2011-07-21 09:57:40,243] WARN : Excluding devel repo Fedora - Rawhide - Developmental packages for the next Fedora release for non-devel anaconda Adding to F16Alpha since this clearly prevents all installations.
Created attachment 514257 [details] 0001-Additional-fix-to-ensure-interim-pre-release-beta-im.patch In addition to the proposed lorax fix [1], should the command-line defaults for is_beta also match the default API value? [1] df849d341927061b633dffc6101f2f4cb0342681
I believe dgilmore resolved this with a custom change to pungi.git. The latest compose images do not exhibit the reported problem. Should this be moved to POST or MODIFIED, pending an updated pungi package?
This seems to hit the alpha release criterion: The installer must boot (if appropriate) and run on all primary architectures from default live image, DVD, and boot.iso install media. Since any boot.iso media will fail with no option to add repos. +1 on alpha blocker
Discussed at the 2011-07-22 blocker bug review meeting. It is unclear whether this will be solved when Fedora 16 is branched and it will be reviewed again next week if this does affect branched installs.
Discussed in the 2011-07-29 blocker review meeting. Accepted as F16 alpha blocker based on perceived impact to branched composes. Fix is available, closing this issue is pending TC1 testing.
pungi-2.9-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/pungi-2.9-1.fc16
Package pungi-2.9-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pungi-2.9-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/pungi-2.9-1.fc16 then log in and leave karma (feedback).
pungi-2.9-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.