Bug 812298 - appliance-creator fails with grub2
appliance-creator fails with grub2
Product: Fedora
Classification: Fedora
Component: appliance-tools (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: David Huff
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-04-13 06:26 EDT by Marko Myllynen
Modified: 2012-04-17 04:34 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-04-13 07:49:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
fed-appl.ks (467 bytes, text/plain)
2012-04-13 06:37 EDT, Marko Myllynen
no flags Details

  None (edit)
Description Marko Myllynen 2012-04-13 06:26:10 EDT
Description of problem:
On Fedora 17 / updates as of 2012-04-13:

[root@localhost ~]# getenforce 
[root@localhost ks]# appliance-creator -c fed-appl.ks -n F17-appl -v
Removing password for user root.
passwd: Success
/sbin/grub2-probe: error: unknown filesystem.
Auto-detection of a filesystem of /dev/mapper/loop2p1 failed.
Try with --recheck.
If the problem persists please report this together with the output of "/sbin/grub2-probe --device-map="/boot/grub2/device.map" --target=fs -v /boot/grub2" to <bug-grub@gnu.org>
Unable to create appliance : Unable to install grub2 bootloader
Unmounting directory /var/tmp/imgcreate-mBmNfj/install_root/
Losetup remove /dev/loop2

Version-Release number of selected component (if applicable):
Comment 1 Marek Goldmann 2012-04-13 06:31:02 EDT
Could you please attach the fed-appl.ks file?
Comment 2 Marko Myllynen 2012-04-13 06:37:26 EDT
Created attachment 577293 [details]
Comment 3 Marek Goldmann 2012-04-13 06:46:01 EDT

Please a add a bios boot partition as mentioned here: http://fedoraproject.org/wiki/Anaconda/Kickstart#bootloader And test again.
Comment 4 Marko Myllynen 2012-04-13 07:46:21 EDT
Thanks for pointing that out, the biosboot partition indeed fixes the issue:

part biosboot --fstype biosboot --size 1 --ondisk vda

Removing password for user root.
passwd: Success
Installation finished. No error reported.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.3.0-0.rc3.git7.2.fc17.x86_64
Found initrd image: /boot/initramfs-3.3.0-0.rc3.git7.2.fc17.x86_64.img
/etc/selinux/targeted/contexts/files/file_contexts: line 2352 has invalid context system_u:object_r:xfs_exec_t:s0
/etc/selinux/targeted/contexts/files/file_contexts: line 2585 has invalid context system_u:object_r:xfs_exec_t:s0
/etc/selinux/targeted/contexts/files/file_contexts: line 3162 has invalid context system_u:object_r:xfs_exec_t:s0
/etc/selinux/targeted/contexts/files/file_contexts: line 3610 has invalid context system_u:object_r:xfs_exec_t:s0
Unmounting directory /var/tmp/imgcreate-9gzrRx/install_root/
Losetup remove /dev/loop0
umount: /var/tmp/imgcreate-9gzrRx/install_root/sys/fs/selinux/load: not found

The last SELinux complaint is printed even with selinux --disabled, the former with selinux --permissive / selinux --enforcing.

Comment 5 Marek Goldmann 2012-04-13 07:49:53 EDT
I'm closing this issue now, the SELinux messages are separate thing, as IIRC, there is no SELinux policy written for appliance-creator.
Comment 6 Marko Myllynen 2012-04-17 04:34:23 EDT
Ok, fair enough, I opened a separate issue about the SELinux messages:


Note You need to log in before you can comment on or make changes to this bug.