Hi, I am trying to move an app that uses NFS file storage to Portworx. Challenge is in installing Helm charts that has yaml files built to use file storage. Though I modified yaml to use px storage class, PVCs, its failing to mount the volume using the PVC claim, during pod creation and results in crashloopback.
So when I checked the log while is pod is in crashloop, I see the below, can you help me with clear steps to identify the problem and resolve the issue please. This is critical to our app modernization journey.
Here is the output of oc describe pvc:
oc describe pvc ibm-sfg1-b2bi-resources
Name: ibm-sfg1-b2bi-resources
Namespace: b2bi
StorageClass: portworx-shared-sc
Status: Bound
Volume: pvc-0d462529-5719-4d98-b040-e35fbf05fc3d
Labels
component=resources
instance=ibm-sfg1
managed-by=Helm
name=b2bi
helm.sh/chart=ibm-b2bi-prod
release=ibm-sfg1
Annotations: helm.sh/hook: pre-install
helm.sh/hook-delete-policy: before-hook-creation
helm.sh/hook-weight: 1
/bind-completed: yes
/bound-by-controller: yes
storage-provisioner](): [portworx-volume]
Finalizers: [/pvc-protection]
Capacity: 1Gi
Access Modes: RWX
VolumeMode: Filesystem
Mounted By: ibm-sfg1-b2bi-db-setup-dxgbt
Events:
Type Reason Age From Message
Normal ProvisioningSucceeded 17m persistentvolume-controller Successfully provisioned volume pvc-0d462529-5719-4d98-b040-e35fbf05fc3d using [/portworx-volume]
Warning ProvisioningFailed 17m persistentvolume-controller Failed to provision volume with StorageClass “portworx-shared-sc”: Get “http://172.21.186.66:9001/v1/osd-volumes/versions”: dial tcp 172.21.186.66:9001: i/o timeout
% oc get svc -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubelet ClusterIP None 10250/TCP,10255/TCP,4194/TCP 154d
portworx-api ClusterIP 172.21.120.159 9001/TCP,9020/TCP,9021/TCP 153d
portworx-service NodePort 172.21.186.66 9001:32614/TCP,9019:32017/TCP,9020:30842/TCP,9021:30747/TCP 153d
stork-service ClusterIP 172.21.125.167 8099/TCP,443/TCP 153d