MicroShift - Topolvm-node pod CrashLoopBackOff issue in Azure VM

Solution Verified - Updated -

Issue

  • After first boot on Azure, MicroShift's POD topolvm-node-<id> can't start and reports a CrashLoopBackOff status while already running on Azure.

Environment

  • Red Hat Device Edge
  • Red Hat Enterprise Linux 9.2+
  • Red Hat build of MicroShift 4.14+
  • Azure Virtual Machine, created after exporting a VM from Hyper-V to vhd standard file.

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