[release-4.5] Bug 1874009: Ensure proper tagging of compute nodes ports #4120

openshift-cherrypick-robot · 2020-08-31T09:56:06Z

This is an automated cherry-pick of #4118

/assign luis5tb

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 · 2020-08-31T09:56:19Z

@openshift-cherrypick-robot: Bugzilla bug 1873448 has been cloned as Bugzilla bug 1874009. Retitling PR to link against new bug.
/retitle [release-4.5] Bug 1874009: Ensure proper tagging of compute nodes ports

Details

In response to this:

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 · 2020-08-31T09:56:40Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST instead

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:

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.

MaysaMacedo · 2020-08-31T09:58:39Z

/lgtm

MaysaMacedo · 2020-08-31T09:59:32Z

/label platform/openstack

pierreprinetti · 2020-08-31T10:22:55Z

/approve
/lgtm
/bugzilla-refresh

openshift-ci-robot · 2020-08-31T10:23:13Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierreprinetti

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~upi/openstack/OWNERS~~ [pierreprinetti]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-bot · 2020-08-31T14:01:08Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-08-31T17:29:05Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-08-31T18:47:05Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-08-31T19:13:02Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-08-31T21:10:07Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-08-31T23:19:59Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-09-01T00:03:14Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-09-01T01:00:45Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-01T01:00:49Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-02T01:00:50Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-02T01:00:53Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-03T01:00:40Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-03T01:00:43Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-04T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-04T01:00:26Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-05T01:01:26Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-05T01:01:29Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-06T01:00:52Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-06T01:00:56Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-07T01:00:50Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-07T01:00:54Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-08T01:00:51Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-08T01:01:06Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-09T01:01:04Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-09T01:01:08Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-10T01:01:14Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-10T01:01:18Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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 · 2020-09-11T01:01:18Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-09-11T01:01:22Z

@openshift-bot: This pull request references Bugzilla bug 1874009, which is invalid:

expected dependent Bugzilla bug 1873448 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead

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:

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.

luis5tb · 2020-09-11T13:15:01Z

/bugzilla refresh

openshift-ci-robot · 2020-09-11T13:15:10Z

@luis5tb: This pull request references Bugzilla bug 1874009, 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.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.5.z) matches configured target release for branch (4.5.z)
bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 1873448 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
dependent Bugzilla bug 1873448 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
bug has dependents

Details

In response to this:

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.

mtnbikenc · 2020-09-16T20:39:16Z

/uncc

markmc · 2020-09-17T15:34:05Z

Docs only change, fixes instructions for UPI on OpenStack with Kuryr

openshift-bot · 2020-09-18T04:13:00Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2020-09-18T04:26:15Z

/retest

Please review the full test history for this PR and help us cut down flakes.

openshift-ci-robot · 2020-09-18T07:25:07Z

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

openshift/installer#4120

Bugzilla bug 1874009 has been moved to the MODIFIED state.

Details

In response to this:

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.

Ensure proper tagging of compute nodes ports

6083bc4

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 assigned luis5tb Aug 31, 2020

openshift-cherrypick-robot mentioned this pull request Aug 31, 2020

Bug 1873448: Ensure proper tagging of compute nodes ports #4118

Merged

openshift-ci-robot requested review from jhixson74 and mtnbikenc August 31, 2020 09:56

openshift-ci-robot changed the title ~~[release-4.5] Bug 1873448: Ensure proper tagging of compute nodes ports~~ [release-4.5] Bug 1874009: Ensure proper tagging of compute nodes ports Aug 31, 2020

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 added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Aug 31, 2020

openshift-ci-robot assigned MaysaMacedo Aug 31, 2020

openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2020

openshift-ci-robot added the platform/openstack label Aug 31, 2020

openshift-ci-robot assigned pierreprinetti Aug 31, 2020

openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2020

openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Sep 11, 2020

openshift-ci-robot removed the request for review from mtnbikenc September 16, 2020 20:39

markmc added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 17, 2020

openshift-merge-robot merged commit 9893a48 into openshift:release-4.5 Sep 18, 2020

[release-4.5] Bug 1874009: Ensure proper tagging of compute nodes ports #4120

[release-4.5] Bug 1874009: Ensure proper tagging of compute nodes ports #4120

Uh oh!

Conversation

openshift-cherrypick-robot commented Aug 31, 2020

Uh oh!

openshift-ci-robot commented Aug 31, 2020

Uh oh!

openshift-ci-robot commented Aug 31, 2020

Uh oh!

MaysaMacedo commented Aug 31, 2020

Uh oh!

MaysaMacedo commented Aug 31, 2020

Uh oh!

pierreprinetti commented Aug 31, 2020

Uh oh!

openshift-ci-robot commented Aug 31, 2020

Uh oh!

openshift-bot commented Aug 31, 2020

Uh oh!

openshift-bot commented Aug 31, 2020

Uh oh!

openshift-bot commented Aug 31, 2020

Uh oh!

openshift-bot commented Aug 31, 2020

Uh oh!

openshift-bot commented Aug 31, 2020

Uh oh!

openshift-bot commented Aug 31, 2020

Uh oh!

openshift-bot commented Sep 1, 2020

Uh oh!

openshift-bot commented Sep 1, 2020

Uh oh!

openshift-ci-robot commented Sep 1, 2020

Uh oh!

openshift-bot commented Sep 2, 2020

Uh oh!

openshift-ci-robot commented Sep 2, 2020

Uh oh!

openshift-bot commented Sep 3, 2020

Uh oh!

openshift-ci-robot commented Sep 3, 2020

Uh oh!

openshift-bot commented Sep 4, 2020

Uh oh!

openshift-ci-robot commented Sep 4, 2020

Uh oh!

openshift-bot commented Sep 5, 2020

Uh oh!

openshift-ci-robot commented Sep 5, 2020

Uh oh!

openshift-bot commented Sep 6, 2020

Uh oh!

openshift-ci-robot commented Sep 6, 2020

Uh oh!

openshift-bot commented Sep 7, 2020

Uh oh!

openshift-ci-robot commented Sep 7, 2020

Uh oh!

openshift-bot commented Sep 8, 2020

Uh oh!

openshift-ci-robot commented Sep 8, 2020

Uh oh!

openshift-bot commented Sep 9, 2020

Uh oh!

openshift-ci-robot commented Sep 9, 2020

Uh oh!

openshift-bot commented Sep 10, 2020

Uh oh!

openshift-ci-robot commented Sep 10, 2020

Uh oh!

openshift-bot commented Sep 11, 2020

Uh oh!

openshift-ci-robot commented Sep 11, 2020

Uh oh!

luis5tb commented Sep 11, 2020

Uh oh!

openshift-ci-robot commented Sep 11, 2020

Uh oh!