Pv,PVC helm chart deployment using helm operator facing issue

[annu-mishraa]

Bug Report

What did you do?

I am trying to deploy pv ,pvc helm chart using helm operator but its nit creating all the persistent volume mentioned. Does it support or not ?

What did you expect to see?

I am expecting to create persistentvolumeclaim with the pv and pvc yaml configuration.

What did you see instead? Under which circumstances?

Environment

Operator type:

language helm

Kubernetes cluster type:

$ operator-sdk version

$ go version (if language is Go)

$ kubectl version

Possible Solution

Additional context

[varshaprasad96]

@annu-mishraa Could you please let us know if there are any errors in the logs. If possible could you also share your project so that we can replicate it. Helm operator should support creation of any K8s resources, if not we would need more information to know what's happening.

[annu-mishraa]

@varshaprasad96 We could see PV's - & PVC's getting deployed , but pvc's are stuck in pending state and also we see the same chart is getting correctly deployed via helm install and are not in pending state.

kubectl get persistentvolumeclaim -n odim
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
etcd-conf-pvc Pending manual 34s
etcd-data-pvc Pending manual 34s
kafka-conf-pvc Pending manual 34s
kafka-data-pvc Pending manual 34s
odimra-log-claim Pending manual 34s
redis-inmemory-data-claim Pending manual 34s
redis-ondisk-data-claim Pending manual 34s
zookeeper-conf-pvc Pending manual 34s
zookeeper-data-pvc Pending manual 34s

kubectl describe persistentvolumeclaim etcd-conf-pvc -n odim
Name: etcd-conf-pvc
Namespace: odim
StorageClass: manual
Status: Pending
Volume:
Labels: app.kubernetes.io/managed-by=Helm
Annotations: meta.helm.sh/release-name: volumeclame-sample
meta.helm.sh/release-namespace: odim
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Used By:
Events:
Type Reason Age From Message

---

Warning ProvisioningFailed (x3 over ) persistentvolume-controller storageclass.storage.k8s.io "manual" not found

[varshaprasad96]

@annu-mishraa It looks like the issue is not related to the helm, but instead relevant to how PVC is created. I could find a thread regarding the same here, according to which it states that "if the PVC cannot bind to the hostpath PV for ANY reason the error is a very generic and misleading one of storageclass.storage.k8s.io "manual" not found". You could see a detailed explanation on this error here, which if I'm not wrong is not because of helm but because the PV is not found. Could you try following the steps mentioned here and create a PV and PVC manually in your cluster to verify that everything works?

[annu-mishraa]

@varshaprasad96
PV and PVC both are created when deployed manually via helm install or using kubectl apply -f . Bothe are deployed without any issues.
1**.oc get pvc**
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
etcd-conf-pvc Bound etcd-conf-pv 100Mi RWO manual 9d
etcd-data-pvc Bound etcd-data-pv 100Mi RWO manual 9d
kafka-conf-pvc Bound kafka-conf-pv 100Mi RWO manual 9d
kafka-data-pvc Bound kafka-data-pv 100Mi RWO manual 9d
odimra-log-claim Bound odimra-log 100Mi RWO manual 9d
redis-inmemory-data-claim Bound redis-inmemory-data 8Gi RWO manual 9d
redis-ondisk-data-claim Bound redis-ondisk-data 8Gi RWO manual 9d
zookeeper-conf-pvc Bound zookeeper-conf-pv 100Mi RWO manual 9d
zookeeper-data-pvc Bound zookeeper-data-pv 100Mi RWO manual 9d
2. oc get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
etcd-conf-pv 100Mi RWO Retain Bound odim/etcd-conf-pvc manual 9d
etcd-data-pv 100Mi RWO Retain Bound odim/etcd-data-pvc manual 9d
kafka-conf-pv 100Mi RWO Retain Bound odim/kafka-conf-pvc manual 9d
kafka-data-pv 100Mi RWO Retain Bound odim/kafka-data-pvc manual 9d
odimra-log 100Mi RWO Retain Bound odim/odimra-log-claim manual 9d
redis-inmemory-data 8Gi RWO Retain Bound odim/redis-inmemory-data-claim manual 9d
redis-ondisk-data 8Gi RWO Retain Bound odim/redis-ondisk-data-claim manual 9d
zookeeper-conf-pv 100Mi RWO Retain Bound odim/zookeeper-conf-pvc manual 9d
zookeeper-data-pv 100Mi RWO Retain Bound odim/zookeeper-data-pvc manual 9d

But similar when deployed via helm operator PV's are getting created but Pvc's are getting stuck in pending. Could you please check once, it might be specific to helm operator.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.