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

install OCP on AWS region us-east-1 is always returning failures when non-zone is set

XMLWordPrintable

    • None
    • 2
    • OpenShift SPLAT - Sprint 263, OpenShift SPLAT - Sprint 265
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the installation of an AWS cluster on AWS emit failures when discovering supported EC2 Instance Types in the zone us-east-1e (use1-az3). With this release, a fix ensures the zone use1-az3 is skipped in the availability zone discovery, when no zones is specified in install-config, preventing cluster configuration in zones which does not offer required EC2 Instance Types by OpenShift.
      Show
      Previously, the installation of an AWS cluster on AWS emit failures when discovering supported EC2 Instance Types in the zone us-east-1e (use1-az3). With this release, a fix ensures the zone use1-az3 is skipped in the availability zone discovery, when no zones is specified in install-config, preventing cluster configuration in zones which does not offer required EC2 Instance Types by OpenShift.
    • Bug Fix
    • In Progress

      Description of problem:

          openshift-install is always raise WANING when install a cluster on AWS Region us-east-1 with default configuration, no zones is set.
      
      ~~~
      WARNING failed to find default instance type for worker pool: no instance type found for the zone constraint 
      WARNING failed to find default instance type: no instance type found for the zone constraint 
      ~~~
      
      The process to discover zones list all zones in the region, then tries to describe instance type offerings across all zones from a list of supported instance types by installer.
      
      The problem that there is an "dead" zone in this region, the us-east-1e (ID use1-az3), which does not support any instance type we support, leading in creating infra resources in one zone which isn't useful as may not able to launch supported instance types there.

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

      * (?)    

      How reproducible:

      always    

      Steps to Reproduce:

          1. create install-config targeting AWS region us-east-1, without setting zones (default)
          2. create manifests, or create cluster
        
          

      Actual results:

      ~~~
      WARNING failed to find default instance type for worker pool: no instance type found for the zone constraint  WARNING failed to find default instance type: no instance type found for the zone constraint 
      ~~~
      
      The WARNING is raised, the install does not fail because the fallback instance type is supported across zones used to make Control Plane and Worker nodes

      Expected results:

      No WARNINGS/failures    

      Additional info:

       

              rhn-support-mrbraga Marco Braga
              rhn-support-mrbraga Marco Braga
              Gaoyun Pei Gaoyun Pei
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: