Welcome to the Linux Foundation Forum!

lab 5.2 : Operation cannot be fulfilled on persistentvolumeclaims "pvc-one"

Posts: 18
in LFD259 Class Forum

it's wierd. Using the resources for S_05. don't know that to do

I create a PV : kubectl create -f PVol.yaml ( I changed my for IP of my master node)
I create a PVC : kubectl create -f pvc.yaml
I create a deployment : kubectl create -f simpleapp.yaml-with-edits

but my pods are stuck at "Pending"

kubectl describe pod try1-dd4b9d99d-5n9gk

  1.   Warning  FailedScheduling  3m36s  default-scheduler  error while running "VolumeBinding" prebind plugin for pod "try1-dd4b9d99d-5n9gk": Operation cannot be fulfilled on persistentvolumeclaims "pvc-one": the object has been modified; please apply your changes to the latest version and try again
  2.   Warning  FailedScheduling  2m33s  default-scheduler  error while running "VolumeBinding" prebind plugin for pod "try1-dd4b9d99d-5n9gk": Failed to bind volumes: failed to check provisioning pvc: could not find v1.PersistentVolumeClaim "default/pvc-one"
  3.   Warning  FailedScheduling  2m33s  default-scheduler  persistentvolumeclaim "pvc-one" not found

kubectl describe pvc pvc-one

  1.   Normal   WaitForPodScheduled   7m40s                  persistentvolume-controller                                                                         waiting for pods try1-dd4b9d99d-xgt6p,try1-dd4b9d99d-hx5bm,try1-dd4b9d99d-8sxz6,try1-dd4b9d99d-vr4cn,try1-dd4b9d99d-5n9gk,try1-dd4b9d99d-pkxh6 to be scheduled
  2.   Normal   Provisioning          3m55s (x5 over 7m40s)  rancher.io/local-path_local-path-provisioner-55d9494bdd-ls947_571488d7-3cb7-4150-a976-0bd747496858  External provisioner is provisioning volume for claim "default/pvc-one"
  3.   Warning  ProvisioningFailed    3m55s (x5 over 7m40s)  rancher.io/local-path_local-path-provisioner-55d9494bdd-ls947_571488d7-3cb7-4150-a976-0bd747496858  failed to provision volume with StorageClass "local-path": Only support ReadWriteOnce access mode
  4.   Normal   ExternalProvisioning  107s (x25 over 7m40s)  persistentvolume-controller                                                                         waiting for a volume to be created, either by external provisioner "rancher.io/local-path" or manually created by system administrator

kubectl describe pv pvvol-1

  1. Source:
  2.     Type:      NFS (an NFS mount that lasts the lifetime of a pod)
  3.     Server:    192.168.50.8
  4.     Path:      /opt/sfw
  5.     ReadOnly:  false
  6. Events:        <none>

I installed nfs server on master and the nfs client on worker nodes too
from worker2

  1. k8s-worker2:~$ ls -l /mnt/
  2. total 4
  3. -rw-r--r-- 1 root root 9 Oct 25 23:47 hello.txt

k8s-master:~/labs/LFD259/SOLUTIONS/s_05$ sudo showmount -e localhost

  1. Export list for localhost:
  2. /opt/sfw *

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • Posts: 18

    hummm. I saw that I added local-path-storage before

    1.   - name: Deploy local-path-provisioner
    2.     become: false
    3.     command: kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/deploy/local-path-storage.yaml
    4.  
    5.   - name: Set local-path sc to default
    6.     become: false
    7.     command: 'kubectl patch storageclass local-path -p ''{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'''

    why does it interfers with the NFS in the example. Is it because we didn't specify a storage class. Probably, because of that, it's using the default, which in the local-path-provisioner. What should I modify to make it work (without uninstalling the local-path) ?

  • Posts: 2,451

    Hi @SebastienDionne,

    I see many rancher references in your output. Did you use rancher to build your cluster instead of the described method in Lab 2 ?

    Regards,
    -Chris

  • Posts: 18

    yes, I used my vagrant script. I saw later that I used rancher for host-path provider. so I think that I could fix my problem with creating a new nfs storageclass. I used those problems as practice for the exam in the same time :)

  • Posts: 18

    I was able to get it to work. I was right. I have to specify a storageClassName: nfs-client after installing nfs-client-provider. Now I can continue the exercices

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Quick Links

Categories

Upcoming Training