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

[all] Update k8s dependencies to v1.19.0 #1151

Merged

Conversation

seanschneeweiss
Copy link
Contributor

@seanschneeweiss seanschneeweiss commented Aug 6, 2020

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:

NONE

Sean Schneeweiss sean.schneeweiss@daimler.com, Daimler TSS GmbH, legal info/Impressum

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Aug 6, 2020
@k8s-ci-robot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 6, 2020
@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build succeeded.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@seanschneeweiss seanschneeweiss changed the title [occm] Update k8s dependencies to v1.19.0-rc.4 [all] Update k8s dependencies to v1.19.0-rc.4 Aug 6, 2020
@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build succeeded.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build failed.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build succeeded.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build succeeded.

@seanschneeweiss seanschneeweiss changed the title [all] Update k8s dependencies to v1.19.0-rc.4 [WIP] [all] Update k8s dependencies to v1.19.0-rc.4 Aug 6, 2020
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 6, 2020
@seanschneeweiss seanschneeweiss changed the title [WIP] [all] Update k8s dependencies to v1.19.0-rc.4 [WIP] [all] Update k8s dependencies to v1.19.0-rc.2 Aug 6, 2020
@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build succeeded.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Aug 6, 2020

Build succeeded.

@ramineni
Copy link
Contributor

ramineni commented Sep 8, 2020

/test cloud-provider-openstack-acceptance-test-csi-manila

@k8s-ci-robot
Copy link
Contributor

@ramineni: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

  • /test pull-cloud-provider-openstack-check
  • /test pull-cloud-provider-openstack-test

Use /test all to run all jobs.

In response to this:

/test cloud-provider-openstack-acceptance-test-csi-manila

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.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Sep 8, 2020

Build failed.

@lingxiankong
Copy link
Contributor

lingxiankong commented Sep 8, 2020

@gman0 @gouthampacha @tombarron Could you please help to look at the failure of the job cloud-provider-openstack-acceptance-test-csi-manila?

2020-09-08 07:44:38.188857 | ubuntu-bionic | + /home/zuul/src/k8s.io/kubernetes/cluster/kubectl.sh wait --for=condition=Ready pod/new-nfs-share-snap-restore-pod --timeout=300s
2020-09-08 07:49:39.110059 | ubuntu-bionic | error: timed out waiting for the condition on pods/new-nfs-share-snap-restore-pod

@gman0
Copy link
Member

gman0 commented Sep 8, 2020

@lingxiankong I'll have a look.

csi-snapshotter logs:

E0908 07:43:44.636902       1 snapshot_controller.go:370] createSnapshot [create-default/new-nfs-share-snap[81b4c0af-5cb3-40c8-8d9b-1952f4fc51a2]]: error occurred in createSnapshotOperation: selfLink was empty, can't make reference

The snapshot is never created. This in turn fails to create a PVC from this snapshot. pods/new-nfs-share-snap-restore-pod mounts this PVC, but can't.

@gman0
Copy link
Member

gman0 commented Sep 8, 2020

@ramineni and other csi-cinder folks: can you please confirm snapshotting works for you with k8s 1.19 and csi-snapshotter v1.2.2?

@jichenjc
Copy link
Contributor

jichenjc commented Sep 8, 2020

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
Copy link
Member

gman0 commented Sep 8, 2020

@jichenjc Ah, I missed #974. Both CSI Cinder and Manila were on csi-snapshotter v1.2.2 (or at least the csi-cinder's Helm chart still is). And CI job for csi-manila tests snapshotting as well.

@jichenjc
Copy link
Contributor

jichenjc commented Sep 8, 2020

@jichenjc Ah, I missed #974. Both CSI Cinder and Manila were on csi-snapshotter v1.2.2 (or at least the csi-cinder's Helm chart still is). And CI job for csi-manila tests snapshotting as well.

should I do additional test? I don't have manila env on my hand ..

@ramineni
Copy link
Contributor

ramineni commented Sep 9, 2020

@ramineni and other csi-cinder folks: can you please confirm snapshotting works for you with k8s 1.19 and csi-snapshotter v1.2.2?

@gman0 cinder is updated to 2.1.1 for 1.19 .
Any update on the manila failure? This is blocking cpo release.
/cc @gouthampacha @tombarron

@gman0
Copy link
Member

gman0 commented Sep 9, 2020

@ramineni OpenLab's install-k8s role uses k8s master:

2020-09-08 06:54:30.295331 | TASK [install-k8s : Install etcd v3.4.13 and kubernetes 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:

E0909 15:43:35.798659       1 event.go:247] Could not construct reference to: '&v1alpha1.VolumeSnapshot{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"new-nfs-share-snap", GenerateName:"", Namespace:"default", SelfLink:"", UID:"c06ae5a9-7a84-441a-8fe2-b2b3eea805b0", ResourceVersion:"470", Generation:2, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63735262998, loc:(*time.Location)(0x238f460)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Initializers:(*v1.Initializers)(nil), Finalizers:[]string{"snapshot.storage.kubernetes.io/volumesnapshot-protection"}, ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry{v1.ManagedFieldsEntry{Manager:"kubectl", Operation:"Update", APIVersion:"snapshot.storage.k8s.io/v1alpha1", Time:(*v1.Time)(0xc000319bc0), Fields:(*v1.Fields)(nil)}, v1.ManagedFieldsEntry{Manager:"csi-snapshotter", Operation:"Update", APIVersion:"snapshot.storage.k8s.io/v1alpha1", Time:(*v1.Time)(0xc000319c20), Fields:(*v1.Fields)(nil)}}}, Spec:v1alpha1.VolumeSnapshotSpec{Source:(*v1.TypedLocalObjectReference)(0xc0002f16e0), SnapshotContentName:"", VolumeSnapshotClassName:(*string)(0xc000698610)}, Status:v1alpha1.VolumeSnapshotStatus{CreationTime:(*v1.Time)(0xc000319c40), RestoreSize:(*resource.Quantity)(0xc000649dc0), ReadyToUse:false, Error:(*v1beta1.VolumeError)(0xc0002f1710)}}' due to: 'selfLink was empty, can't make reference'. Will not report event: 'Warning' 'SnapshotCreationFailed' 'Failed to create snapshot: selfLink was empty, can't make reference'
E0909 15:43:35.798716       1 snapshot_controller.go:370] createSnapshot [create-default/new-nfs-share-snap[c06ae5a9-7a84-441a-8fe2-b2b3eea805b0]]: error occurred in createSnapshotOperation: selfLink was empty, can't make reference

...which is the same error as we're getting from the CI. I suspect this might be a bug in the latest Kubernetes.

@gman0
Copy link
Member

gman0 commented Sep 9, 2020

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).

@tombarron
Copy link
Contributor

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.

@lingxiankong
Copy link
Contributor

/test cloud-provider-openstack-acceptance-test-csi-manila

@k8s-ci-robot
Copy link
Contributor

@lingxiankong: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

  • /test pull-cloud-provider-openstack-check
  • /test pull-cloud-provider-openstack-test

Use /test all to run all jobs.

In response to this:

/test cloud-provider-openstack-acceptance-test-csi-manila

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.

@theopenlab-ci
Copy link

theopenlab-ci bot commented Sep 10, 2020

Build succeeded.

@jichenjc
Copy link
Contributor

/approve
I think we are ready to merge this now

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 10, 2020
@k8s-ci-robot k8s-ci-robot merged commit cbee1e1 into kubernetes:master Sep 10, 2020
@lingxiankong
Copy link
Contributor

@jichenjc @ramineni @wangxiyuan @gman0 thanks for your help!

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Sep 10, 2020
powellchristoph pushed a commit to powellchristoph/cloud-provider-openstack that referenced this pull request Jan 19, 2022
* [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 <sean.schneeweiss@daimler.com>

* [occm] use version v1.19.0, do not use InstancesV2

InstancesV2 requires further testing before being used.

Signed-off-by: Sean Schneeweiss <sean.schneeweiss@daimler.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants