Bug 2018129: Ensure KLB is updated #585

dulek · 2021-10-28T10:02:58Z

We're moving this because we discovered that Octavia will not always
raise Conflict if you create an LB with the same IP.

If no VIP port got created for an LB, then Octavia will not have any
issue with creating another LB with the same IP.

Closes-Bug: 1947809

Change-Id: I26b911b30403c7ea5a35706b2fc80af499e91330

We're moving this because we discovered that Octavia will not always raise Conflict if you create an LB with the same IP. If no VIP port got created for an LB, then Octavia will not have any issue with creating another LB with the same IP. Closes-Bug: 1947809 Change-Id: I26b911b30403c7ea5a35706b2fc80af499e91330

dulek · 2021-10-28T10:03:46Z

cc: @zerodayz

openshift-ci · 2021-10-28T10:04:09Z

@dulek: This pull request references Bugzilla bug 2018129, which is invalid:

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-10-29T09:50:49Z

/retest

MaysaMacedo · 2021-10-29T09:58:18Z

/lgtm

openshift-ci · 2021-10-29T10:02:56Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dulek, MaysaMacedo

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~~ [MaysaMacedo,dulek]

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

dulek · 2021-10-29T10:07:03Z

/label backport-risk-assesed

openshift-ci · 2021-10-29T10:07:04Z

@dulek: The label(s) /label backport-risk-assesed cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, backport-risk-assessed, cherry-pick-approved

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.

dulek · 2021-10-29T10:07:17Z

/label backport-risk-assessed

openshift-bot · 2021-10-30T01:00:41Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-10-30T01:00:45Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-10-31T01:00:21Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-10-31T01:00:27Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-01T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-01T01:00:26Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-02T01:00:26Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-02T01:00:35Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-03T01:00:40Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-03T01:00:44Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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.

zerodayz · 2021-11-03T05:39:47Z

Once this is merged can we /cherrypick release-4.8, 4.7 and 4.6 ?

dulek · 2021-11-03T08:54:30Z

It has little sense, QE needs to go through all the backports one-by-one, so once it's merged here we backport to 4.8, then once it's in 4.8 we backport to 4.7 and so on. There's the FastFix process, but I wouldn't really like it applied to this commit as it touches code that I find sensitive and prefer it to go through full QE validation.

zerodayz · 2021-11-03T11:36:34Z

Ack, thank you! 👍

openshift-bot · 2021-11-04T01:00:21Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-04T01:00:25Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-05T01:00:27Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-05T01:00:34Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-06T01:00:30Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-06T01:00:33Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-07T01:00:29Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-07T01:00:33Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-08T01:00:34Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-08T01:00:38Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-09T01:01:02Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-09T01:01:06Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-10T01:01:07Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-10T01:01:11Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-11T01:01:15Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-11T01:01:19Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-12T01:01:04Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-12T01:01:07Z

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

expected dependent Bugzilla bug 2014538 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), 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.

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 · 2021-11-13T01:00:36Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-13T01:00:44Z

@openshift-bot: This pull request references Bugzilla bug 2018129, 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.9.z) matches configured target release for branch (4.9.z)
bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2014538 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2014538 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
bug has dependents

Requesting review from QA contact:
/cc @eurijon

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.

eurijon · 2021-11-22T15:47:28Z

/label cherry-pick-approved

openshift-ci · 2021-11-22T16:15:18Z

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

openshift/kuryr-kubernetes#585

Bugzilla bug 2018129 has been moved to the MODIFIED state.

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.

dulek requested a review from MaysaMacedo October 28, 2021 10:03

openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 28, 2021

openshift-ci bot requested a review from luis5tb October 28, 2021 10:05

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2021

openshift-ci bot assigned MaysaMacedo Oct 29, 2021

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 29, 2021

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 29, 2021

openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Nov 13, 2021

openshift-ci bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Nov 13, 2021

openshift-ci bot requested a review from eurijon November 13, 2021 01:00

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 22, 2021

openshift-merge-robot merged commit 473fd0c into openshift:release-4.9 Nov 22, 2021

Bug 2018129: Ensure KLB is updated #585

Bug 2018129: Ensure KLB is updated #585

Conversation

dulek commented Oct 28, 2021

dulek commented Oct 28, 2021

openshift-ci bot commented Oct 28, 2021

MaysaMacedo commented Oct 29, 2021

MaysaMacedo commented Oct 29, 2021

openshift-ci bot commented Oct 29, 2021

dulek commented Oct 29, 2021

openshift-ci bot commented Oct 29, 2021

dulek commented Oct 29, 2021

openshift-bot commented Oct 30, 2021

openshift-ci bot commented Oct 30, 2021

openshift-bot commented Oct 31, 2021

openshift-ci bot commented Oct 31, 2021

openshift-bot commented Nov 1, 2021

openshift-ci bot commented Nov 1, 2021

openshift-bot commented Nov 2, 2021

openshift-ci bot commented Nov 2, 2021

openshift-bot commented Nov 3, 2021

openshift-ci bot commented Nov 3, 2021

zerodayz commented Nov 3, 2021

dulek commented Nov 3, 2021

zerodayz commented Nov 3, 2021

openshift-bot commented Nov 4, 2021

openshift-ci bot commented Nov 4, 2021

openshift-bot commented Nov 5, 2021

openshift-ci bot commented Nov 5, 2021

openshift-bot commented Nov 6, 2021

openshift-ci bot commented Nov 6, 2021

openshift-bot commented Nov 7, 2021

openshift-ci bot commented Nov 7, 2021

openshift-bot commented Nov 8, 2021

openshift-ci bot commented Nov 8, 2021

openshift-bot commented Nov 9, 2021

openshift-ci bot commented Nov 9, 2021

openshift-bot commented Nov 10, 2021

openshift-ci bot commented Nov 10, 2021

openshift-bot commented Nov 11, 2021

openshift-ci bot commented Nov 11, 2021

openshift-bot commented Nov 12, 2021

openshift-ci bot commented Nov 12, 2021

openshift-bot commented Nov 13, 2021

openshift-ci bot commented Nov 13, 2021

eurijon commented Nov 22, 2021

openshift-ci bot commented Nov 22, 2021