Enabling kdump

Steps to enable kdump in IBM Storage Fusion.

About this task

Enable kdump before the Global data platform upgrade begins on the storage operators.

For any node drain issues, see Issues related to IBM Storage Fusion HCI System node drains.

As a prerequisite to run base64, you must install base64 or jq.

1. Create a MachineConfig YAML file, "kdump-worker.yaml" with the following information that configures and enables kdump.

   
   apiVersion: machineconfiguration.openshift.io/v1
   kind: MachineConfig
   metadata:
     labels:
       machineconfiguration.openshift.io/role: "worker"
     name: 00-printk-worker
   spec:
     config:
       ignition:
         version: 3.2.0
       storage:
         files:
           - contents:
               source: data:text/plain;charset=utf-8;base64,a2VybmVsLnByaW50ayA9IDM=
             mode: 0644
             overwrite: true
             path: "/etc/sysctl.d/00-printk.conf"

2. Create a MachineConfig YAML file, "kdump-master.yaml" with the following information that configures and enable kdump.

   
   apiVersion: machineconfiguration.openshift.io/v1
   kind: MachineConfig
   metadata:
     labels:
       machineconfiguration.openshift.io/role: "master"
     name: 00-printk-master
   spec:
     config:
       ignition:
         version: 3.2.0
       storage:
         files:
           - contents:
               source: data:text/plain;charset=utf-8;base64,a2VybmVsLnByaW50ayA9IDM=
             mode: 0644
             overwrite: true
             path: "/etc/sysctl.d/00-printk.conf"

3. Run the OC commands to enable the kdump.

   
   oc apply -f kdump-master.yaml
   oc apply -f kdump-worker.yaml