Description of problem: As of released version diskimage-builder-0.1.34-20.el7ost, an image built from RHEL 7 onto RHOS 6 will be built with an ext4 filesystem with 64bit enabled. Due to bug https://bugzilla.redhat.com/show_bug.cgi?id=1099237, this results in an unbootable filesystem. Until this bug is resolved, the only functional workaround to this problem is to build an ext3 filesystem (which is a still-more unfortunate solution than disabling 64bit.) The patch at https://review.openstack.org/#/c/165149/ will allow MKFS_OPTIONS to be extended, allowing the passage of the "-O ^64bit" flag, allowing the filesytem to boot. Backporting this patch will allow generation of HDP (and CDH) images on an ext4 filesystem on RHEL 6, which is critical to OpenStack Sahara's user flow. Version-Release number of selected component (if applicable): diskimage-builder-0.1.34-20.el7ost How reproducible: 100% Steps to Reproduce: 1. Download a RHEL 6.6 qcow2. 2. Using a filesystem address for DIB_CLOUD_IMAGES, create any rhel-based image ('disk-image-create "rhel vm" -n' for minimal test.) 3. Boot said image. Actual results: Extlinux reports no configuration file found (it cannot understand the filesystem, and points at the root directory. Even if the config, kernel, and ramdisk are moved to root, the kernel image is interpreted as corrupt.) The image is unbootable. Expected results: The image boots. Additional info:
The patch adds a new option which removes the 64 bit flag. The generation of RHEL6 images from RHEL7 has been successfully tested with: `disk-image-create "rhel vm" --mkfs-options "-O ^64bit" -n -o rhel6.qcow2` The patch does not change the default behavior (for example, a simple `disk-image-create -o fedora-20-dib.qcow2 vm fedora` works as before ) diskimage-builder-0.1.34-21.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0928.html