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

[release-4.9] Bug 2010188: Label ODF multicluster operator pod based on deployment name #47

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #44

/assign umangachapagain

Signed-off-by: Gowtham Shanmugasundaram <gshanmug@redhat.com>
Signed-off-by: Gowtham Shanmugasundaram <gshanmug@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 4, 2021

@openshift-cherrypick-robot: Bugzilla bug 2005843 has been cloned as Bugzilla bug 2010188. Retitling PR to link against new bug.
/retitle [release-4.9] Bug 2010188: Label ODF multicluster operator pod based on deployment name

In response to this:

[release-4.9] Bug 2005843: Label ODF multicluster operator pod based on deployment name

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 changed the title [release-4.9] Bug 2005843: Label ODF multicluster operator pod based on deployment name [release-4.9] Bug 2010188: Label ODF multicluster operator pod based on deployment name Oct 4, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 4, 2021

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2010188, which is valid. The bug has been moved to the POST state. 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 (ODF 4.9.0) matches configured target release for branch (ODF 4.9.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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

In response to this:

[release-4.9] Bug 2010188: Label ODF multicluster operator pod based on deployment name

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.

Copy link
Contributor

@umangachapagain umangachapagain 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
Copy link
Contributor

openshift-ci bot commented Oct 4, 2021

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@umangachapagain
Copy link
Contributor

/retest

@openshift-merge-robot openshift-merge-robot merged commit ec8e846 into red-hat-storage:release-4.9 Oct 6, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2021

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2010188 has been moved to the MODIFIED state.

In response to this:

[release-4.9] Bug 2010188: Label ODF multicluster operator pod based on deployment name

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants