-
Notifications
You must be signed in to change notification settings - Fork 597
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
cinder-csi-plugin@v1.23.3
fails with "x509: certificate signed by unknown authority"
#1948
Comments
/sig storage |
I also found related issue #1938 do you might I create a new rc release and you give a try first before we upgrade to 1.23.4 ? @ialidzhikov ? |
Sounds good. Sure, I will test the new rc on our side and provide feedback whether it fixes the issue or not. |
@ialidzhikov please try 1.23.4-rc1 and see whether it can fix your problem .. didn't do anything other than just do the release procedure again... at least previous issue on #1938 seems ok now on my local env |
I can confirm that |
I can also confirm that 1.23.4-rc1 works as expected and that the issue is not reproducible with it. |
https://github.com/kubernetes/cloud-provider-openstack/releases/tag/v1.23.4 is created and root@jjtest1:~/go/src/github.com/cloud-provider-openstack# docker run -it k8scloudprovider/cinder-csi-plugin:v1.23.4 which blkid |
/close |
@ialidzhikov: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
I am trying to update out cinder-csi-plugin version from v1.23.0 to v1.23.3 (for K8s 1.23 clusters). We are running
docker.io/k8scloudprovider/cinder-csi-plugin@v1.23.0
without issues more than a year.When I tried v1.23.3, it fails with:
I checked the diff between v1.23.0..v1.23.3, but I cannot spot a change that would cause such failure. I don't have any change to the configuration - the same v1.23.0 configuration is used.
The more interesting thing is that I don't face such issue when I build v1.23.3 cinder-csi-plugin image from source.
An example image that works without issues -
innoweek/cinder-csi-plugin-amd64:v1.23.3
.I assume there is something wrong with
docker.io/k8scloudprovider/cinder-csi-plugin:v1.23.3
. Can it be the case the binary in this image does not correspond to the v1.23.3 tag? Otherwise I cannot explain why it works for my custom built image and does not work for the upstream one.What you expected to happen:
docker.io/k8scloudprovider/cinder-csi-plugin:v1.23.3
to work without issues ("x509: certificate signed by unknown authority").How to reproduce it:
See above.
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: