Created attachment 897040 [details] This is very similar to (actually derived from it) fedora-spin-kickstarts/fedora-x86_64-cloud.ks Description of problem: anaconda seems to get stuck in a loop when I try ot build the fedora cloud image with Fedora 19's lmc. Version-Release number of selected component (if applicable): $ rpm -q anaconda lorax anaconda-19.30.13-1.fc19.x86_64 lorax-19.6-1.fc19.x86_64 boot.iso is Fedora 19's boot.iso How reproducible: always Steps to Reproduce: 1. Use attached kickstart and 2. sudo -E livemedia-creator --make-disk --iso boot.iso --ks ovirt-appliance-fedora.ks --ram=3048 --vcpus=4 3. Actual results: a zillion times: 08:28:41,471 DEBUG anaconda: In a non-main thread, sending a message with exception data 08:28:41,471 DEBUG anaconda: running handleException 08:28:41,471 DEBUG anaconda: Gtk cannot be initialized 08:28:41,471 DEBUG anaconda: In a non-main thread, sending a message with exception data 08:28:41,472 DEBUG anaconda: running handleException 08:28:41,472 DEBUG anaconda: Gtk cannot be initialized 08:28:41,472 DEBUG anaconda: In a non-main thread, sending a message with exception data 08:28:41,472 DEBUG anaconda: running handleException 08:28:41,473 DEBUG anaconda: Gtk cannot be initialized 08:28:41,473 DEBUG anaconda: In the main thread, running exception handler Expected results: Fedora cloud image is installed Additional info:
Created attachment 897041 [details] Complete log
08:35:15,173 DEBUG yum: Checking for virtual provide or file-provide for dracut-config-generic I think your url/repo setup is wrong. you can't just point to the updates repo, some things haven't been updated since the release. I'd do this: url = primary fedora release repo update = fedora updates repo ovirt = ovirt repo