It would be helpful, if document states that somewhere that a normal qcow2 image can also be directly deployed as a user image. I was facing challenges in generating Initrd and vmlinuz images and tried normal rhel qcow2 image and it worked. Reported by: bmw_vibhor https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/bare_metal_provisioning/configuring-the-bare-metal-provisioning-service-after-deployment#annotations:e1716da7-a86b-4f9f-bcf2-9c3e76d2805e
The customer is right, the docs referenced are talking about use of a partition image, and not a whole disk image. I think it is in large part as a hold-over as the RHEL qcow2 image in the past didn't work when the documentation was originally written. I think we need to: 1) Highlight the instructions cover the generation of a "partition image 2) Indicate that deployment of whole disk qcow2 images is a possibility as well, if appropriately uploaded to glance. i.e. no kernel and no ramdisk file associated in the uploaded glance image.
Updated content available on the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/bare_metal_provisioning/assembly_configuring-the-bare-metal-provisioning-service-after-deployment#proc_creating-images-for-launching-bare-metal-instances_bare-metal-post-deployment https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/bare_metal_provisioning/assembly_configuring-the-bare-metal-provisioning-service-after-deployment#proc_creating-images-for-launching-bare-metal-instances_bare-metal-post-deployment