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:
Install a VM with an ISO file, and use vnc console to follow the installation.The vnc console will jam after some operations.
Version-Release number of selected component (if applicable):
cockpit-machines-197.2-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create a VM with an ISO file(such as fedora*.iso), then install it
2. Use the vnc console to follow the installation
Actual results:
1. The vnc console will jam after some operations
Expected results:
1. The vnc console can run properly
Additional info:
The vnc console can continue to run if switch to the other type console and switch back
Yunming I am not sure what you mean by jam. The design of the VMs page has drastically changed since 197,specically in Cockpit 231 with https://github.com/cockpit-project/cockpit/pull/14346.
I am suspecting that in the new design the issue you describe does not exist.
The issue means that the progress bar in the installation dialog get stuck. And in the past version, it will be recovered if we switched to another tab and switched back. For now, I try several times in cockpit-machines-235, the issue seems to disappear.
Pre-verified Versions:
cockpit-machines-236-1.el8.noarch
cockpit-236-1.el8.x86_64
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64
Pre-verified Steps:
1. Create a VM with an ISO file(fedora 31), then install it
2. Use the vnc console to follow the installation
Pre-verified Results:
The vnc console can run correctly.
According to the results, change ‘Verified’ status to ‘TESTED’.
Test Versions:
cockpit-machines-237-1.el8.noarch
cockpit-236-1.el8.x86_64
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64
Test Steps:
1. Create a VM with an ISO file(fedora 31), then install it
2. Use the vnc console to follow the installation
Test Results:
The vnc console can run correctly.
According to the results, move the status to 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