Bug 2028257: Check if generic_plugin is loaded before invoking it #598

EmilienM · 2021-12-02T13:36:48Z

(cherry picked from commit 59cbb8b)

openshift-ci · 2021-12-02T13:36:54Z

@EmilienM: This pull request references Bugzilla bug 2015835, which is invalid:

expected dependent Bugzilla bug 2015481 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 2028256 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2028257 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2028257 to target a release in 4.9.0, 4.9.z, but it targets "4.8.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.

EmilienM · 2021-12-02T13:37:13Z

/assign zshi-redhat

zshi-redhat · 2021-12-03T02:33:52Z

/lgtm
/approve
/label backport-risk-assessed

openshift-ci · 2021-12-03T02:34:23Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EmilienM, zshi-redhat

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~~ [zshi-redhat]

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

openshift-bot · 2021-12-04T01:00:44Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-04T01:00:50Z

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

expected dependent Bugzilla bug 2015481 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 2028256 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2028257 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2028257 to target a release in 4.9.0, 4.9.z, but it targets "4.8.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.

openshift-bot · 2021-12-05T01:00:31Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-05T01:00:37Z

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

expected dependent Bugzilla bug 2015481 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 2028256 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2028257 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2028257 to target a release in 4.9.0, 4.9.z, but it targets "4.8.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.

openshift-bot · 2021-12-06T01:00:36Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-06T01:00:41Z

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

expected dependent Bugzilla bug 2015481 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 2028256 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2028257 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2028257 to target a release in 4.9.0, 4.9.z, but it targets "4.8.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.

openshift-bot · 2021-12-07T01:00:36Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-07T01:00:43Z

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

expected dependent Bugzilla bug 2015481 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 2028256 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2028257 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2028257 to target a release in 4.9.0, 4.9.z, but it targets "4.8.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.

openshift-bot · 2021-12-08T01:00:51Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-08T01:00:57Z

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

expected dependent Bugzilla bug 2015481 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 2028256 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2028257 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2028257 to target a release in 4.9.0, 4.9.z, but it targets "4.8.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.

EmilienM · 2021-12-08T14:19:44Z

/bugzilla refresh

openshift-ci · 2021-12-08T14:19:48Z

@EmilienM: This pull request references Bugzilla bug 2015835, which is invalid:

expected dependent Bugzilla bug 2028256 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2028257 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.0" instead
expected dependent Bugzilla bug 2028257 to target a release in 4.9.0, 4.9.z, but it targets "4.8.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.

openshift-ci · 2021-12-08T14:33:04Z

@EmilienM: This pull request references Bugzilla bug 2028257, which is invalid:

expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.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.

EmilienM · 2021-12-08T14:33:07Z

/bugzilla refresh

openshift-ci · 2021-12-08T14:33:11Z

@EmilienM: This pull request references Bugzilla bug 2028257, which is invalid:

expected dependent Bugzilla bug 2015481 to target a release in 4.9.0, 4.9.z, but it targets "4.10.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 · 2021-12-13T14:36:13Z

@zshi-redhat: This pull request references Bugzilla bug 2028257, which is invalid:

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

zshi-redhat · 2021-12-13T14:44:17Z

/bugzilla refresh

openshift-ci · 2021-12-13T14:45:23Z

@zshi-redhat: This pull request references Bugzilla bug 2028257, which is invalid:

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

zshi-redhat · 2021-12-13T14:47:30Z

/bugzilla refresh

openshift-ci · 2021-12-13T14:47:34Z

@zshi-redhat: This pull request references Bugzilla bug 2028257, which is invalid:

expected dependent Bugzilla bug 2028256 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.

zshi-redhat · 2021-12-13T14:49:25Z

I duplicated the above bug to bz2028256 which is ON_QA, once it is verified, this PR can be refreshed to get the valid-bug label.

openshift-bot · 2021-12-14T01:00:26Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-14T01:00:34Z

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

expected dependent Bugzilla bug 2028256 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-12-15T01:00:56Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-15T01:01:00Z

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

expected dependent Bugzilla bug 2028256 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-12-16T01:00:16Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-16T01:00:21Z

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

expected dependent Bugzilla bug 2028256 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-12-17T01:00:49Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-17T01:00:53Z

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

expected dependent Bugzilla bug 2028256 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-12-18T01:00:45Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-18T01:00:49Z

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

expected dependent Bugzilla bug 2028256 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-12-19T01:01:12Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-19T01:01:16Z

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

expected dependent Bugzilla bug 2028256 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-12-20T01:01:14Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-12-20T01:01:18Z

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

expected dependent Bugzilla bug 2028256 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.

EmilienM · 2021-12-20T14:20:58Z

/bugzilla refresh

openshift-ci · 2021-12-20T14:21:04Z

@EmilienM: This pull request references Bugzilla bug 2028257, which is valid.

6 validation(s) were run on this bug

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

No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request.

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.

zhaozhanqi · 2021-12-21T02:19:51Z

/label cherry-pick-approved

openshift-ci · 2021-12-21T03:24:10Z

@EmilienM: all tests passed!

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 · 2021-12-21T03:25:30Z

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

openshift/sriov-network-operator#598

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

Add wrapper for utils package from sriov-device-plugin

Check if generic_plugin is loaded before invoking it

78cb7e9

(cherry picked from commit 59cbb8b)

openshift-ci bot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent 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 Dec 2, 2021

EmilienM mentioned this pull request Dec 2, 2021

[release-4.8] Bug 2015835: Sync upstream: 2021-10-20 #596

Closed

openshift-ci bot assigned zshi-redhat Dec 2, 2021

openshift-ci bot requested review from pliurh and s1061123 December 2, 2021 13:38

openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. lgtm Indicates that a PR is ready to be merged. labels Dec 3, 2021

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

EmilienM changed the title ~~Bug 2015835: Check if generic_plugin is loaded before invoking it~~ Bug 2028257: Check if generic_plugin is loaded before invoking it Dec 8, 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 Dec 20, 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 Dec 20, 2021

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 Dec 21, 2021

openshift-merge-robot merged commit 6ad9128 into openshift:release-4.8 Dec 21, 2021

zeeke added a commit to zeeke/sriov-network-operator that referenced this pull request Feb 1, 2024

Merge pull request openshift#598 from ykulazhenkov/pr-dputis-wrapper

9648745

Add wrapper for utils package from sriov-device-plugin

Bug 2028257: Check if generic_plugin is loaded before invoking it #598

Bug 2028257: Check if generic_plugin is loaded before invoking it #598

Conversation

EmilienM commented Dec 2, 2021

openshift-ci bot commented Dec 2, 2021

EmilienM commented Dec 2, 2021

zshi-redhat commented Dec 3, 2021

openshift-ci bot commented Dec 3, 2021

openshift-bot commented Dec 4, 2021

openshift-ci bot commented Dec 4, 2021

openshift-bot commented Dec 5, 2021

openshift-ci bot commented Dec 5, 2021

openshift-bot commented Dec 6, 2021

openshift-ci bot commented Dec 6, 2021

openshift-bot commented Dec 7, 2021

openshift-ci bot commented Dec 7, 2021

openshift-bot commented Dec 8, 2021

openshift-ci bot commented Dec 8, 2021

EmilienM commented Dec 8, 2021

openshift-ci bot commented Dec 8, 2021

openshift-ci bot commented Dec 8, 2021

EmilienM commented Dec 8, 2021

openshift-ci bot commented Dec 8, 2021

openshift-ci bot commented Dec 13, 2021

zshi-redhat commented Dec 13, 2021

openshift-ci bot commented Dec 13, 2021

zshi-redhat commented Dec 13, 2021

openshift-ci bot commented Dec 13, 2021

zshi-redhat commented Dec 13, 2021

openshift-bot commented Dec 14, 2021

openshift-ci bot commented Dec 14, 2021

openshift-bot commented Dec 15, 2021

openshift-ci bot commented Dec 15, 2021

openshift-bot commented Dec 16, 2021

openshift-ci bot commented Dec 16, 2021

openshift-bot commented Dec 17, 2021

openshift-ci bot commented Dec 17, 2021

openshift-bot commented Dec 18, 2021

openshift-ci bot commented Dec 18, 2021

openshift-bot commented Dec 19, 2021

openshift-ci bot commented Dec 19, 2021

openshift-bot commented Dec 20, 2021

openshift-ci bot commented Dec 20, 2021

EmilienM commented Dec 20, 2021

openshift-ci bot commented Dec 20, 2021

zhaozhanqi commented Dec 21, 2021

openshift-ci bot commented Dec 21, 2021

openshift-ci bot commented Dec 21, 2021