Troubleshooting command device update issues

1. Delete the PVC. Enter:

   kubectl delete pvc pvc-sdb -n ucp

   If the status is in the Terminating state and you are unable to proceed, in a separate SSH session, enter:
   

   

   
   

   kubectl patch pvc pvc-sdb -n ucp -p '{"metadata":{"finalizers":[]}}' --type=merge

2. Delete the PV. Enter:

   kubectl delete pv pv-sdb

   If you are unable to proceed, enter:

   kubectl patch pv pv-sdb -n ucp -p '{"metadata":{"finalizers":[]}}' --type=merge

1. Tear down the running sdi-gateway-block PODs. Enter:

   kubectl patch deployment sdi-gateway-block -n ucp --type "merge" -p '{"spec":{"replicas":0}}'

2. Verify that the tear down for the sdi-gateway-block POD is successful. Enter:

   kubectl get pods -n ucp | grep sdi

   Continue to run the above command until only the following blocks are displayed:

   • sdi-gateway-compute-XYZ
   • sdi-gateway-network-XYZ

   Note: It takes approximately 90 seconds for a tear down.
3. Retrieve the current running image. Enter:

   kubectl get deployment sdi-gateway-block -n ucp -o yaml | grep "image:"

   Note the output image name for use in the following step. For example: triangulum-docker-dev-sc.repo.sc.eng.hitachivantara.com/sdi-gateway-block:v9.1.0.dev-4662
4. Replace the docker image with the image name output above to remove the command device.

   For example, enter:

   kubectl patch deployment sdi-gateway-block -n ucp --type "merge" -p '{"spec":{"template":{"spec":{"containers":[{"name":"sdi-gateway-block", "image":"10.96.3.49/sdi-gateway-block:v9.3.0.dev-5226", "volumeMounts":[{"name":"log-dir", "mountPath":"/var/log/sdi-gateway","subPath":"sdi-gateway-block"}]}], "volumes":[{"name":"log-dir", "persistentVolumeClaim":{"claimName":"pvc-logs"}}]}}}}'

kubectl patch deployment sdi-gateway-block -n ucp --type "merge" -p '{"spec":{"replicas":1}}'