Description of problem: When using livemedia-creator to create a disk image with the following command: livemedia-creator \ --make-disk --no-virt --image-only --keep-image \ --ks=/root/F17-minimal.ks The kickstart file defines the following partitions: part /boot --size 255 --fstype ext3 --label=boot part swap --size 511 --label=swap part / --size 3327 --fstype ext4 --label=rootfs which were created as expected. The following /etc/fstab entries were created on the image: UUID=f9360b1d-f56c-4b52-ab6b-58775bf57a17 / ext4 defaults 1 1 UUID=5f9bb5f2-a818-4e72-aefc-cd2c304726a6 /boot ext3 defaults 1 2 /dev/mapper/diskt9BQ8tp3 swap swap defaults 0 0 The entry for swap should not reference "/dev/mapper/disk<tmpstring>". Version-Release number of selected component (if applicable): anaconda-17.21-1.fc17 How reproducible: Always: Steps to Reproduce: 1. (see description above) Actual results: /etc/fstab includes: /dev/mapper/diskt9BQ8tp3 swap swap defaults 0 0 Expected results: No "/dev/mapper/..." entry for swap. Additional info: Via email: pyanaconda.storage.devices.DMLinearDevice should use pyanaconda.storage.devices.StorageDevice.fstabSpec instead of inheriting from DMDevice.
David, Try running it again, but this time add the following to the livemedia-creator command line: --anaconda-arg \ "updates=http://dlehman.fedorapeople.org/updates/updates-818352.0.img" Let me know how it goes.
After applying the patch you posted to the email list, I rebuilt anaconda and did a test run. The swap entry in /etc/fstab now uses the UUID, as expected. Please push this patch and I think we can mark this one fixed. Thank you.
anaconda-17.26-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.26-1.fc17
Package anaconda-17.26-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.26-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7623/anaconda-17.26-1.fc17 then log in and leave karma (feedback).
I tested anaconda-17.26-1.fc17 on a Trim Slice system, and it resolves this issue. Thank you.
anaconda-17.26-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.