Vault pod not coming up about vault-helm

[amanchourasiya]

Same as this https://stackoverflow.com/questions/55044486/waitforfirstconsumer-persistentvolumeclaim-waiting-for-first-consumer-to-be-crea
But the solution given is not working

[jasonodonnell]

Hello,

Can you provide the output to the following commands:

kubectl get storageclass
kubectl describe storageclass
kubectl get pvc
kubectl describe pvc
kubectl get pv

[amanchourasiya]

[root@node1-dev]# k get storageclass
NAME PROVISIONER AGE
local-storage kubernetes.io/no-provisioner 23h

[root@node1-dev]# k describe sc local-storage
Name: local-storage
IsDefaultClass: No
Annotations:
Provisioner: kubernetes.io/no-provisioner
Parameters:
AllowVolumeExpansion:
MountOptions:
ReclaimPolicy: Delete
VolumeBindingMode: WaitForFirstConsumer
Events:

[root@node1-dev]# kubectl get pvc
data-vault10-0 Pending local-storage 2m13s

[root@node1-dev]# k describe pvc data-vault10-0
Name: data-vault10-0
Namespace: default
StorageClass: local-storage
Status: Pending
Volume:
Labels: app.kubernetes.io/instance=vault10
app.kubernetes.io/name=vault
component=server
helm.sh/chart=vault-0.2.1
Annotations:
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Mounted By: vault10-0
Events:
Type Reason Age From Message

---

Normal WaitForFirstConsumer 14s (x13 over 3m7s) persistentvolume-controller waiting for first consumer to be created before binding

[root@node1-dev]# k get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
local-pv 10Gi RWO Retain Available local-storage 6m24s

[amanchourasiya]

In values.yaml I made entered these values

affinity: |
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchLabels:
app.kubernetes.io/name: {{ template "vault.name" . }}
app.kubernetes.io/instance: "{{ .Release.Name }}"
component: server
topologyKey: kubernetes.io/node1

dataStorage:
enabled: true
# Size of the PVC created
size: 5Gi
# Name of the storage class to use. If null it will use the
# configured default Storage Class.
storageClass: local-storage
# Access Mode of the storage device being used for the PVC
accessMode: ReadWriteOnce

[amanchourasiya]

Is there any other value in values.yaml we need to modify?

[imorti]

I'm having the same problem. So happy to add values etc.

[imorti]

btw, if you change
dev: from false to true the pod comes up. All keys will be deleted upon restart but it's dev mode so...

[jasonodonnell]

Dev mode auto-initializes and unseals itself, so it will show a ready status. Standard and HA mode do not, they need to be initialized and unsealed before they become ready.

Dev mode also has no volume claims, so if there's a problem with storage, you won't see it in dev mode.

[jasonodonnell]

@amanchourasiya This issue seems to be related to the storage class being used and not Vault Helm itself. I haven't been able to track down what the issue with the storage class is because I cannot replicate it on my end. Can you provide more info about your environment? I'm not familiar with local-storage storage class. Where can this be found?