Skip to content

[enterprise-4.4] Bug 1873448: Ensure proper tagging of compute node ports#25141

Merged
maxwelldb merged 2 commits intoopenshift:enterprise-4.4from
openshift-cherrypick-robot:cherry-pick-25137-to-enterprise-4.4
Aug 31, 2020
Merged

[enterprise-4.4] Bug 1873448: Ensure proper tagging of compute node ports#25141
maxwelldb merged 2 commits intoopenshift:enterprise-4.4from
openshift-cherrypick-robot:cherry-pick-25137-to-enterprise-4.4

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #25137

/assign maxwelldb

luis5tb and others added 2 commits August 31, 2020 14:51
Wrong tagging of compute node parent ports make kuryr not able
to find the precreated ports, thus breaking the kuryr ports pool
functionality
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Could not make automatic cherrypick of Bugzilla bug 1873448 for this PR as the target_release is not set for this branch in the bugzilla plugin config. Running refresh:
/bugzilla refresh

Details

In response to this:

[enterprise-4.4] Bug 1873448: Ensure proper tagging of compute node ports

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 the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Aug 31, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-ci-robot: This pull request references Bugzilla bug 1873448, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead
  • expected Bugzilla bug 1873448 to depend on a bug in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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

Details

In response to this:

@openshift-cherrypick-robot: Could not make automatic cherrypick of Bugzilla bug 1873448 for this PR as the target_release is not set for this branch in the bugzilla plugin config. Running refresh:
/bugzilla refresh

In response to this:

[enterprise-4.4] Bug 1873448: Ensure proper tagging of compute node ports

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.

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 bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 31, 2020
@maxwelldb maxwelldb merged commit 0930bdb into openshift:enterprise-4.4 Aug 31, 2020
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Bugzilla bug 1873448 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

Details

In response to this:

[enterprise-4.4] Bug 1873448: Ensure proper tagging of compute node ports

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

Labels

bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants