-
Notifications
You must be signed in to change notification settings - Fork 619
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
[all] Update k8s dependencies to v1.19.0 #1151
[all] Update k8s dependencies to v1.19.0 #1151
Conversation
Hi @seanschneeweiss. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Build failed.
|
Build failed.
|
Build succeeded.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build succeeded.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build failed.
|
Build succeeded.
|
Build succeeded.
|
c5151d9
to
7440729
Compare
Build succeeded.
|
Build succeeded.
|
/test cloud-provider-openstack-acceptance-test-csi-manila |
@ramineni: The specified target(s) for
Use 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. |
Build failed.
|
@gman0 @gouthampacha @tombarron Could you please help to look at the failure of the job cloud-provider-openstack-acceptance-test-csi-manila?
|
@lingxiankong I'll have a look.
The snapshot is never created. This in turn fails to create a PVC from this snapshot. |
@ramineni and other csi-cinder folks: can you please confirm snapshotting works for you with k8s 1.19 and csi-snapshotter v1.2.2? |
I tested locally #974 before the code merge (volume create ==> snapshot create ) , it is not v1.19 exactly but it's with master branch , of course not with very thorough test due to no CI why cinder CSI snapshot is related to manila ? |
@gman0 cinder is updated to 2.1.1 for 1.19 . |
@ramineni OpenLab's install-k8s role uses k8s master:
I've just checked out k8s with branch v1.19.0 and csi-snapshotter v1.2.2 works. Then I tried with k8s master:
...which is the same error as we're getting from the CI. I suspect this might be a bug in the latest Kubernetes. |
To not block this PR any further, I'll disable all snapshot-related tests in csi-manila's CI job until it's resolved (or we move to csi-snapshotter v2 - whichever comes first). |
Thankis for this out, @gman0. I had a long weekend (holiday combined with a couple days vacation) and was just looking at this issue now and was not sure what was going on. |
/test cloud-provider-openstack-acceptance-test-csi-manila |
@lingxiankong: The specified target(s) for
Use 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. |
Build succeeded.
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@jichenjc @ramineni @wangxiyuan @gman0 thanks for your help! |
* [occm] update cloud-provider to 1.19.0 This commit updates k8s version to 1.19.0 to use the cloud-provider pkg from its new location. Signed-off-by: Sean Schneeweiss <[email protected]> * [occm] use version v1.19.0, do not use InstancesV2 InstancesV2 requires further testing before being used. Signed-off-by: Sean Schneeweiss <[email protected]>
What this PR does / why we need it:
The current v1.18.0 service controller for OCCM is missing two important fixes:
Also the cloud-provider controllers were moved to k8s.io/cloud-provider/controllers.
Therefore, an update/vendoring is suggested to version v1.19.0.
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:
Release note:
Sean Schneeweiss [email protected], Daimler TSS GmbH, legal info/Impressum