Welcome to the new Linux Foundation Forum!

Lab-15.1 Pending status issue Installing MariaDb with Helm

arturogalanarturogalan Posts: 1
edited April 2018 in LFS258 Class Forum

Hi everybody! I followed the steps in lab-15.1 installing mariadb via Helm package manager.


helm --debug install stable/mariadb

 

Once done, the status of the pod is pending.


master $ kubectl get po

NAME READY
alliterating-starfish-mariadb-69f5c444d7-8g5g9 0/1

STATUS RESTARTS AGE

Pending 0 18m

 

 

Looking into the PVC that the pod makes, it has the following error:


master $ kubectl describe pvc alliterating-starfish-mariadb
Name: alliterating-starfish-mariadb
Namespace: default
StorageClass:
Status: Pending
Volume:
Labels: app=mariadb
chart=mariadb-3.0.3
heritage=Tiller
release=alliterating-starfish
Annotations: <none>
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal FailedBinding 4m (x63 over 19m) persistentvolume-controller no persistent
volumes available for this claim and no storage class is set

 

¿Any help on how to resolve this error?: no persistent volumes available for this claim and no storage class is set 

Thanks!

 

 

Comments

  • Hi, 

    When installing mariadb with Helm, did you use the command as provided above? 


    helm --debug install stable/mariadb

    or did you use the complete command as provided in the lab manual?


    helm --debug install stable/mariadb \ --set persistence.enabled=false

    Using the command from the lab did not produce any errors for me.

    Regards, 

    -Chris

  • serewiczserewicz Posts: 467

    Hello,

    You could also you your experience from earlier labs to create PVs for the chart, if you didn't want to set persistence.enabled=false. May be a good exercise to see how PVs work.

    Regards,

     

Sign In or Register to comment.