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 2087042: UPSTREAM: 333: Bump providers to k8s v1.24 #17

Merged
merged 4 commits into from Jun 24, 2022

Conversation

Fedosin
Copy link

@Fedosin Fedosin commented Jun 23, 2022

Upstream PR: kubernetes#333

@openshift-ci openshift-ci bot added 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. labels Jun 23, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jun 23, 2022

@Fedosin: This pull request references Bugzilla bug 2087042, 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.11.0) matches configured target release for branch (4.11.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 @sunzhaohua2

In response to this:

Bug 2087042: UPSTREAM: 333: Bump providers to k8s v1.24

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

openshift-ci bot commented Jun 23, 2022

@Fedosin: This pull request references Bugzilla bug 2087042, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.11.0) matches configured target release for branch (4.11.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 @sunzhaohua2

In response to this:

Bug 2087042: UPSTREAM: 333: Bump providers to k8s v1.24

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.

@damdo
Copy link
Member

damdo commented Jun 23, 2022

/retest

@JoelSpeed
Copy link

Changes look ok, would like to see some CI signal on this before labelling

@Fedosin
Copy link
Author

Fedosin commented Jun 23, 2022

/retest

5 similar comments
@Fedosin
Copy link
Author

Fedosin commented Jun 23, 2022

/retest

@damdo
Copy link
Member

damdo commented Jun 24, 2022

/retest

@damdo
Copy link
Member

damdo commented Jun 24, 2022

/retest

@damdo
Copy link
Member

damdo commented Jun 24, 2022

/retest

@damdo
Copy link
Member

damdo commented Jun 24, 2022

/retest

@openshift-ci
Copy link

openshift-ci bot commented Jun 24, 2022

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

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-ccm 9bf5d4b link false /test e2e-gcp-ccm
ci/prow/e2e-gcp-ccm-install 9bf5d4b link false /test e2e-gcp-ccm-install

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.

Copy link

@alexander-demicev alexander-demicev left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 24, 2022
@elmiko
Copy link

elmiko commented Jun 24, 2022

fwiw, i talked with upstream at the sig meeting and Jakub is also working on a PR to update the dependencies. we just need to be mindful when removing these commits that it might be a different pr than 333.
/approve

@openshift-ci
Copy link

openshift-ci bot commented Jun 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexander-demichev, elmiko

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 Jun 24, 2022
@openshift-ci openshift-ci bot merged commit 9a303b1 into openshift:master Jun 24, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jun 24, 2022

@Fedosin: 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 2087042 has not been moved to the MODIFIED state.

In response to this:

Bug 2087042: UPSTREAM: 333: Bump providers to k8s v1.24

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