Red Hat Bugzilla – Bug 853494
livemedia-creator fails on installing fedora-logos
Last modified: 2013-01-10 03:33:01 EST
Created attachment 608591 [details]
kickstart file used with livemedia-creator
Description of problem:
livemedia-creator fails on installing fedora-logos from the updates repo. After repeated attempts on different systems, this always fails on the same package. If I remove the updates repo from the kickstart file, the image compose completes successfully.
I have installed the fedora-logos package with no errors on an existing F17 system, so the package appears to be good.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. livemedia-creator \
--make-disk --no-virt --image-only --keep-image \
Installing fedora-logos-17.0.2-5.fc17.noarch (4 MB)
Fedora-related icons and pictures
anaconda 17.29 exception report
Traceback (most recent call first):
File "/usr/lib/python2.7/site-packages/pyanaconda/cmdline.py", line 114, in messageWindow
File "/usr/lib/python2.7/site-packages/pyanaconda/yuminstall.py", line 262, in callback
RuntimeError: (Error Installing Package)
A unpack error occurred when installing the fedora-logos package. This could indicate errors when reading the installation media. Installation cannot continue.
losetup: /dev/loop1: detach failed: Device or resource busy
2012-08-31 12:45:38,851: Install failed
Package installs and the rest of the compose completes without error.
I used a specific fedora repo because I was seeing other errors when using these mirror lists:
I think I've found the problem. Please note that the /boot partition in the example kickstart file is 'VFAT'. The version of fedora-logos in updates adds the following lines:
+ln -s background.png fireworks.png
VFAT does not support symbolic links, so I believe this will cause the install to fail. The original (F17 GA) version of fedora-logos did not include this symbolic link, so it installed without errors.
Which example kickstart? livemedia-creator's example has / and /boot on ext4. We shouldn't be using VFAT for anything other than the UEFI system partition, and that's mounted on /boot/efi/ not /boot.
The example kickstart file is the one attached to this BZ, and which may be used with livemedia-creator to reproduce the error. It uses:
part /boot --size 255 --fstype vfat --asprimary --label=boot
Some devices we install require a VFAT /boot partition (boot loader requirement).
It appears that this issue is due to a change in the fedora-logos package, and not specific to livemedia-creator, so I have moved it to that package.
I suppose we'll do a cp -a instead of a symbolic link. Frickin frackin legacy filesystem trash.
Perhaps we could try the symbolic link, and only copy if it failed?
I'm sorry, but we're still stuck with some legacy file systems, at least for now.
No, because the symlink happens during package generation time. It tries to write out the package manifest including symlinks, and fails on VFAT, but not in a fatal way (that file just doesn't get written out).
fedora-logos-17.0.3-1.fc17 has been submitted as an update for Fedora 17.
fedora-logos-17.0.3-1.fc18 has been submitted as an update for Fedora 18.
Not sure that changing this is a good idea - /boot has to be a POSIX filesystem, using vfat for it isn't supported.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedora-logos-17.0.3-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
fedora-logos-17.0.3-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.