[release-4.8] Bug 1980302: VNC console stays in Connecting state

[openshift-cherrypick-robot]

This is an automated cherry-pick of #9400

/assign glekner

[openshift-ci]

@openshift-cherrypick-robot: Bugzilla bug 1977037 has been cloned as Bugzilla bug 1980302. Retitling PR to link against new bug.
/retitle [release-4.8] Bug 1980302: VNC console stays in Connecting state

In response to this:

[release-4.8] Bug 1977037: VNC console stays in Connecting state

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]

@openshift-cherrypick-robot: This pull request references Bugzilla bug 1980302, 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.8.0) matches configured target release for branch (4.8.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1977037 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Bugzilla bug 1977037 targets the "4.9.0" release, which is one of the valid target releases: 4.9.0
• bug has dependents

Requesting review from QA contact:
/cc @gouyang

In response to this:

[release-4.8] Bug 1980302: VNC console stays in Connecting state

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.

[yaacov]

@tnisan @gouyang this is a bckport of BZ1977037 to 4.8

Do we need to escalate and get "group-lead-approved" before 4.8.0 is out ?

[yaacov]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, 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

[kobi86]

Can we push this to the current version?
We are talking about access to VM issue, this can effect a lot of users

[yaacov]

Can we push this to the current version?
We are talking about access to VM issue, this can effect a lot of users

@kobi86 @tnisan hi, do we need to push this to 4.8.0 ?

cc:// @spadgett

[kobi86]

We must push it to 4.8, if some customers will upgrade OCP without CNV right away that will break the VNC console and with it the idea of CNV.
So yes, we need to make sure it's shipped with 4.8

[sdodson]

Re-validating bugzilla status after prow config updates.
/bugzilla refresh

[openshift-ci]

@sdodson: This pull request references Bugzilla bug 1980302, 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 1977037 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1977037 targets the "4.9.0" release, which is one of the valid target releases: 4.9.0
• bug has dependents

Requesting review from QA contact:
/cc @gouyang

In response to this:

Re-validating bugzilla status after prow config updates.
/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.

[openshift-ci]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

• openshift/console#9442

Bugzilla bug 1980302 has been moved to the MODIFIED state.

In response to this:

[release-4.8] Bug 1980302: VNC console stays in Connecting state

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.