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

Slow network causes metal IPI bootstrap to fail

XMLWordPrintable

    • Moderate
    • None
    • 1
    • Metal Platform 259
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when installing a cluster on bare metal using installer provisioned infrastructure, the installation could time out if the network to the bootstrap virtual machine is slow. With this update, the timeout duration has been increased to cover a wider range of network performance scenarios. (link:https://issues.redhat.com/browse/OCPBUGS-41500[*OCPBUGS-41500*])
      Show
      * Previously, when installing a cluster on bare metal using installer provisioned infrastructure, the installation could time out if the network to the bootstrap virtual machine is slow. With this update, the timeout duration has been increased to cover a wider range of network performance scenarios. (link: https://issues.redhat.com/browse/OCPBUGS-41500 [* OCPBUGS-41500 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-39081. The following is the description of the original issue:
      —
      If the network to the bootstrap VM is slow, the extract-machine-os.service can time out (after 180s). If this happens, it will be restarted but services that depend on it (like ironic) will never be started even once it succeeds. systemd added support for Restart:on-failure for Type:oneshot services, but they still don't behave the same way as other types of services.

      This can be simulated in dev-scripts by doing:

      sudo tc qdisc add dev ostestbm root netem rate 33Mbit

            dhiggins@redhat.com Derek Higgins
            openshift-crt-jira-prow OpenShift Prow Bot
            Jad Haj Yahya Jad Haj Yahya
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: