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

Installer should not complain about API resolution when the domains resolved

XMLWordPrintable

    • Moderate
    • No
    • Sprint 253
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Searching CI turns up runs like this which log:

      level=warning msg=The bootstrap machine is unable to resolve API and/or API-Int Server URLs

      despite the gathere log-bundle saying resolution was fine:

      $ curl -s https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.15-e2e-gcp-ovn-upgrade/1721875076346810368/artifacts/e2e-gcp-ovn-upgrade/ipi-install-install-stableinitial/artifacts/log-bundle-20231107134325.tar | tar xOz log-bundle-20231107134325/bootstrap/services/bootkube.json | jq -r '.[] | .timestamp + "  " + (.stage // "-") + " " + .phase + " " + (.result // "-")' bootstrap/services/bootkube.json | sort | grep resolve
2023-11-03T10:26:53Z  resolve-api-int-url stage end success
2023-11-03T10:26:53Z  resolve-api-int-url stage start -
2023-11-03T10:26:53Z  resolve-api-url stage end success
2023-11-03T10:26:53Z  resolve-api-url stage start -
2023-11-03T10:47:30Z  resolve-api-int-url stage end success
2023-11-03T10:47:30Z  resolve-api-int-url stage start -
2023-11-03T10:47:30Z  resolve-api-url stage end success
2023-11-03T10:47:30Z  resolve-api-url stage start -

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

      Definitely 4.15, from that CI run. Likely all releases since the check landed in installer#5816.

      How reproducible:

      Untested, but from inspecting the code, I'd expect fairly reproducible.

      Steps to Reproduce:

      1. Feed the installer an impossible manifest (e.g. using a kind that does not exist).
      2. Try to install.
      3. See the installer gather bootstrap logs and analyze them.

      Actual results:

      level=warning msg=The bootstrap machine is unable to resolve API and/or API-Int Server URLs

      Expected results:

      Installer does not complain about API resolution unless API resolution is broken.

      Additional info:

      The check logic seems to be looking at overall success of the bootkube service. It should be updated to only check the success of the resolve-api-url and resolve-api-int-url steps in that service. Ideally with separate analysis steps, so you don't have to say "and/or" in the logged warning.

            rh-ee-bbarbach Brent Barbachem
            trking W. Trevor King
            Jianli Wei Jianli Wei
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: