Created attachment 669365 [details] Libreport files Description of problem: Anaconda crashes because it can't find @core packages. @core package repo tree is not the primary tree Version-Release number of selected component (if applicable): 18-TC3 How reproducible: Steps to Reproduce: 1. Installation from CD-rom with a repo tree on the CD. 2. repo tree on the CD does not contain @core package definition. 3. @core package definition is on a repo tree that is defined on the kickstart file. 4. System crahes because it can't find @core package definition. 5. It looks like anaconda wants the @core tree in the repo on the primary repo -tree. This was not the case in F17. This installation setup I use, works fine in F17. Actual results: Anaconda can't find @caore group. Expected results: Anaconda should look at other repo's, where @core group is and install from there. Additional info:
Please attach your logs as individual, uncompressed attachments. Doing anything else prevents us from searching bugzilla later.
Created attachment 671665 [details] Anaconda.log
Created attachment 671666 [details] ifcfg.log
Created attachment 671667 [details] packaging.log
Created attachment 671668 [details] program.log
Created attachment 671669 [details] storage.log
Created attachment 671670 [details] ks.cfg
Created attachment 671681 [details] reason.log
I see multiple lines in your packaging.log about failing to get group metadata from each repo. Can you please confirm that the repos you are installing from are constructed correctly, including the group metadata? Thanks.
Created attachment 672345 [details] Packaging.log from 18-TC4 install Retested this with 18-TC4 and ran into the same error. Attached is the packaging.log from this attempt. In the same setting I did a manual install from the network installation repo. This install was succesfull, so in the TC4 case I can confirm, that the network repo is not the cause of the problem. In the log there is an error concerning the updates repo, because this is not there on my network. But as the core packages are on the main repo, this can not at least should not be the problem I would say. As I can reproduce this here, if you have any particular questions or tests, I can run a new test for that.
Newer log shows that all of the repodata failed to download. This was a problem with the mirror.