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

[WIP] [release-4.6] Rebase onto v1.19.12 #850

Closed
wants to merge 455 commits into from

Conversation

damemi
Copy link

@damemi damemi commented Jul 8, 2021

Commits sheet: https://docs.google.com/spreadsheets/d/154TrUMoS-xiKjw7sgyMA6upb9WDxaaTu6TEWostnh3U/edit?usp=sharing

I am having trouble with the generated/openshift files. Following the steps in the rebase doc, files like hyperkube/Dockerfile.rhel don't exist. So I am unable to carry commits that have that file or edit it. Still trying to figure it out

Anago GCB and others added 30 commits February 17, 2021 13:32
Given we're pulling the relnotes team into review, the changes to
reviewers will happen a little more frequently, which means we'll have
the same issue of needing a top-level approver to do updates that we
were trying to avoid by creating the subdirectory in the first place.

Signed-off-by: Stephen Augustus <foo@auggie.dev>
(cherry picked from commit 5639cd9)
Dan and Sascha are senior Release Managers, SIG Release leadership, and
have already been giving thoughtful reviews of the content in this
directory.

Adding them as reviewers to spread the load of SIG Release eyes on
content.

Signed-off-by: Stephen Augustus <foo@auggie.dev>
(cherry picked from commit 1a43c65)
Creates a few agnhost related functions that creates agnhost
pods / containers for general purposes.

The following commits will refactor tests to use those functions.
Make pre provisioned snapshots using CSI driver by
1. Take a dynamic snapshot with retain policy
2. Delete the dynamic snapshot and content
3. Create a preprovisioned snapshot with snapshotHandle

This commit adds a preprovisiond test pattern, all snapshots made using
create snapshot resource become prepv snapshots. All exisitng test cases
now run again with prepv snapshots.
Prepv snapshots only need to specify driver.
A previous commit created a few agnhost related functions that creates agnhost
pods / containers for general purposes.

Refactors tests to use those functions.
This fixes a problem when using the framework helper
e2epod.CreateExecPodOrFail() more than once in the same test.

The problem is that this function was creating pods with both the
pod.Name and pod.GenerateName set.
The second pod failed to be created with a 500 with Reason ServerTimeout
indicating a unique name could not be found in the time allotted,
xref https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/
e2e tests should log stdout / stderr of failed commands executed via
PodExec. "command terminated with exit code 1" is not really useful.
Add a separate in-tree gcepd driver for windows cluster because it does
not support certain features as Linux driver.

Change-Id: I2fca86b3f32f17db7703c46a36944d9ee51f355f
Update snapshottable and disable disruptive test for Windows

Change-Id: I9d6beb25078c1941e405bf61545caae30326ddd1
Update storage test suits to enable some tests on Windows

Change-Id: I1f596bb9f7a0f41ae398aec43406ee5c753cdce3
Update storage topology tests setup for Windows

Change-Id: I9a2773b91806a10553db06f61f7259db4df71c3b
sttts and others added 16 commits July 7, 2021 13:53
…d provider

OpenStack cloud provider must not use nil when provisioning a Cinder
volume.
Instead of allowing the cloud provider to guess at the zones that
should be applied for a cluster under test, allow the explicit list
of zones to consider to be passed as a new test context flag -gce-zones.

Only the GCE test cloud provider recognizes this value because only
the GCE test cloud provider makes assumptions about zones for verifying
values, and the default assumptions for GKE do not always match non-GKE
providers.
A number of e2e tests are useful to run after the system has been
disrupted or is in the progress of being disrupted, but the current
suite and test logic blocks progress waiting for all nodes to be
healthy.

By passing -1 to --minStartupPods or --allowed-not-ready-nodes flags
the caller can bypass wait logic before and after test suites that
would prevent running e2e during disruption. This allows use of parts
of the e2e suite during cluster duress to verify that controllers or
components still function.
Set informer for the openstack cloud provider to ensure it is properly
initialized when reading config from a secret.

Upstream 89885 was closed in favor of 96750.

Co-authored-by: Hemant Kumar <hekumar@redhat.com>
There is a race when the server is coming up and the subsequent dial on
the socket. Fix the race with a PollImmediate retry.
…ingTermination

Ensures the pod to be pending termination or be killed, after
(*podKillerWithChannel).KillPod has been returned, by limiting
one request per pod in (*podKillerWithChannel).KillPod.
@openshift-ci
Copy link

openshift-ci bot commented Jul 8, 2021

@damemi: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[WIP] [release-4.6] Rebase onto v1.19.12

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.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 8, 2021
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jul 8, 2021
@openshift-ci-robot
Copy link

@damemi: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

@openshift-ci openshift-ci bot requested review from deads2k and sjenning July 8, 2021 15:32
@openshift-ci
Copy link

openshift-ci bot commented Jul 8, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: damemi
To complete the pull request process, please assign mfojtik after the PR has been reviewed.
You can assign the PR to them by writing /assign @mfojtik in a comment when ready.

The full list of commands accepted by this bot can be found 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

@openshift-ci
Copy link

openshift-ci bot commented Jul 8, 2021

@damemi: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/verify 4414ff5 link /test verify
ci/prow/integration 4414ff5 link /test integration
ci/prow/unit 4414ff5 link /test unit
ci/prow/verify-commits 4414ff5 link /test verify-commits
ci/prow/k8s-e2e-gcp-serial 4414ff5 link /test k8s-e2e-gcp-serial
ci/prow/e2e-aws-ovn 4414ff5 link /test e2e-aws-ovn
ci/prow/k8s-e2e-conformance-aws 4414ff5 link /test k8s-e2e-conformance-aws
ci/prow/e2e-gcp 4414ff5 link /test e2e-gcp
ci/prow/e2e-aws 4414ff5 link /test e2e-aws
ci/prow/e2e-agnostic-cmd 4414ff5 link /test e2e-agnostic-cmd
ci/prow/e2e-aws-csi 4414ff5 link /test e2e-aws-csi
ci/prow/e2e-aws-jenkins 4414ff5 link /test e2e-aws-jenkins
ci/prow/e2e-agnostic-upgrade 4414ff5 link /test e2e-agnostic-upgrade
ci/prow/k8s-e2e-gcp 4414ff5 link /test k8s-e2e-gcp
ci/prow/e2e-aws-serial 4414ff5 link /test e2e-aws-serial
ci/prow/images 4414ff5 link /test images
ci/prow/e2e-azure 4414ff5 link /test e2e-azure

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@damemi
Copy link
Author

damemi commented Jul 8, 2021

It looks like I missed something because make update is failing with:

# k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/server
vendor/k8s.io/apiserver/pkg/server/config.go:721:55: c.IsTerminating undefined (type *Config has no field or method IsTerminating)
# k8s.io/kubernetes/vendor/k8s.io/legacy-cloud-providers/openstack
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:300:66: cannot refer to unexported name os.secretName
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:300:81: cannot refer to unexported name os.secretNamespace
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:310:20: undefined: newProvider
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:314:3: cannot refer to unexported name os.provider
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:315:3: cannot refer to unexported name os.region
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:329:7: os.secretName undefined (type *OpenStack has no field or method secretName)
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:329:30: os.secretNamespace undefined (type *OpenStack has no field or method secretNamespace)
vendor/k8s.io/legacy-cloud-providers/openstack/openstack.go:330:12: os.setConfigFromSecret undefined (type *OpenStack has no field or method setConfigFromSecret)

Which must be from one of the openstack picks

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 11, 2021
@openshift-ci
Copy link

openshift-ci bot commented Jul 11, 2021

@damemi: PR needs rebase.

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.

@damemi
Copy link
Author

damemi commented Sep 14, 2021

/close

@openshift-ci openshift-ci bot closed this Sep 14, 2021
@openshift-ci
Copy link

openshift-ci bot commented Sep 14, 2021

@damemi: Closed this PR.

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet