Bug 812298

Summary: appliance-creator fails with grub2
Product: [Fedora] Fedora Reporter: Marko Myllynen <myllynen>
Component: appliance-toolsAssignee: David Huff <dhuff>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: apevec, dhuff, mgoldman, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-13 11:49:53 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:
Attachments:
Description Flags
fed-appl.ks none

Description Marko Myllynen 2012-04-13 10:26:10 UTC 
Description of problem:
On Fedora 17 / updates as of 2012-04-13:

[root@localhost ~]# getenforce 
Permissive
[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>
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):
appliance-tools-006.1-2.fc17
Comment 1 Marek Goldmann 2012-04-13 10:31:02 UTC 
Could you please attach the fed-appl.ks file?
Comment 2 Marko Myllynen 2012-04-13 10:37:26 UTC 
Created attachment 577293 [details]
fed-appl.ks
Comment 3 Marek Goldmann 2012-04-13 10:46:01 UTC 
Marko,

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 11:46:21 UTC 
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
done
/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
99%
Unmounting directory /var/tmp/imgcreate-9gzrRx/install_root/
Losetup remove /dev/loop0
Finished
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.

Thanks.
Comment 5 Marek Goldmann 2012-04-13 11:49:53 UTC 
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 08:34:23 UTC 
Ok, fair enough, I opened a separate issue about the SELinux messages:

https://bugzilla.redhat.com/show_bug.cgi?id=813200