Bug 1918133: improve 4.7 failure tests part2

[gouyang]

Notes for reviewer:

1. remove unnecessary setOS as it's default to the template OS.
2. improve volumeMode selection
3. add wait for VMI instead of using virtctl inspect vm login prompt, it's more stable.
4. enhance isOnDetailView and isOnListView for templates.
5. change provision source from CONTAINER to URL as URL take less time to import.
6. inactive test for CNV-3052/CNV-4096/CNV-2447 as it's covered in normal test sceriao and CNV-3657/CNV-4097 as it's not valid scenario any more.

[openshift-ci-robot]

@gouyang: This pull request references Bugzilla bug 1918133, which is invalid:

• expected the bug to target the "4.7.0" release, but it targets "---" 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:

Bug 1918133: improve 4.7 failure tests part2

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]

@gouyang: This pull request references Bugzilla bug 1918133, which is invalid:

• expected the bug to target the "4.7.0" release, but it targets "---" 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:

Bug 1918133: improve 4.7 failure tests part2

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]

@gouyang: This pull request references Bugzilla bug 1918133, which is invalid:

• expected the bug to target the "4.7.0" release, but it targets "---" 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:

Bug 1918133: improve 4.7 failure tests part2

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.

[gouyang]

/test kubevirt-plugin

[gouyang]

/bugzilla refresh

[openshift-ci-robot]

@gouyang: This pull request references Bugzilla bug 1918133, 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.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.7.0) matches configured target release for branch (4.7.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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.

[gouyang]

@yaacov @rawagner PTAL

[yaacov]

/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gouyang, yaacov

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 [yaacov]

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-ci-robot]

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

• openshift/console#7876

Bugzilla bug 1918133 has been moved to the MODIFIED state.

In response to this:

Bug 1918133: improve 4.7 failure tests part2

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.