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

[AWS][4.13] installer get stuck if BYO private hosted zone is configured

XMLWordPrintable

    • Yes
    • Sprint 234, Sprint 235
    • 2
    • Approved
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Bug Fix
    • Done

      Description of problem:

      Installer get stuck at the beginning of installation if BYO private hosted zone is configured in install-config, from the CI logs, installer has no actions in 2 hours.

Errors:
level=info msg=Credentials loaded from the "default" profile in file "/var/run/secrets/ci.openshift.io/cluster-profile/.awscred"
185
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:164","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","severity":"error","time":"2023-03-05T16:44:27Z"}

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

      4.13.0-0.nightly-2023-03-23-000343

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create an install-config.yaml, and config byo private hosted zone
2. Create the cluster

      Actual results:

      installer showed the following message and then get stuck, the cluster can not be created.

level=info msg=Credentials loaded from the "default" profile in file "/var/run/secrets/ci.openshift.io/cluster-profile/.awscred"

      Expected results:

      create cluster successfully

      Additional info:

       

            [OCPBUGS-11261] [AWS][4.13] installer get stuck if BYO private hosted zone is configured

            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 (Important: OpenShift Container Platform 4.13.0 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:1326

            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 (Important: OpenShift Container Platform 4.13.0 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:1326

            Yunfei Jiang added a comment -

            padillon It looks good to me to move to VERIFIED, I tested on 4.13.0-0.nightly-2023-05-02-134729 and all of them got passed.

            Yunfei Jiang added a comment - padillon It looks good to me to move to VERIFIED, I tested on 4.13.0-0.nightly-2023-05-02-134729 and all of them got passed.

            Patrick Dillon added a comment -

            yunjiang-1 I moved the status of this to verfiied based on the cherry-pick approval from jianlin: https://github.com/openshift/installer/pull/7129#issuecomment-1522633745

            Let me know if that is not right.

            Patrick Dillon added a comment - yunjiang-1 I moved the status of this to verfiied based on the cherry-pick approval from jianlin: https://github.com/openshift/installer/pull/7129#issuecomment-1522633745 Let me know if that is not right.

              sdasu@redhat.com Sandhya Dasu
              yunjiang-1 Yunfei Jiang
              Yunfei Jiang Yunfei Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: