How To
Summary
This article includes how to increase the debug level for NooBaa resources.
Objective
In some instances, it may be necessary to set the debugging level higher on the NooBaa resources when capturing must-gather for BugZilla or Jira case interactions with engineering.
1. `default_level` - default debugging.
2. `warn` - warning/errors debugging only.
3. `nsfs` - additional `nsfs` detailed debugging.
4. `all` - all detailed debugging.
Environment
Steps
- When editing any resource, it's good practice to back up the resource before editing:
$ oc get cm -n openshift-storage noobaa-config -o yaml > noobaa-config.yaml
- Edit the
noobaa-configconfigmap and set theNOOBAA_LOG_LEVELtoall.
$ oc edit cm -n openshift-storage noobaa-config
apiVersion: v1
data:
DISABLE_DEV_RANDOM_SEED: "true"
NOOBAA_DISABLE_COMPRESSION: "false"
NOOBAA_LOG_LEVEL: default_level <------------------ change to "all"
kind: ConfigMap
<omitted-for-space>
-
This will cause a restart of all NooBaa pods. Wait for all pods to restart. Once pods are r
unningstatus, wait an additional 5 minutes. -
After 5 minutes have passed, begin collecting the ODF must-gather. Refer to the respective ODF version's Troubleshooting documentation for the ODF must-gather command.
-
After the must-gather(s) have been collected, revert the
NOOBAA_LOG_LEVELback todefault_level.
$ oc edit cm -n openshift-storage noobaa-config
apiVersion: v1
data:
DISABLE_DEV_RANDOM_SEED: "true"
NOOBAA_DISABLE_COMPRESSION: "false"
NOOBAA_LOG_LEVEL: all <-------- change back to to "default_level"
kind: ConfigMap
<omitted-for-space>
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
17 April 2025
UID
ibm17230933