Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-1551

MicroShift fails to start on isolated network (no Internet connectivity)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • openshift-4.14
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • uShift Sprint 240, uShift Sprint 241, uShift Sprint 242, uShift Sprint 243

      Description of problem:

      MicroShift fails to start on isolated network, created according to the instructions here: https://github.com/openshift/microshift/blob/main/docs/contributor/rhel4edge_iso.md#offline-mode

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

      4.14

      How reproducible:

      100%

      Steps to Reproduce:

      1. Run build.sh with `-embed_containers`
      2. Boot the ISO on `isolated` network
      

      Actual results:

      MicroShift does not start

      Expected results:

      MicroShift up and running

      Additional info:

      Aug 06 10:15:56 localhost.localdomain microshift[1294]: kubelet E0806 10:15:56.273798    1294 kubelet_node_status.go:728] "Failed to set some node status fields" err="can't get ip address of node localhost.localdomain. error: no default routes found in \"/proc/net/route\" or \"/proc/net/ipv6_route\"" node="localhost.localdomain"
      Aug 06 10:15:57 localhost.localdomain microshift[1294]: kubelet E0806 10:15:57.386614    1294 kubelet.go:2892] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: No CNI configuration file in /etc/cni/net.d/. Has your network provider started

              pliurh Peng Liu
              eslutsky Evgeny Slutsky
              Douglas Hensel
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: