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

Incompatibale example manifest files on master branch #137

Closed
leakingtapan opened this issue Dec 4, 2018 · 2 comments
Closed

Incompatibale example manifest files on master branch #137

leakingtapan opened this issue Dec 4, 2018 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@leakingtapan
Copy link
Contributor

leakingtapan commented Dec 4, 2018

/kind bug

What happened?
I deployed ./deploy/kubernetes/v1.12+ driver on my v1.12 cluster, csi-driver-registrar fails to start

Due to follow error:

Events:
  Type     Reason       Age                  From                                     Message
  ----     ------       ----                 ----                                     -------
  Normal   Scheduled    3m10s                default-scheduler                        Successfully assigned default/csi-node-zt2v2 to ip-172-20-127-156.ec2.internal
  Warning  FailedMount  67s                  kubelet, ip-172-20-127-156.ec2.internal  Unable to mount volumes for pod "csi-node-zt2v2_default(dbced501-f7f9-11e8-81f1-0a75e9a76798)": timeout expired waiting for
volumes to attach or mount for pod "default"/"csi-node-zt2v2". list of unmounted volumes=[registration-dir]. list of unattached volumes=[kubelet-dir plugin-dir registration-dir device-dir csi-node-sa-token-blrn
x]
  Warning  FailedMount  62s (x9 over 3m10s)  kubelet, ip-172-20-127-156.ec2.internal  MountVolume.SetUp failed for volume "registration-dir" : hostPath type check failed: /var/lib/kubelet/plugins_registry/ is not a directory

What you expected to happen?
v1.12 manifest should still work with v1.12 cluster

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 4, 2018
@leakingtapan
Copy link
Contributor Author

/cc @bertinatto

@leakingtapan
Copy link
Contributor Author

leakingtapan commented Dec 4, 2018

This is caused by backward incompatible changes made on CSI with regard to k/k v1.13 and our CSI 1.0 manifest files are update on v1.12 folder. So those manifests can not run on v1.12 cluster.

bertinatto pushed a commit to bertinatto/aws-ebs-csi-driver that referenced this issue Dec 12, 2018
Fixes: kubernetes-sigs#137

I use latest instead of v1.13 to highlight that is the latest version
under development which might have issues. And any other versioned
manifest files should not break.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants