[release-4.4] Bug 1815141: Filter out datavolumes which do not have owner reference

[openshift-cherrypick-robot]

This is an automated cherry-pick of #4776

/assign rawagner

[openshift-ci-robot]

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

• expected the bug to target the "4.4.0" release, but it targets "4.5.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is MODIFIED instead
• expected Bugzilla bug 1815138 to depend on a bug targeting the "4.5.0" release and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

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:

[release-4.4] Bug 1815138: Filter out datavolumes which do not have owner reference

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.

[rawagner]

/retitle [release-4.4] Bug 1815141: Filter out datavolumes which do not have owner reference

[openshift-ci-robot]

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

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

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.4] Bug 1815141: Filter out datavolumes which do not have owner reference

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.

[rawagner]

/retest

[rawagner]

/bugzilla refresh

[openshift-ci-robot]

@rawagner: This pull request references Bugzilla bug 1815141, 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.4.0) matches configured target release for branch (4.4.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1815138 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
• dependent Bugzilla bug 1815138 targets the "4.5.0" release, matching the expected (4.5.0) release
• bug has dependents

In response to this:

/bugzilla refresh

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.

[rawagner]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• frontend/packages/kubevirt-plugin/OWNERS [rawagner]

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

[openshift-bot]

/retest

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

[openshift-bot]

/retest

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

[openshift-ci-robot]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: openshift/console#4807. Bugzilla bug 1815141 has been moved to the MODIFIED state.

In response to this:

[release-4.4] Bug 1815141: Filter out datavolumes which do not have owner reference

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.