-
Bug
-
Resolution: Done
-
Undefined
-
None
-
ACM 2.7.0
-
False
-
None
-
False
-
-
-
No
Description of problem:
Host Inventory Settings or CIM Enable documentation (technically equal) lead to misconfigured IngressController and so the agent-image-service can not be reached by external HTTP traffic and so the Discovery ISO can not be dowloaded.
Version-Release number of selected component (if applicable):
- 2.6+ for documentation
- 2.7 for its UI-counterpart (equal) Host Inventory Settings
How reproducible:
- AWS/IPI 100% (i.e. ACM's weekly acm-console-development-cluster)
- not sure about other cases, they depend on actual IngressController settings
Steps to Reproduce:
- Install ACM and so the Assisted Service is deployed but not functional till AgentServiceConfig resource is created. To do o
- Go to All Clusters --> Infrastructure --> Host Inventory
- check: the list is empty and the Create button is disabled
- Click Host Inventory Settings, a modal is shown
- Since the cluster is on AWS, let it configure for AWS
- click Configure
- Wait till the process is finished (a green Success alert is shown on the Host Inventory page)
- create a new Host Inventory
- Open Add host via Discovery ISO, pass till "wget" command to download the ISO is shown
- copy & run the wget locally
- the wget process hangs. No error, no ISO is downloaded
Actual results:
The ISO is not downloaded since the HTTP traffic does not reach the agent-image-service
Expected results:
The ISO is downloaded
Additional info:
In AWS/IPI, the default IngressController has no "spec.domain" set so matching all traffic to *.CLUSTER_DOMAIN.
The configuration above creates a new IngressController matching *nlb-apps.CLUSTER_DOMAIN, so conflicting with the default one.
Same issue can be when the default (or any other) IngressController has spec.domain set to a conflicting value wit the .nlb-apps..
- relates to
-
ACM-3023 CIM Enable section for potentially conflicting IngressControllers
- Closed