After upgrading to 4.13 from 4.12 node went into emergency mode in RHOCP4

Solution Verified - Updated -

Issue

  • After upgrading to 4.13 from 4.12 one of the worker node went into emergency mode in RHOCP 4

    ª    3.296696| systemdª1|: Starting CoreOS LUKS Opener...
         Starting ª0;1;39mCoreOS LUKS Openerª0m...
    ª    3.368077| coreos-cryptfsª711|: coreos-cryptfs: /dev/sda2 uses the 'cipher_null-ecb'
    ª    3.368143| coreos-cryptfsª711|: coreos-cryptfs: /dev/sda2 is not encrypted. Device will be mounted as device-mapper linear target.
    ª    3.389451| coreos-cryptfsª736|: WARN: unknown label12:21:12
    ª    3.392668| coreos-cryptfsª736|: failed ªsfd_dump:1| sfdisk --unit=S --dump /dev/sda
    ª    3.393100| coreos-cryptfsª756|: sfdisk: /dev/sda: does not contain a recognized partition table
    ª    3.393217| coreos-cryptfsª736|: FAILED: failed to dump sfdisk info for /dev/sda
    ª    3.394710| coreos-cryptfsª758|: blockdev: cannot open /dev/sda2: No such file or directory
    ª    3.395491|  sda:VOL1/  0XC184: sda1 sda2
    ª    3.403428| systemdª1|: Finished CoreOS LUKS Opener.
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.12
  • Red Hat Enterprise Linux CoreOS (RHCOS)
    • RHCOS-4.12

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