Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The vm console shows "Disconnected" after click Run in the vm details page
Version-Release number of selected component (if applicable):
cockpit-machines-234-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare an off vm
2. Click the vm name to enter the vm details page, click Run
Actual results:
It shows "Disconnected" in the Console tab in step 2.
But after return to the Virtual machines page and enter the vm details page again, the console tab shows fine.
Expected results:
It should show the running vm console directly after click Run in Step 2.
Additional info:
This will be fixed in cockpit-machines-236.
This upstream commit should should have fixed the problem.
commit 7924a15f7284b5f2977051f4bed243ee93e5f0a5
Author: Katerina Koukiou <kkoukiou>
Date: Wed Dec 9 17:12:42 2020 +0100
package.json: upgrade the react-console dependency
Pre verified with package:
cockpit-machines-236-1.el8.noarch
Steps :
1. Prepare an off vm
2. Click the vm name to enter the vm details page, click Run
It shows the running vm console directly after click Run in Step 2.
So pre-verified.
re verified with package:
cockpit-machines-237-1.el8.noarch
Steps :
1. Prepare an off vm
2. Click the vm name to enter the vm details page, click Run
It shows the running vm console directly after click Run in Step 2.
So verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (cockpit-appstream bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:1875