Troubleshooting issue for bootstrapper pod
When inside the NetBackup fluentbit collector, you may see multiple bootstrapper log folders. This is expected behavior because Kubernetes jobs add unique IDs to the pod's name every time the pod is rescheduled or redeployed.
To ensure that you are looking at the most recent bootstrapper logs, check the date when the bootstrapper log folder was created by running the following command:
ls -lt
To initialize the bootstrapper pod to run again after addressing the failure, execute the following steps:
Execute the following command:
$ kubectl get jobs -n <netbackup namespace> NAME
Output is:
COMPLETIONS DURATION AGE job.batch/<netbackup namespace>-bootstrapper 0/1 61m 61m
Extract the name provided by the kubectl command in step 1 and run:
$ kubectl delete job.batch/<netbackup namespace>-bootstrapper -n <netbackup namespace>
After the command completes successfully, the bootstrapper pod getting executed in the environment.
$ kubectl get pods -n <netbackup namespace> bash-4.4$ kubectl get pods -n netbackup NAME READY STATUS RESTARTS AGE <netbackup namespace>-bootstrapper-qf5xt 0/2 Running 0 4m47s <netbackup namespace>-nbatd-0 1/4 Running 0 4m37s <netbackup namespace>-nbmqbroker-0 0/2 Init:0/2 0 4m31s <netbackup namespace>-nbwsapp-0 0/4 Init:0/2 0 4m26s <netbackup namespace>-policyjob-0 0/5 Init:0/1 0 4m26s <netbackup namespace>-policyjobmgr-0 0/5 Init:0/1 0 4m26s <netbackup namespace>-primary-0 0/2 Init:0/1 0 4m26s <netbackup namespace>-requestrouter-6db64979c8-r49jm 0/1 Init:0/1 0 2m26s nb-fluentbit-collector-587d75547-8n4qj 2/2 Running 0 6m22s nb-fluentbit-daemonset-j59k8 1/1 Running 0 3m47s nb-fluentbit-daemonset-plxvk 1/1 Running 0 6m22s nb-postgresql-0 1/1 Running 0 6m17s