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

aws autoscaler broken with dhcp option domain-name

XMLWordPrintable

    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the approval mechanism for certificate signing requests (CSRs) failed because the node name and internal DNS entry for a CSR did not match in terms of character case differences. With this release, an update to the approval mechanism for CSRs skips case-sensitive checks so that a CSR with a matching node name and internal DNS entry does not fail the check because of character case differences. (link:https://issues.redhat.com/browse/OCPBUGS-43312[*OCPBUGS-43312*])
      Show
      * Previously, the approval mechanism for certificate signing requests (CSRs) failed because the node name and internal DNS entry for a CSR did not match in terms of character case differences. With this release, an update to the approval mechanism for CSRs skips case-sensitive checks so that a CSR with a matching node name and internal DNS entry does not fail the check because of character case differences. (link: https://issues.redhat.com/browse/OCPBUGS-43312 [* OCPBUGS-43312 *])
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-44705. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-44629. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-43312. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-36871. The following is the description of the original issue:
      —
      Description of problem:

      Customer has a cluster in AWS that was born on an old OCP version (4.7) and was upgraded all the way through 4.15.
During the lifetime of the cluster they changed the DHCP option in AWS to "domain name". 
During the node provisioning during MachineSet scaling the Machine can successfully be created at the cloud provider but the Node is never added to the cluster. 
The CSR remain pending and do not get auto-approved

This issue is eventually related or similar to the bug fixed via https://issues.redhat.com/browse/OCPBUGS-29290

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

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

         CSR don't get auto approved. New nodes have a different domain name when CSR is approved manually.

      Expected results:

          CSR should get approved automatically and domain name scheme should not change.

      Additional info:

              joelspeed Joel Speed
              openshift-crt-jira-prow OpenShift Prow Bot
              Huali Liu Huali Liu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: