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

PODAUTO-99: Fix VPA e2e test failures #286

Merged

Conversation

jkyros
Copy link

@jkyros jkyros commented Feb 15, 2024

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


We run the upstream tests downstream against the VPA operator repo, and
they are failing after the rebase, which is blocking our VPA operator
release chores.

Upstream has already fixed this in the weeks between our rebase and now,
so we just need to bring the fixes back so our tests pass and we can merge
 code again.

* Add recommendation for single container only if no other recommendations are given

* Add custom recommender name back to test

* go mod vendor for e2e tests
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 15, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 15, 2024

@jkyros: This pull request references PODAUTO-99 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from nrb and racheljpg February 15, 2024 00:45
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 15, 2024

@jkyros: This pull request references PODAUTO-99 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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 openshift-eng/jira-lifecycle-plugin repository.

@jkyros
Copy link
Author

jkyros commented Feb 15, 2024

/test e2e-hypershift

@joelsmith
Copy link

/lgtm
/retest

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2024
@joelsmith
Copy link

/label acknowledge-critical-fixes-only
/approve

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 20, 2024
Copy link

openshift-ci bot commented Feb 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelsmith

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 20, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD cb4f7f2 and 2 for PR HEAD 3bb1ea7 in total

@joelsmith
Copy link

/retest

@jkyros
Copy link
Author

jkyros commented Feb 20, 2024

e2e-hypershift is failing because a capi provider container is crashing. I don't know why yet, but it's not related to this PR, it's happening in #287 also (and all that's PR is doing is updating a .snyk file):

util.go:484: Container manager in pod capi-provider-5f658fc869-8pmlk has a restartCount > 0 (1)

@jkyros
Copy link
Author

jkyros commented Feb 21, 2024

Global history seems to think this is a flake and it does sometimes pass, I'm going to try one more time and see if I can get more favorable timings.

It looks like context deadline exceeded on the leaderelection lease, causing the pod to think it lost the election and restart:

E0220 15:51:36.261880       1 leaderelection.go:327] error retrieving resource lock e2e-clusters-6vd97-example-jvz6f/controller-leader-elect-capa: Get "https://172.29.0.1:443/apis/coordination.k8s.io/v1/namespaces/e2e-clusters-6vd97-example-jvz6f/leases/controller-leader-elect-capa": context deadline exceeded
I0220 15:51:36.261907       1 leaderelection.go:280] failed to renew lease e2e-clusters-6vd97-example-jvz6f/controller-leader-elect-capa: timed out waiting for the condition
E0220 15:51:36.261952       1 logger.go:94] "setup: problem running manager" err="leader election lost"
I0220 15:51:36.261978       1 recorder.go:104] "events: capi-provider-5f658fc869-8pmlk_cebbd79a-caa2-48b1-aeb2-bbe759f63ab5 stopped leading" type="Normal" object={"kind":"Lease","namespace":"e2e-clusters-6vd97-example-jvz6f","name":"controller-leader-elect-capa","uid":"b1d56836-3f63-4c82-8723-8ab9fce94359","apiVersion":"coordination.k8s.io/v1","resourceVersion":"19855"} reason="LeaderElection"

/retest

@joelsmith
Copy link

/retest

Copy link

openshift-ci bot commented Feb 21, 2024

@jkyros: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit d832711 into openshift:master Feb 21, 2024
12 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-vertical-pod-autoscaler-container-v4.16.0-202402210509.p0.gd832711.assembly.stream.el9 for distgit vertical-pod-autoscaler.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants