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.

Sign up for GitHub

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

Jump to bottom

OCPBUGS-4604: [release-4.10] bump to kube 1.23.12 #323

Merged
merged 3 commits into from
Dec 21, 2022
Merged

OCPBUGS-4604: [release-4.10] bump to kube 1.23.12 #323

merged 3 commits into from
Dec 21, 2022

Conversation

sanchezl
Copy link
Contributor

@sanchezl sanchezl commented Oct 17, 2022 •
edited
Loading

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 17, 2022

@sanchezl: 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:

proof: bump kube 1.23.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 requested review from p0lyn0mial and tkashem October 17, 2022 19:42
@sanchezl sanchezl mentioned this pull request Oct 18, 2022
Merged
@sanchezl
Copy link
Contributor Author

/retest-required

@sanchezl
Copy link
Contributor Author

/retest

@sanchezl sanchezl force-pushed the release-4.10-bump-kube-1.23.12 branch from b54796d to 4ad84d5 Compare October 19, 2022 05:42
@sanchezl sanchezl changed the title proof: bump kube 1.23.12 bump kube 1.23.12 Oct 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 19, 2022

@sanchezl: 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:

bump kube 1.23.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.

@sanchezl sanchezl force-pushed the release-4.10-bump-kube-1.23.12 branch from 4ad84d5 to 17209bd Compare October 19, 2022 14:28
@sanchezl
Copy link
Contributor Author

/retest

@sanchezl sanchezl changed the title bump kube 1.23.12 [release-4.10] OCPBUGS-2553: bump to kube 1.23.12 Oct 26, 2022
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 26, 2022
@openshift-ci-robot
Copy link

@sanchezl: This pull request references Jira Issue OCPBUGS-2553, which is invalid:

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

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

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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
Contributor

openshift-ci bot commented Oct 26, 2022

@sanchezl: 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:

[release-4.10] OCPBUGS-2553: bump to kube 1.23.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.

@sanchezl
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 28, 2022

@sanchezl: 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.

@sanchezl sanchezl changed the title [release-4.10] OCPBUGS-2553: bump to kube 1.23.12 [release-4.10] bump to kube 1.23.12 Oct 28, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 28, 2022

@sanchezl: 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:

[release-4.10] bump to kube 1.23.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.

1 similar comment
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 28, 2022

@sanchezl: 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:

[release-4.10] bump to kube 1.23.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.

@tkashem
Copy link
Contributor

tkashem commented Dec 21, 2022

/label backport-risk-assessed
/lgtm
/approve

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Dec 21, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 21, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sanchezl, tkashem

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 Dec 21, 2022
@tkashem
Copy link
Contributor

tkashem commented Dec 21, 2022

/retitle OCPBUGS-4604: [release-4.10] bump to kube 1.23.12

@openshift-ci openshift-ci bot changed the title [release-4.10] bump to kube 1.23.12 OCPBUGS-4604: [release-4.10] bump to kube 1.23.12 Dec 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 21, 2022

@sanchezl: 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:

OCPBUGS-4604: [release-4.10] bump to kube 1.23.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-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. and removed jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. labels Dec 21, 2022
@openshift-ci-robot
Copy link

@sanchezl: This pull request references Jira Issue OCPBUGS-4604, which is invalid:

  • expected the bug to target the "4.10.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-4604 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Picks up kubernetes/kubernetes#109137.

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.

@tkashem
Copy link
Contributor

tkashem commented Dec 21, 2022

/jira refresh

@openshift-ci-robot
Copy link

@tkashem: This pull request references Jira Issue OCPBUGS-4604, which is invalid:

  • expected Jira Issue OCPBUGS-4604 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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

In response to this:

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

@tkashem
Copy link
Contributor

tkashem commented Dec 21, 2022

/override bugzilla/valid-bug

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 21, 2022

@tkashem: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • bugzilla/valid-bug

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-aws
  • ci/prow/e2e-aws-builds
  • ci/prow/e2e-aws-serial
  • ci/prow/e2e-aws-upgrade
  • ci/prow/e2e-cmd
  • ci/prow/images
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-openshift-apiserver-master-images
  • pull-ci-openshift-openshift-apiserver-master-unit
  • pull-ci-openshift-openshift-apiserver-master-verify
  • pull-ci-openshift-openshift-apiserver-master-verify-deps
  • pull-ci-openshift-openshift-apiserver-release-4.10-e2e-aws
  • pull-ci-openshift-openshift-apiserver-release-4.10-e2e-aws-builds
  • pull-ci-openshift-openshift-apiserver-release-4.10-e2e-aws-serial
  • pull-ci-openshift-openshift-apiserver-release-4.10-e2e-aws-upgrade
  • pull-ci-openshift-openshift-apiserver-release-4.10-e2e-cmd
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override bugzilla/valid-bug

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.

@tkashem
Copy link
Contributor

tkashem commented Dec 21, 2022

/label bugzilla/valid-bug

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 21, 2022

@tkashem: Can not set label bugzilla/valid-bug: Must be member in one of these teams: [openshift-patch-managers openshift-staff-engineers]

In response to this:

/label bugzilla/valid-bug

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.

@tkashem
Copy link
Contributor

tkashem commented Dec 21, 2022

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid 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 Dec 21, 2022
@openshift-ci-robot
Copy link

@tkashem: This pull request references Jira Issue OCPBUGS-4604, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.10.z) matches configured target version for branch (4.10.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-5115 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-5115 targets the "4.11.0" version, which is one of the valid target versions: 4.11.0, 4.11.z
  • bug has dependents

Requesting review from QA contact:
/cc @gangwgr

In response to this:

/jira 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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 21, 2022
@openshift-ci openshift-ci bot requested a review from gangwgr December 21, 2022 15:08
@gangwgr
Copy link

gangwgr commented Dec 21, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 21, 2022
@openshift-merge-robot openshift-merge-robot merged commit 67425d4 into openshift:release-4.10 Dec 21, 2022
@openshift-ci-robot
Copy link

@sanchezl: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-4604 has been moved to the MODIFIED state.

In response to this:

Picks up kubernetes/kubernetes#109137.

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
Reviewers

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

@tkashem tkashem Awaiting requested review from tkashem

@gangwgr gangwgr Awaiting requested review from gangwgr

Assignees

@tkashem tkashem

@xingxingxia xingxingxia

@wangke19 wangke19

@gangwgr gangwgr

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@sanchezl @openshift-ci-robot @tkashem @gangwgr @xingxingxia @openshift-merge-robot @wangke19