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.12] OCPBUGS-7561: Fix SLAVE port going to master or listening state #200

Merged
merged 2 commits into from Mar 2, 2023

Conversation

aneeshkp
Copy link
Member

/jira cherrypick OCPBUGS-5465

Signed-off-by: Aneesh Puttur <aneeshputtur@gmail.com>

Signed-off-by: Aneesh Puttur <aneeshputtur@gmail.com>
Signed-off-by: Aneesh Puttur <aneeshputtur@gmail.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 15, 2023

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

Fix SLAVE port going to master or listening state

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.

@aneeshkp
Copy link
Member Author

/jira cherrypick OCPBUGS-5465

@openshift-ci-robot
Copy link

@aneeshkp: Jira Issue OCPBUGS-5465 has been cloned as Jira Issue OCPBUGS-7561. Retitling PR to link against new bug.
/retitle OCPBUGS-7561: Fix SLAVE port going to master or listening state

In response to this:

/jira cherrypick OCPBUGS-5465

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 Fix SLAVE port going to master or listening state OCPBUGS-7561: Fix SLAVE port going to master or listening state Feb 15, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 15, 2023

@aneeshkp: 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-7561: Fix SLAVE port going to master or listening state

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

@aneeshkp: This pull request references Jira Issue OCPBUGS-7561, which is invalid:

  • expected dependent Jira Issue OCPBUGS-5465 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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:

/jira cherrypick OCPBUGS-5465

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.

@aneeshkp
Copy link
Member Author

/test e2e-aws

@aneeshkp
Copy link
Member Author

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

@aneeshkp: you cannot LGTM your own PR.

In response to this:

/lgtm

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.

@aneeshkp aneeshkp changed the title OCPBUGS-7561: Fix SLAVE port going to master or listening state [release-4.12] OCPBUGS-7561: Fix SLAVE port going to master or listening state Feb 16, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2023

@aneeshkp: 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.12] OCPBUGS-7561: Fix SLAVE port going to master or listening state

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.

@aneeshkp
Copy link
Member Author

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 23, 2023

@aneeshkp: you cannot LGTM your own PR.

In response to this:

/lgtm

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
Member

@jzding jzding 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 Feb 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aneeshkp, jzding, nishant-parekh

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

@aneeshkp
Copy link
Member Author

aneeshkp commented Mar 1, 2023

/jira refresh

@openshift-ci-robot
Copy link

@aneeshkp: This pull request references Jira Issue OCPBUGS-7561, which is invalid:

  • expected dependent Jira Issue OCPBUGS-5465 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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:

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

@aneeshkp aneeshkp merged commit 1bf71a2 into redhat-cne:release-4.12 Mar 2, 2023
@openshift-ci-robot
Copy link

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

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

In response to this:

/jira cherrypick OCPBUGS-5465

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

[ART PR BUILD NOTIFIER] (beta)

This PR has been included in build cloud-event-proxy-container-v4.12.0-202303021731.p0.g1bf71a2.assembly.stream for distgit cloud-event-proxy.
All builds following this will include this PR.

1 similar comment
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER] (beta)

This PR has been included in build cloud-event-proxy-container-v4.12.0-202303021731.p0.g1bf71a2.assembly.stream for distgit cloud-event-proxy.
All builds following this will include this PR.

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

5 participants