-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
4.13.z, 4.12.z, 4.14.z, 4.15
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-26051. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-25600. The following is the description of the original issue:
—
Description of problem:
The installer doesn’t do precheck if node architecture and vm type are consistent for aws and gcp, it works on azure
Version-Release number of selected component (if applicable):
4.15.0-0.nightly-multi-2023-12-06-195439
How reproducible:
Always
Steps to Reproduce:
1.Config compute architecture field to arm64 but vm type choose amd64 instance type in install-config 2.Create cluster 3.Check installation
Actual results:
Azure will precheck if architecture is consistent with instance type when creating manifests, like: 12-07 11:18:24.452 [INFO] Generating manifests files.....12-07 11:18:24.452 level=info msg=Credentials loaded from file "/home/jenkins/ws/workspace/ocp-common/Flexy-install/flexy/workdir/azurecreds20231207-285-jd7gpj" 12-07 11:18:56.474 level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: controlPlane.platform.azure.type: Invalid value: "Standard_D4ps_v5": instance type architecture 'Arm64' does not match install config architecture amd64 But aws and gcp don’t have precheck, it will fail during installation, but many resources have been created. The case more likely to happen in multiarch cluster
Expected results:
The installer can do a precheck for architecture and vm type , especially for heterogeneous supported platforms(aws,gcp,azure)
Additional info:
- clones
-
OCPBUGS-26051 AWS: The installer doesn’t precheck if node architecture and vm type are consistent
- Closed
- is blocked by
-
OCPBUGS-26051 AWS: The installer doesn’t precheck if node architecture and vm type are consistent
- Closed