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

Bug 1986003: Rebase to Kubernetes 1.22 #262

Conversation

coreydaley
Copy link
Member

No description provided.

@coreydaley
Copy link
Member Author

/test all

@coreydaley
Copy link
Member Author

/test e2e-aws

@coreydaley coreydaley force-pushed the jira_build_297_rebase_to_k8s_1_22 branch 2 times, most recently from 4029f7c to 2b42346 Compare August 18, 2021 15:15
@coreydaley coreydaley force-pushed the jira_build_297_rebase_to_k8s_1_22 branch from 2b42346 to 2b8cafd Compare August 18, 2021 16:10
@coreydaley coreydaley force-pushed the jira_build_297_rebase_to_k8s_1_22 branch from bb51429 to af83e25 Compare August 18, 2021 16:26
@coreydaley
Copy link
Member Author

/retest
infrastructure issue

 level=info msg=Creating infrastructure resources...
level=error
level=error msg=Error: Error retrieving Target Group Attributes: TargetGroupNotFound: Target groups 'arn:aws:elasticloadbalancing:us-east-1:460538899914:targetgroup/ci-op-hnblpriv-f242d-6lbct-aext/e60484d43df1dee3' not found
level=error msg=	status code: 400, request id: 009de565-1fd9-4bd4-a38f-900cef790770
level=error
level=error msg=  on ../tmp/openshift-install-cluster-034962729/vpc/master-elb.tf line 71, in resource "aws_lb_target_group" "api_external":
level=error msg=  71: resource "aws_lb_target_group" "api_external" {
level=error
level=error
level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change 

@coreydaley
Copy link
Member Author

/retest
unrelated test failure/flake

@coreydaley
Copy link
Member Author

/retest
infrastructure issues

level=error
level=error msg=Error: Error retrieving Target Group Attributes: TargetGroupNotFound: Target groups 'arn:aws:elasticloadbalancing:us-east-1:460538899914:targetgroup/ci-op-hnblpriv-f242d-6lbct-aext/e60484d43df1dee3' not found
level=error msg=	status code: 400, request id: 009de565-1fd9-4bd4-a38f-900cef790770
level=error
level=error msg=  on ../tmp/openshift-install-cluster-034962729/vpc/master-elb.tf line 71, in resource "aws_lb_target_group" "api_external":
level=error msg=  71: resource "aws_lb_target_group" "api_external" {
level=error
level=error
level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change 

@coreydaley
Copy link
Member Author

/retest

2 similar comments
@coreydaley
Copy link
Member Author

/retest

@coreydaley
Copy link
Member Author

/retest

@coreydaley
Copy link
Member Author

/assign @adambkaplan @gabemontero

@coreydaley
Copy link
Member Author

/retest

@gabemontero
Copy link
Contributor

gabemontero commented Aug 19, 2021

well the most recent e2e-aws-image-ecosystem failure turned up an issue with the recent fix to shorten the connection timeout ... broke the retry mechanism

that fix merged 9 days ago, so it must not be frequent (I saw evidence of networking pain in various logs) but I'll be opening a new BZ for this in a few minutes and have a PR up shortly after

the cgroupsv2 e2e needs my BUILD-278 PR in this repo ... that optional job should be skipped

but I won't issue the skip yet so we can

/test e2e-aws-image-ecosystem

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2021
@gabemontero
Copy link
Contributor

openshift/cluster-samples-operator#386 up for fixing retry on tbr check

@gabemontero
Copy link
Contributor

the image eco suite failed, but if you look at the results, the actual tests passed, but an error occurred during must gather

/test e2e-aws-image-ecosystem

@gabemontero
Copy link
Contributor

/test e2e-aws-image-ecosystem

@coreydaley
Copy link
Member Author

/retest

@gabemontero
Copy link
Contributor

gabemontero commented Aug 19, 2021

yeah that cgroupv2 won't pass until BUILD-278 merges @coreydaley

I just wanted to see a clean image eco (that latest failures have been non samples flakes) before officially invoking a skip to clear out the cgroupv2 e2e

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2021

@coreydaley: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-cgroupsv2 af83e25 link /test e2e-aws-cgroupsv2

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.

@gabemontero
Copy link
Contributor

gabemontero commented Aug 19, 2021

ok we have a green image eco

going to

/skip

to clear out the cgroupv2 test .... it will be covered by BUILD-278 which should cover cgroupv2 and k8s v1.22 after this PR merges.

@coreydaley
Copy link
Member Author

Thanks @gabemontero
Looks like i still need an approval from @adambkaplan

Copy link
Contributor

@adambkaplan adambkaplan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@adambkaplan
Copy link
Contributor

/label docs-approved

No documentation required for this

@openshift-ci openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Aug 19, 2021
@adambkaplan
Copy link
Contributor

/label px-approved

No PX materials required for this

@adambkaplan
Copy link
Contributor

/assign @jitendar-singh

I think the CI test for this PR is sufficient. If you agree you can label this "qe-approved" and this can merge.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan, coreydaley, gabemontero

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. px-approved Signifies that Product Support has signed off on this PR labels Aug 19, 2021
@coreydaley
Copy link
Member Author

/retitle Bug 1986003: Rebase to Kubernetes 1.22

@openshift-ci openshift-ci bot changed the title BUILD-297: Bump Kubernetes to v1.22 Bug 1986003: Rebase to Kubernetes 1.22 Aug 19, 2021
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 19, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2021

@coreydaley: This pull request references Bugzilla bug 1986003, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1986003: Rebase to Kubernetes 1.22

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.

@coreydaley
Copy link
Member Author

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2021

@coreydaley: This pull request references Bugzilla bug 1986003, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@coreydaley
Copy link
Member Author

/bugzilla refresh

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Aug 19, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2021

@coreydaley: This pull request references Bugzilla bug 1986003, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @wangke19

In response to this:

/bugzilla refresh

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 removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Aug 19, 2021
@openshift-ci openshift-ci bot requested a review from wangke19 August 19, 2021 17:02
@openshift-merge-robot openshift-merge-robot merged commit 31e9b2f into openshift:master Aug 19, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2021

@coreydaley: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 1986003 has not been moved to the MODIFIED state.

In response to this:

Bug 1986003: Rebase to Kubernetes 1.22

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.

@jitendar-singh
Copy link

/qe-approved

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. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants