Description of problem: The image name is hard coded to rhcos, which prevents users who do not have control of their images and their names from running the installer. How reproducible: always Steps to Reproduce: 1. Do not have image named rhcos 2. run installer 3. fail
@adahiya Do you mind if I take this bug?
This looks a RFE, `allow user to provide the image name for boot-image` on OpenStack.
Is the issue about uploading an image to glance under a name the user chooses, or about using an image from glance where the name is different from `rhcos`? In the "upload to glance" case, the user will anyway depend on someone with the right permission to upload to glance, and can ask to upload under a specific name. In the "download from glance" case, I think we can already override the image name by setting the OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE environment variable (to be verified). If so, then we have a workaround and this bz is basically a feature request to have the boot image selection in the install wizard. In both case I think we shouldn't try to squeeze it in 4.2 -- we're way past feature freeze.
After the discussions with PMs we decided not to implement this in 4.2, because there is a workaround to define OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE variable which allows to set another glance image name. This is explained in the user documentation. And in 4.3 we're going to implement auto image uploading, where installer automatically creates an image in glance. so all this image stuff will be hidden from users and they don't have to specify the image name at all.