Description of problem: 22 Alpha TC5 Workstation netinst uses Fedora Cloud Server as default software selection. It should use Workstation instead. Version-Release number of selected component (if applicable): Fedora-Workstation-netinst-x86_64-22_Alpha_TC5.iso How reproducible: Always Steps to Reproduce: 1. boot workstation netinst, choose language Actual results: Fedora Cloud Server is chosen in software selection by default Expected results: Workstation package set should be used Additional info: I propose this as F22 Beta Blocker because it violates the beta criterion 'Default package set': When installing with a dedicated installer image for a specific Fedora flavor, the default package set must be the correct set for that flavor.
+1 BetaBlocker based on criteria cited.
Discussed at today's blocker review meeting [1]. This bug was accepted as Beta Blocker - This bug is a clear violation of the beta criterion: "When installing with a dedicated installer image for a specific Fedora flavor, the default package set must be the correct set for that flavor." http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-02/
This is fixed in Alpha RC3 (gold). Default is Workstation. I think this was probably caused by 1196504.
I encountered this bug with F22 Beta RC3, when trying PXE boot.
Created attachment 1015237 [details] screenshot of anaconda minimal install is selected instead of workstation
Created attachment 1015238 [details] anaconda.log
Created attachment 1015239 [details] dnf.log
Created attachment 1015241 [details] hawkey.log
Created attachment 1015242 [details] packaging.log
Created attachment 1015243 [details] program.log
Created attachment 1015244 [details] syslog
I've seen it sometimes in bare metal testing of various Beta images, but not consistently, and it rarely or never seems to happen in a VM - I just booted the x86_64 image in a VM and it's showing Workstation, for instance. Unfortunately there always seemed to be something else that needed firefighting and I never found time to get to the bottom of it :( I guess we need to know how common this is...
I received Workstation package set by default 5 times out of 5 attempts, using a VM. I believe the reason is that Lukas's laptop is affected by bug 1212009 and this seems to be a side-effect of having the network down during anaconda initialization. Testing...
Ditto here: 5 VM boots, 5 metal boots (with network), all Workstation. With network cable disconnected, I get 'error setting up base repository', obviously. After connecting the cable and doing the 'set it to http://foo then set it back to Closest Mirror' trick on INSTALLATION SOURCE, I get 'Nothing selected' for SOFTWARE SELECTION. Which, eh, dunno if it should be called a 'bug' or not, but definitely not a blocker.
So on a closer reading we noticed you said 'PXE boot', which makes this a completely different case. I'm not sure if it's a 'bug' or not that this customization isn't applied to a PXE boot case, but I wouldn't personally vote it as a Beta blocker, and it doesn't make sense to re-open this bug for it, as it's a different case. Can you please file it separately? Thanks.
FWIW I did test with PXE boot and 'inst.stage2=(path/to/Workstation)' and got Workstation as the default too.
(In reply to awilliam from comment #16) > FWIW I did test with PXE boot and 'inst.stage2=(path/to/Workstation)' and > got Workstation as the default too. Sorry for confusion, this was a issue with our local mirror. It did not contain product.img. This was an error on our end.