Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-26051

AWS: The installer doesn’t precheck if node architecture and vm type are consistent

XMLWordPrintable

    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, installing a cluster on AWS failed when the specified machine instance type (`platform.aws.type`) did not support the machine architecture that was specified for control plane or compute machines (`controlPlane.architecture` and `compute.architecture`). With this update, the installation program now checks to determine if the machine instance type supports the specified architecture and displays an error message if it does not. (link:https://issues.redhat.com/browse/OCPBUGS-26051[*OCPBUGS-26051*])
      Show
      Previously, installing a cluster on AWS failed when the specified machine instance type (`platform.aws.type`) did not support the machine architecture that was specified for control plane or compute machines (`controlPlane.architecture` and `compute.architecture`). With this update, the installation program now checks to determine if the machine instance type supports the specified architecture and displays an error message if it does not. (link: https://issues.redhat.com/browse/OCPBUGS-26051 [* OCPBUGS-26051 *])
    • Bug Fix
    • Done

      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:

            [OCPBUGS-26051] AWS: The installer doesn’t precheck if node architecture and vm type are consistent

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.15.0 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2023:7198

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.15.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:7198

            OpenShift Jira Bot added a comment -

            Hi ,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            Lin Wang added a comment -

            verified on version(registry.build05.ci.openshift.org/ci-ln-3pnh2sk/release:latest) with pr merge which cluster bot built https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-aws-modern/1744212652055334912
            level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: [controlPlane.platform.aws.type: Invalid value: "m6i.xlarge": instance type supported architectures [amd64] do not match specified architecture arm64, compute[0].platform.aws.type: Invalid value: "m6i.xlarge": instance type supported architectures [amd64] do not match specified architecture arm64]

            Lin Wang added a comment - verified on version(registry.build05.ci.openshift.org/ci-ln-3pnh2sk/release:latest) with pr merge which cluster bot built https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-aws-modern/1744212652055334912 level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: [controlPlane.platform.aws.type: Invalid value: "m6i.xlarge": instance type supported architectures [amd64] do not match specified architecture arm64, compute [0] .platform.aws.type: Invalid value: "m6i.xlarge": instance type supported architectures [amd64] do not match specified architecture arm64]

            OpenShift Jira Bot added a comment -

            Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the "Target Backport Versions" field to indicate which version(s) will receive the fix.

            OpenShift Jira Bot added a comment - Looks like this bug is far enough along in the workflow that a code fix is ready. Customers and support need to know the backport plan. Please complete the " Target Backport Versions " field to indicate which version(s) will receive the fix.

              rdossant Rafael Fonseca dos Santos
              openshift-crt-jira-prow OpenShift Prow Bot
              Lin Wang Lin Wang
              Mike Pytlak Mike Pytlak (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: