Description of problem (please be detailed as possible and provide log
snippests):

After resizing the OSD in the GCP 4.16 platform, the OSDs failed to restart automatically, and the OSD, PVC, and PV sizes did not increase.

Version of all relevant components (if applicable):
GCP platform, OCP/ODF 4.16.

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, we can't increase the OSD size when using GCP.

Is there any workaround available to the best of your knowledge?
Restarting the OSD manually may solve this issue, but I am unsure.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes.

Can this issue reproduce from the UI?
No.

If this is a regression, please provide more details to justify this:
No.

Steps to Reproduce:
1. Resize the OSD with the command: 
oc -n openshift-storage patch storagecluster ocs-storagecluster -n openshift-storage -p '[{ "op": "replace", "path": "/spec/storageDeviceSets/0/dataPVCTemplate/spec/resources/requests/storage", "value": <size_to_increase>}]' --type json
2. Wait for the OSD pods to restart and the new size to be reflected on the OSDs, PVCs, and PVs.


Actual results:
The OSD pods failed to restart, and the OSD, PVC, and PV sizes did not increase.

Expected results:
The OSD pods should restart, and the new size should be reflected on the OSDs, PVCs, and PVs.


Additional info:

Logs: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-007gi1c33-t1/j-007gi1c33-t1_20241013T053541/logs/failed_testcase_ocs_logs_1728817074/test_resize_osd_ocs_logs/j-007gi1c33-t1/