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

Installation 4.16 cluster in AWS (self manage) with two master subnets failed at bootstrap phase.

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      * Previously, when you defined multiple bring-your-own (BYO) subnet CIDRs for the `machineNetwork` parameter in the `install-config.yaml` configuration file, the installation failed at the bootstrap stage. This situation occurred because the control plane nodes were blocked from reaching the machine config server (MCS) to get their necessary setup configurations. The root cause was an overly strict {aws-short} security group rule that limited MCS access to only the first specified machine network CIDR. With this release, a fix to the {aws-short} security group means that the installation succeeds when multiple CIDRs are specified in the `machineNetwork` parameter of the `install-config.yaml`. (link:https://issues.redhat.com/browse/OCPBUGS-57292[OCPBUGS-57292])
      Show
      * Previously, when you defined multiple bring-your-own (BYO) subnet CIDRs for the `machineNetwork` parameter in the `install-config.yaml` configuration file, the installation failed at the bootstrap stage. This situation occurred because the control plane nodes were blocked from reaching the machine config server (MCS) to get their necessary setup configurations. The root cause was an overly strict {aws-short} security group rule that limited MCS access to only the first specified machine network CIDR. With this release, a fix to the {aws-short} security group means that the installation succeeds when multiple CIDRs are specified in the `machineNetwork` parameter of the `install-config.yaml`. (link: https://issues.redhat.com/browse/OCPBUGS-57292 [ OCPBUGS-57292 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-57139. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-57039. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-54502. The following is the description of the original issue:
      —
      Description of problem:

         Installation 4.16 cluster in AWS (self manage) with two master subnets failed at bootstrap phase.

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

          4.16

      How reproducible:

      Steps to Reproduce:

          We are installing 4.16 cluster in AWS (self manage) & in install config we have two master subnets mentioned but we found that Security group attached to NLB is updated with only one master subnet to allow 22623 traffic for bootstrapping - because of this other master nodes in second subnet not able to communicate API for bootstrapping and cluster install fails: 

https://docs.openshift.com/container-platform/4.16/installing/installing_aws/ipi/installing-aws-private.html

      Actual results:

      Expected results:

      Additional info:

          Slack Threads raised for the issue - https://redhat-internal.slack.com/archives/C0646PP2U0M/p1741582588159709

              rh-ee-thvo Thuan Vo
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Yunfei Jiang Yunfei Jiang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: