Bug 853494
| Summary: | livemedia-creator fails on installing fedora-logos | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | D. Marlin <dmarlin> | ||||
| Component: | fedora-logos | Assignee: | Tom "spot" Callaway <tcallawa> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | anaconda-maint-list, bcl, jfeeney, mgracik, tcallawa | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-09-27 05:00:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
D. Marlin
2012-08-31 18:02:11 UTC
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: +pushd $RPM_BUILD_ROOT/boot/grub2/themes/system/ +ln -s background.png fireworks.png +popd 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. https://admin.fedoraproject.org/updates/fedora-logos-17.0.3-1.fc17 fedora-logos-17.0.3-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedora-logos-17.0.3-1.fc18 Not sure that changing this is a good idea - /boot has to be a POSIX filesystem, using vfat for it isn't supported. Package fedora-logos-17.0.3-1.fc18: * 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: https://admin.fedoraproject.org/updates/FEDORA-2012-14528/fedora-logos-17.0.3-1.fc18 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. |