Skip to main content
Question

ifs-storage goes CrashLoopBackOff after upgrade run 24R1


Forum|alt.badge.img+5

Hi,

 

I am doing IFS cloud upgrade from 23R1 to 24R1.

KUBERNETES and ingress pods are up but ifs storage pods is not coming up.

ifs-storage   csi-smb-node-fvzgf                                     1/3     CrashLoopBackOff   34 (3m14s ago)   72m
ifs-storage   csi-smb-controller-6c679d7fbf-4zj92                    1/3     CrashLoopBackOff   34 (3m13s ago)   72m

2 replies

Forum|alt.badge.img+15
  • Superhero (Employee)
  • 182 replies
  • October 30, 2024

Hi Shashikant,

There is not enough information here to determine the cause. Please check the pod description and container logs for further details.

Describe commands:

1kubectl describe deployment/csi-smb-controller -n ifs-storage
2kubectl describe daemonset/csi-smb-node -n ifs-storage

Get the logs for each container. (Note: each pod contains three containers.):

1kubectl logs deployment/csi-smb-controller -c csi-provisioner -n ifs-storage
2kubectl logs deployment/csi-smb-controller -c smb -n ifs-storage
3kubectl logs deployment/csi-smb-controller -c liveness-probe -n ifs-storage
4kubectl logs daemonset/csi-smb-node -c smb -n ifs-storage
5kubectl logs daemonset/csi-smb-node -c node-driver-registrar -n ifs-storage
6kubectl logs daemonset/csi-smb-node -c liveness-probe -n ifs-storage

Depending on when the pods crash, you may also append -p to the above output to try to get the logs for the previously crashed pods.

Best regards -- Ben


Forum|alt.badge.img+5
  • Author
  • Sidekick (Partner)
  • 5 replies
  • November 18, 2024

Hi,

Issue has been resolved after run 

.\main.ps1 -resource 'CHANGE-POD-IP-RANGE'

 

Thanks

Sashikant


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings