[release-4.2] Bug 1849324: UPSTREAM: 89937: portAllocator sync local data before allocate #25177

openshift-cherrypick-robot · 2020-06-20T16:34:00Z

This is an automated cherry-pick of #25150

/assign sttts

openshift-ci-robot · 2020-06-20T16:34:12Z

@openshift-cherrypick-robot: Bugzilla bug 1848379 has been cloned as Bugzilla bug 1849324. Retitling PR to link against new bug.
/retitle [release-4.2] Bug 1849324: UPSTREAM: 89937: portAllocator sync local data before allocate

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-06-20T16:34:30Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is MODIFIED instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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.

sttts · 2020-06-24T07:30:10Z

/retest
/lgtm
/approve
/assign @mfojtik

openshift-ci-robot · 2020-06-24T07:30:46Z

[APPROVALNOTIFIER] This PR is APPROVED

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

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~~ [sttts]

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-06-25T01:00:12Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-06-25T01:00:15Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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-06-26T01:00:49Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-06-26T01:00:51Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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-06-27T01:01:08Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-06-27T01:01:10Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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-06-28T01:00:52Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-06-28T01:00:55Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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-06-29T01:00:59Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-06-29T01:01:02Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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-06-30T01:00:54Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-06-30T01:00:57Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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-07-01T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci-robot · 2020-07-01T01:00:25Z

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

expected dependent Bugzilla bug 1848379 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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-07-02T01:00:42Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-09T01:00:48Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-10T01:00:29Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-10T01:00:46Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-11T01:00:31Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-11T01:00:48Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-12T01:01:25Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-12T01:01:43Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-13T01:01:13Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-13T01:01:54Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-14T01:01:14Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-14T01:01:39Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-15T01:00:46Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-15T01:01:20Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-16T01:00:42Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-16T01:01:05Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-17T01:01:02Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-17T01:01:22Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-18T01:01:06Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-18T01:01:29Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-19T01:01:01Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-19T01:01:25Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-20T01:00:55Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-20T01:01:18Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-21T01:01:11Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-21T01:01:37Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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 · 2022-04-22T01:00:43Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-04-22T01:01:13Z

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

expected the bug to be open, but it isn't
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is CLOSED (WONTFIX) instead
expected dependent Bugzilla bug 1848379 to target a release in 4.3.0, 4.3.z, but it targets "4.6.0" 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.

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.

deads2k · 2022-04-22T15:25:46Z

/close

closing due to age. If this fix is still required, please work through CEE.

openshift-ci · 2022-04-22T15:26:26Z

@deads2k: Closed this PR.

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.

UPSTREAM: 89937: portAllocator sync local data before allocate

7fbe528

openshift-ci-robot assigned sttts Jun 20, 2020

openshift-cherrypick-robot mentioned this pull request Jun 20, 2020

Bug 1848379: UPSTREAM: 89937: portAllocator sync local data before allocate #25150

Merged

openshift-ci-robot requested review from smarterclayton and tbielawa June 20, 2020 16:34

openshift-ci-robot changed the title ~~[release-4.2] Bug 1848379: UPSTREAM: 89937: portAllocator sync local data before allocate~~ [release-4.2] Bug 1849324: UPSTREAM: 89937: portAllocator sync local data before allocate Jun 20, 2020

openshift-ci-robot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Jun 20, 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 Jun 20, 2020

openshift-ci-robot assigned mfojtik Jun 24, 2020

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

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

deads2k closed this Apr 22, 2022

[release-4.2] Bug 1849324: UPSTREAM: 89937: portAllocator sync local data before allocate #25177

[release-4.2] Bug 1849324: UPSTREAM: 89937: portAllocator sync local data before allocate #25177

Conversation

openshift-cherrypick-robot commented Jun 20, 2020

openshift-ci-robot commented Jun 20, 2020

openshift-ci-robot commented Jun 20, 2020

sttts commented Jun 24, 2020

openshift-ci-robot commented Jun 24, 2020

openshift-bot commented Jun 25, 2020

openshift-ci-robot commented Jun 25, 2020

openshift-bot commented Jun 26, 2020

openshift-ci-robot commented Jun 26, 2020

openshift-bot commented Jun 27, 2020

openshift-ci-robot commented Jun 27, 2020

openshift-bot commented Jun 28, 2020

openshift-ci-robot commented Jun 28, 2020

openshift-bot commented Jun 29, 2020

openshift-ci-robot commented Jun 29, 2020

openshift-bot commented Jun 30, 2020

openshift-ci-robot commented Jun 30, 2020

openshift-bot commented Jul 1, 2020

openshift-ci-robot commented Jul 1, 2020

openshift-bot commented Jul 2, 2020

openshift-ci bot commented Apr 9, 2022

openshift-bot commented Apr 10, 2022

openshift-ci bot commented Apr 10, 2022

openshift-bot commented Apr 11, 2022

openshift-ci bot commented Apr 11, 2022

openshift-bot commented Apr 12, 2022

openshift-ci bot commented Apr 12, 2022

openshift-bot commented Apr 13, 2022

openshift-ci bot commented Apr 13, 2022

openshift-bot commented Apr 14, 2022

openshift-ci bot commented Apr 14, 2022

openshift-bot commented Apr 15, 2022

openshift-ci bot commented Apr 15, 2022

openshift-bot commented Apr 16, 2022

openshift-ci bot commented Apr 16, 2022

openshift-bot commented Apr 17, 2022

openshift-ci bot commented Apr 17, 2022

openshift-bot commented Apr 18, 2022

openshift-ci bot commented Apr 18, 2022

openshift-bot commented Apr 19, 2022

openshift-ci bot commented Apr 19, 2022

openshift-bot commented Apr 20, 2022

openshift-ci bot commented Apr 20, 2022

openshift-bot commented Apr 21, 2022

openshift-ci bot commented Apr 21, 2022

openshift-bot commented Apr 22, 2022

openshift-ci bot commented Apr 22, 2022

deads2k commented Apr 22, 2022

openshift-ci bot commented Apr 22, 2022