Why new install of MicroShift reports "Node not ready" in proxy environment?

Solution Verified - Updated -

Issue

*Why new install of MicroShift reports "Node not ready" ?
* MicroShift reports failure to pull the image "pinging container registry quay.io: Get \"https://quay.io/v2/\": EOF""

Nov 27 11:39:37 test.net microshift[19823]: kubelet E1127 11:39:37.246567   19823 remote_runtime.go:176] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = creating pod sandbox with name \"k8s_ovnkube-master-mb9gs_openshift-ovn-kubernetes_1c643722-509f-4189-aa43-af2865f19e37_0\": initializing source docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a473975a9daa31cb3d4805ea03f3e16818caecb073758d5c4982dc056c585e2a: pinging container registry quay.io: Get \"https://quay.io/v2/\": EOF"

Environment

  • Red Hat Enterprise Linux 9.3
  • Red Hat build of MicroShift 4.14

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content