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

MCO should fall back to us-east-1 for AWS bootimages if no region specific-AMI exists

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 2
    • Moderate
    • None
    • None
    • MCO Sprint 270
    • 1
    • Done
    • Bug Fix
    • Hide
      * Previously, if you launched a cluster for an AWS region for which an Amazon Machine Images (AMI) is not available, the installation could fail. This was problematic for OKD, which does not have an AMI for all of the AWS regions. This fix adds a default region that is used if in case the cluster was launched with a region is not available. (link:https://issues.redhat.com/browse/OCPBUGS-55231[OCPBUGS-55231])
      Show
      * Previously, if you launched a cluster for an AWS region for which an Amazon Machine Images (AMI) is not available, the installation could fail. This was problematic for OKD, which does not have an AMI for all of the AWS regions. This fix adds a default region that is used if in case the cluster was launched with a region is not available. (link: https://issues.redhat.com/browse/OCPBUGS-55231 [ OCPBUGS-55231 ])
    • None
    • None
    • None
    • None

      On OKD, AMIs for all regions are not published in the installer's scos.json. This causes failures during boot image updates, when the region specified in the installconfig isn't found in the boot images configmap. We should add a default,mirroring how the installer works in such cases. 

              djoshy David Joshy
              djoshy David Joshy
              None
              None
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: