search

openshift / multi-operator-manager

experimental playspace
Apache License 2.0
3 stars 4 forks source link

[release-4.18] OCPBUGS-45119: make it more foolproof to manage controllers #56

Closed openshift-cherrypick-robot closed 3 days ago

openshift-cherrypick-robot commented 3 days ago

This is an automated cherry-pick of #55

/assign bertinatto

openshift-ci-robot commented 3 days ago

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: API-1835

In response to [this](https://github.com/openshift/multi-operator-manager/pull/56): >This is an automated cherry-pick of #55 > >/assign bertinatto Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fmulti-operator-manager). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
bertinatto commented 3 days ago

/retitle [release-4.18] OCPBUGS-45119: make it more foolproof to manage controllers

openshift-ci-robot commented 3 days ago

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-45119, which is valid.

7 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.18.0) matches configured target version for branch (4.18.0) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * release note type set to "Release Note Not Required" * dependent bug [Jira Issue OCPBUGS-45120](https://issues.redhat.com//browse/OCPBUGS-45120) is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED) * dependent [Jira Issue OCPBUGS-45120](https://issues.redhat.com//browse/OCPBUGS-45120) targets the "4.19.0" version, which is one of the valid target versions: 4.19.0 * bug has dependents

Requesting review from QA contact: /cc @wangke19

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

In response to [this](https://github.com/openshift/multi-operator-manager/pull/56): >This is an automated cherry-pick of #55 > >/assign bertinatto Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fmulti-operator-manager). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
bertinatto commented 3 days ago

/lgtm /approve /label backport-risk-assessed

openshift-ci[bot] commented 3 days ago

@bertinatto: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-patch-managers openshift-staff-engineers openshift-release-oversight]

In response to [this](https://github.com/openshift/multi-operator-manager/pull/56#issuecomment-2504398675): >/lgtm >/approve >/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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
openshift-ci[bot] commented 3 days ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, openshift-cherrypick-robot

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/multi-operator-manager/blob/release-4.18/OWNERS)~~ [bertinatto] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 3 days ago

@openshift-cherrypick-robot: 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci-robot commented 3 days ago

@openshift-cherrypick-robot: Jira Issue OCPBUGS-45119: 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 Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to [this](https://github.com/openshift/multi-operator-manager/pull/56): >This is an automated cherry-pick of #55 > >/assign bertinatto Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fmulti-operator-manager). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.