Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-13207

Kernel panic after rebuilding the initrd in os layer (waiting on Dracut)

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 5
    • Critical
    • No
    • None
    • None
    • Rejected
    • Sprint 236 - Update&Remoting, Sprint 237 - Update&Remoting, Sprint 238 - Update&Remoting, Sprint 239 - Update&Remoting, Sprint 240 - Update&Remoting
    • 5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      High level objective we are trying to achieve is to update kernel modules for storage and network  with OS layering. 

      We are able to install driver RPM as a OS layer but rebuilding the initrd is failing with kernel panic when OS is booted.

      To isolate the issue, we made a CoreOS layer that does nothing but rebuilding the initrd without adding any  kernel module. But we observed kernel panic after reboot. 

       

      Detailed steps

      --------------------

      (1) Created a Docker file. Here's the content of the Containerfile

       

      # oc adm release info --image-for rhel-coreos-8 4.12.14
      FROM quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:90625d9f3713874b50b91b59b61d3a9d7c39c61ef38da8147c5d9203edfe50a9
      RUN KERNEL=$(rpm -q kernel | cut -c 8-); dracut --reproducible -v --add 'ostree' -f --no-hostonly --omit-drivers 'nouveau' --omit 'nfs' --add 'iscsi' --add 'ifcfg' --add 'fips' --omit 'network-legacy' /lib/modules/$KERNEL/initramfs.img $KERNEL 

       

       

      (2) Built the image using docker file. We got some warning/error messages while building. 'Build log is attached,

       

      (3) Created a Machine Config:

      apiVersion: machineconfiguration.openshift.io/v1
      kind: MachineConfig
      metadata:
        labels:
          machineconfiguration.openshift.io/role: worker 
        name: initrd-trials
      spec:
        osImageURL: quay.io/pkoppa0/initrd_trials

      (4) ** Kernel panic was seen after reboot. Screenshot attached.

              rhn-support-jmarrero Joseph Marrero Corchado
              pkoppa@cisco.com Paniraja Koppa (Inactive)
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: