Bug 1956428

Summary: ISO file format should be configurable by clusterdeployment
Product: OpenShift Container Platform Reporter: Ulrich Schlueter <uschlute>
Component: assisted-installerAssignee: Michael Filanov <mfilanov>
assisted-installer sub component: assisted-service QA Contact: Yuri Obshansky <yobshans>
Status: CLOSED DEFERRED Docs Contact:
Severity: unspecified    
Priority: medium CC: alazar, aos-bugs, atraeger
Version: 4.8   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AI-Team-Hive KNI-EDGE-4.8
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-20 14:54:57 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:
Embargoed:

Description Ulrich Schlueter 2021-05-03 16:36:43 UTC 
Description of problem:

The decision whether the InfraEnv resource for a clusterdeployment creates a minimal-iso or a full-iso version of the boot ISO for the cluster servers is currently made a Community Operator build time (by defining the subscription file) or latest at installation time (by modifying the subscription file ahead of a manual installation ). After encountering a problem with booting from minimal-iso for Dell hardware (https://bugzilla.redhat.com/show_bug.cgi?id=1955747 ) this turns out to be difficult to handle and not feasible for  the  multi-cluster/multi-customer setup we are looking for for OSD Baremetal 


Version-Release number of selected component (if applicable):


How reproducible:

Install the Community Edition Assisted Service from the OperatorHub and try to change the ISO format 

Steps to Reproduce:
1.
2.
3.

Actual results:

Format handled on Assisted Service instance level (install time setting)

Expected results:

Iso file format should be a parameter at clusterdeployment or InfraEnv creation time

Additional info:
Comment 1 Michael Filanov 2021-05-09 13:37:34 UTC 
@atraeger Is supporting only minimal-iso by default is a requirement? 
Do we want to make it part of the API with a default value to minimal-iso?
Comment 2 Avishay Traeger 2021-05-10 06:36:55 UTC 
Ulrich, can you please elaborate on why this makes your use case difficult/unfeasible?  Our reasoning was that it was logical for a given deployment to want to use either the full or the minimal ISO, not both, and therefore we wanted to simplify the user-facing API.
Comment 3 Ulrich Schlueter 2021-05-14 14:34:30 UTC 
Two points:
- this BZ is a knock-on effect of https://bugzilla.redhat.com/show_bug.cgi?id=1955747 where booting from the minimum-iso failed, but booting from the full-iso worked. Meanwhile that BZ is at least explained as a server side bug and worked around so this change is not required at the moment.

- The idea is not to have both formats at the same time, but making the iso format configurable without reinstalling the assisted-service operator. This would have appeared to be a useful feature in a scenario where many clusters are installed from the same operator instance (which is what I'm testing).
Comment 4 Ronnie Lazar 2021-05-18 09:48:31 UTC 
Should this be configured in ClusterDeployment or on InfraEnv?
Comment 5 Avishay Traeger 2021-05-18 09:58:20 UTC 
It can be configured on the InfraEnv if we add the API to do so.  Our assumption (which I still believe is correct) was that any given deployment would use a single format.
Comment 6 Ronnie Lazar 2021-05-20 14:54:57 UTC 
This is duplicate of https://issues.redhat.com/browse/MGMT-3444
Closing this BZ