[release-4.10] Bug 2111552: Remove conntrack entries after rules #1219

tssurya · 2022-07-29T12:08:08Z

When service is deleted, we were removing the conntrack
entries before removing the flows/iptable rules. It's
safer to do the reverse so that in the nano second interim
the conntrack entries don't get recreated before the rules/flows
get deleted.

Signed-off-by: Surya Seetharaman suryaseetharaman.9@gmail.com
(cherry picked from commit 58b23ea)
(cherry picked from commit 525e7f1)

CLEAN PICK from #1218

When service is deleted, we were removing the conntrack entries before removing the flows/iptable rules. It's safer to do the reverse so that in the nano second interim the conntrack entries don't get recreated before the rules/flows get deleted. Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com> (cherry picked from commit 58b23ea) (cherry picked from commit 525e7f1)

openshift-ci · 2022-07-29T12:08:41Z

@tssurya: This pull request references Bugzilla bug 2111552, which is invalid:

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, but it targets "4.12.0" instead
expected dependent Bugzilla bug 2111548 to target a release in 4.11.0, but it targets "4.11.z" 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.

tssurya · 2022-08-01T10:41:52Z

/retest

jcaamano · 2022-08-16T17:40:50Z

/lgtm
/approve
/label backport-risk-assessed

openshift-ci · 2022-08-16T17:41:24Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, tssurya

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

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

openshift-bot · 2022-08-17T01:01:08Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-17T01:01:33Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-18T01:00:56Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-18T01:01:07Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-19T01:01:05Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-19T01:01:16Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-20T01:00:43Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-20T01:00:57Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-21T01:00:43Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-21T01:01:00Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-22T01:00:47Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-22T01:01:07Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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.

weliang1 · 2022-08-22T21:21:59Z

/label cherry-pick-approved

openshift-bot · 2022-08-23T01:03:15Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-23T01:03:27Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-ci · 2022-08-25T01:01:29Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-26T01:01:14Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-26T01:01:29Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-27T01:01:09Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-27T01:01:21Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-28T01:01:09Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-28T01:01:17Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-29T01:01:11Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-30T01:00:36Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-30T01:00:57Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-08-31T01:00:38Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-08-31T01:01:01Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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-09-01T01:00:28Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-09-01T01:00:55Z

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

expected dependent Bugzilla bug 2111534 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead
expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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.

weliang1 · 2022-09-01T18:20:34Z

/label qe-approved

openshift-bot · 2022-09-02T01:07:52Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-09-02T01:08:10Z

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

expected dependent Bugzilla bug 2111548 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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.

tssurya · 2022-09-02T11:54:35Z

/bugzilla refresh

openshift-ci · 2022-09-02T11:54:42Z

@tssurya: This pull request references Bugzilla bug 2111552, which is invalid:

expected dependent Bugzilla bug 2111534 to target a release in 4.11.0, 4.11.z, but it targets "4.12.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.

tssurya · 2022-09-02T11:55:40Z

/bugzilla refresh

openshift-ci · 2022-09-02T11:55:49Z

@tssurya: This pull request references Bugzilla bug 2111552, which is valid.

6 validation(s) were run on this bug

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

Requesting review from QA contact:
/cc @anuragthehatter

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 · 2022-09-02T15:54:07Z

@tssurya: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-vsphere-ovn	`bedef57`	link	false	`/test e2e-vsphere-ovn`

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

openshift-ci-robot · 2022-09-02T16:00:04Z

/retest-required

Remaining retests: 0 against base HEAD 8ebd5c1 and 2 for PR HEAD bedef57 in total

openshift-ci · 2022-09-02T19:00:58Z

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

openshift/ovn-kubernetes#1219

Bugzilla bug 2111552 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.

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 Jul 29, 2022

openshift-ci bot requested review from JacobTanenbaum and jcaamano July 29, 2022 12:09

tssurya changed the title ~~Bug 2111552: Remove conntrack entries after rules~~ [release-4.10] Bug 2111552: Remove conntrack entries after rules Jul 29, 2022

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

openshift-ci bot assigned jcaamano Aug 16, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 16, 2022

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 16, 2022

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 Aug 22, 2022

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Sep 1, 2022

openshift-ci bot 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 2, 2022

openshift-ci bot requested a review from anuragthehatter September 2, 2022 11:55

openshift-merge-robot merged commit b17d789 into openshift:release-4.10 Sep 2, 2022

[release-4.10] Bug 2111552: Remove conntrack entries after rules #1219

[release-4.10] Bug 2111552: Remove conntrack entries after rules #1219

Conversation

tssurya commented Jul 29, 2022

openshift-ci bot commented Jul 29, 2022

tssurya commented Aug 1, 2022

jcaamano commented Aug 16, 2022

openshift-ci bot commented Aug 16, 2022

openshift-bot commented Aug 17, 2022

openshift-ci bot commented Aug 17, 2022

openshift-bot commented Aug 18, 2022

openshift-ci bot commented Aug 18, 2022

openshift-bot commented Aug 19, 2022

openshift-ci bot commented Aug 19, 2022

openshift-bot commented Aug 20, 2022

openshift-ci bot commented Aug 20, 2022

openshift-bot commented Aug 21, 2022

openshift-ci bot commented Aug 21, 2022

openshift-bot commented Aug 22, 2022

openshift-ci bot commented Aug 22, 2022

weliang1 commented Aug 22, 2022

openshift-bot commented Aug 23, 2022

openshift-ci bot commented Aug 23, 2022

openshift-ci bot commented Aug 25, 2022

openshift-bot commented Aug 26, 2022

openshift-ci bot commented Aug 26, 2022

openshift-bot commented Aug 27, 2022

openshift-ci bot commented Aug 27, 2022

openshift-bot commented Aug 28, 2022

openshift-ci bot commented Aug 28, 2022

openshift-bot commented Aug 29, 2022

openshift-ci bot commented Aug 29, 2022

openshift-bot commented Aug 30, 2022

openshift-ci bot commented Aug 30, 2022

openshift-bot commented Aug 31, 2022

openshift-ci bot commented Aug 31, 2022

openshift-bot commented Sep 1, 2022

openshift-ci bot commented Sep 1, 2022

weliang1 commented Sep 1, 2022

openshift-bot commented Sep 2, 2022

openshift-ci bot commented Sep 2, 2022

tssurya commented Sep 2, 2022

openshift-ci bot commented Sep 2, 2022

tssurya commented Sep 2, 2022

openshift-ci bot commented Sep 2, 2022

openshift-ci bot commented Sep 2, 2022 • edited

openshift-ci-robot commented Sep 2, 2022

openshift-ci bot commented Sep 2, 2022

openshift-ci bot commented Sep 2, 2022 •

edited