openshift / ocp-release-operator-sdk

Apache License 2.0
16 stars 39 forks source link

OCPBUGS-6744: Merge upstream tag v1.25.4 to release-4.12 #299

Closed rashmigottipati closed 1 year ago

rashmigottipati commented 1 year ago

This PR is to downstream the upstream Operator-SDK v1.25.4 patch release to the release-4.12 branch.

Merge executed via ./UPSTREAM-MERGE.sh v1.25.4 release-4.12

Patches verified via make -f ci/prow.Makefile patch build

openshift-ci[bot] commented 1 year ago

@rashmigottipati: 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](https://github.com/openshift/ocp-release-operator-sdk/pull/299): >Merge upstream tag v1.25.4 to release-4.12 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
jmrodri commented 1 year ago

@rashmigottipati looks great. Nicely done.

openshift-ci[bot] commented 1 year ago

@rashmigottipati: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci[bot] commented 1 year ago

@rashmigottipati: 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](https://github.com/openshift/ocp-release-operator-sdk/pull/299): >OCPBUGS-6744: Merge upstream tag v1.25.4 to release-4.12 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
openshift-ci-robot commented 1 year ago

@rashmigottipati: This pull request references Jira Issue OCPBUGS-6744, which is invalid:

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](https://github.com/openshift/ocp-release-operator-sdk/pull/299): >This PR is to downstream the upstream Operator-SDK v1.25.4 patch release to the release-4.12 branch. > >Merge executed via `./UPSTREAM-MERGE.sh v1.25.4 release-4.12` > >Patches verified via `make -f ci/prow.Makefile patch build` Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
rashmigottipati commented 1 year ago

/jira refresh

openshift-ci-robot commented 1 year ago

@rashmigottipati: This pull request references Jira Issue OCPBUGS-6744, which is invalid:

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](https://github.com/openshift/ocp-release-operator-sdk/pull/299#issuecomment-1407103935): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
emmajiafan commented 1 year ago

/label qe-approved

emmajiafan commented 1 year ago

/jira refresh

openshift-ci-robot commented 1 year ago

@emmajiafan: This pull request references Jira Issue OCPBUGS-6744, which is invalid:

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](https://github.com/openshift/ocp-release-operator-sdk/pull/299#issuecomment-1407238099): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
emmajiafan commented 1 year ago

/jira refresh

openshift-ci-robot commented 1 year ago

@emmajiafan: This pull request references Jira Issue OCPBUGS-6744, which is valid.

6 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.12.z) matches configured target version for branch (4.12.z) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-6748](https://issues.redhat.com//browse/OCPBUGS-6748) is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE)) * dependent [Jira Issue OCPBUGS-6748](https://issues.redhat.com//browse/OCPBUGS-6748) targets the "4.13.0" version, which is one of the valid target versions: 4.13.0 * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/299#issuecomment-1407241688): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
michaelryanpeter commented 1 year ago

/label docs-approved

everettraven commented 1 year ago

/approved

everettraven commented 1 year ago

/approve

rashmigottipati commented 1 year ago

@emmajiafan could you also please add the backport-risk-assessed label as well?

cc @oceanc80

openshift-ci[bot] commented 1 year ago

@emmajiafan: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers]

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/299#issuecomment-1409607193): >/label backport-risk-assessed Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
oceanc80 commented 1 year ago

/approve

oceanc80 commented 1 year ago

label backport-risk-assessed

oceanc80 commented 1 year ago

/label backport-risk-assessed

oceanc80 commented 1 year ago

/lgtm

theishshah commented 1 year ago

/lgtm

theishshah commented 1 year ago

/approve

openshift-ci[bot] commented 1 year ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, oceanc80, rashmigottipati, theishshah

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: - ~~[OWNERS](https://github.com/openshift/ocp-release-operator-sdk/blob/release-4.12/OWNERS)~~ [theishshah] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
emmajiafan commented 1 year ago

/label cherry-pick-approved

openshift-ci-robot commented 1 year ago

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

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/299): >This PR is to downstream the upstream Operator-SDK v1.25.4 patch release to the release-4.12 branch. > >Merge executed via `./UPSTREAM-MERGE.sh v1.25.4 release-4.12` > >Patches verified via `make -f ci/prow.Makefile patch build` Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.