The resource-topology-exporter (RTE) container fails to start with error "transport: Error while dialing: dial unix /host-podresources/kubelet.sock: connect: permission denied".

Solution Verified - Updated -

Issue

  • NUMA-aware scheduler fails to start as the resource-topology-exporter container fails to start since it can not access the kubelet socket.
  • The RTE pods gets stuck on CrashLoopBackOff due an selinux issue.
  • numaresourcesoperator-xxxx POD is in CrashLoopBackOff status.

Environment

  • Red Hat Openshift Container Platform (OCP) 4.16.25, 4.16.26
  • Red Hat Openshift Container Platform (OCP) 4.17.7, 4.17.8
  • numaresources-operator.v4.17.1

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