Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug or question] Cannot install in kind because of the PVC #17

Closed
gaocegege opened this issue May 19, 2021 · 3 comments
Closed

[bug or question] Cannot install in kind because of the PVC #17

gaocegege opened this issue May 19, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@gaocegege
Copy link

gaocegege commented May 19, 2021

/kind bug

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

kind create cluster
export KUBECONFIG=~/.kube/config
curl -SsL https://github.com/koderover/zadig/releases/latest/download/install.sh | bash
kubectl -n zadig describe pvc
Name:          zadig-nfs-server
Namespace:     zadig
StorageClass:  standard
Status:        Pending
Volume:
Labels:        app.kubernetes.io/instance=zadig-nfs-server
               app.kubernetes.io/managed-by=Helm
               app.kubernetes.io/name=nfs-server
               helm.sh/chart=nfs-server-0.9.5
Annotations:   volume.beta.kubernetes.io/storage-provisioner: rancher.io/local-path
               volume.kubernetes.io/selected-node: kind-control-plane
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       zadig-nfs-server-858477dfb7-fpdx2
Events:
  Type     Reason                Age                     From                                                                                                Message
  ----     ------                ----                    ----                                                                                                -------
  Normal   ExternalProvisioning  4m29s (x523 over 134m)  persistentvolume-controller                                                                         waiting for a volume to be created, either by external provisioner "rancher.io/local-path" or manually created by system administrator
  Normal   Provisioning          2m56s (x14 over 134m)   rancher.io/local-path_local-path-provisioner-78776bfc44-9cz45_91e5ec11-ec4b-45b9-9057-38f5c580f26b  External provisioner is provisioning volume for claim "zadig/zadig-nfs-server"
  Warning  ProvisioningFailed    2m56s (x14 over 134m)   rancher.io/local-path_local-path-provisioner-78776bfc44-9cz45_91e5ec11-ec4b-45b9-9057-38f5c580f26b  failed to provision volume with StorageClass "standard": Only support ReadWriteOnce access mode

What did you expect to happen:

The system is deployed successfully.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@gaocegege
Copy link
Author

failed to provision volume with StorageClass "standard": Only support ReadWriteOnce access mode

Maybe related to rancher/local-path-provisioner#70

@jamsman94 jamsman94 self-assigned this May 19, 2021
@jamsman94 jamsman94 added the bug Something isn't working label May 19, 2021
@jamsman94
Copy link
Contributor

jamsman94 commented May 19, 2021

We confirmed that several storage class is not capable of creating PV with ReadWriteMany access mode. Currently, We changed the access mode of all the pv from ReadWriteMany to ReadWriteOnce. This issue should be fixed.

@jamsman94
Copy link
Contributor

This problem is now resolved with the 1.0.0-rc.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants