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

Agent-based install on vSphere with multiple workers fails

XMLWordPrintable

    • Important
    • No
    • Sprint 244
    • 1
    • Rejected
    • True
    • Hide

      None

      Show
      None
    • Hide
      Previously, the `assisted-service` on the bootstrap machine became unavailable after the bootstrap node rebooted, preventing any communication from the `assisted-installer-controller`. This stopped the `assisted-installer-controller` from removing uninitialized taints from worker nodes, causing the cluster installation to hang waiting on cluster Operators.

      With this update, the `assisted-installer-controller` can remove the uninitialized taints even if `assisted-service` becomes unavailable, and the installation can proceed. (link:https://issues.redhat.com/browse/OCPBUGS-20049[*OCPBUGS-20049*])
      Show
      Previously, the `assisted-service` on the bootstrap machine became unavailable after the bootstrap node rebooted, preventing any communication from the `assisted-installer-controller`. This stopped the `assisted-installer-controller` from removing uninitialized taints from worker nodes, causing the cluster installation to hang waiting on cluster Operators. With this update, the `assisted-installer-controller` can remove the uninitialized taints even if `assisted-service` becomes unavailable, and the installation can proceed. (link: https://issues.redhat.com/browse/OCPBUGS-20049 [* OCPBUGS-20049 *])
    • Bug Fix
    • Done

      Description of problem:

      Agent-based install on vSphere with multiple workers fails

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

      4.13.4

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create agent-config, install-config for 3 master, 3+ worker cluster
2. Create Agent ISO image
3. Boot targets from Agent ISO

      Actual results:

      Deployment hangs waiting on cluster operators

      Expected results:

      Deployment completes

      Additional info:

      Multiple pods cannot start due to tainted nodes:"4 node(s) had untolerated taint {node.cloudprovider.kubernetes.io/uninitialized: true}"

              rwsu1@redhat.com Richard Su
              rhn-gps-tbonds Thomas Bonds
              Manoj Hans Manoj Hans
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: