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.
Bug 1912384 - [machines] The VM detail page will turn white if deleting a VM in a environment which is without storage pools
Summary: [machines] The VM detail page will turn white if deleting a VM in a environme...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.4
Assignee: Simon Kobyda
QA Contact: YunmingYang
URL:
Whiteboard:
: 1918103 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-04 10:38 UTC by YunmingYang
Modified: 2021-05-18 15:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:53:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
a gif for step 3 and step 4. Hope it is helpful (178.60 KB, image/gif)
2021-01-06 01:22 UTC, YunmingYang 		no flags Details
View All

Description YunmingYang 2021-01-04 10:38:02 UTC 
Description of problem:
In a environment without storage pools, create a VM by "virsh define $xml_path && virsh start $vm_name", then go to the detail page of the VM, and delete it with checking disks, there will be an error, which is "no storage vol with matching path $disk_path". Then, uncheck disks, and re-click the "Delete" button, the VM detail page will turn white

Version-Release number of selected components (if applicable):
cockpit-machines-234-1.el8.noarch
cockpit-234-1.el8.x86_64
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64

How reproducible:
100%

Steps to Reproduce:
1 Prepare an environment which has no storage pool
2 Create a VM by "virsh define $xml_path && virsh start $vm_name"
3 Go to the VM detail page, then delete it with checking disks
4 Delete the VM without checking disks

Actual results:
1 After step 3, there will be an error, which is "no storage vol with matching path $disk_path".
2 After step 4, the VM detail page turns white

Expected results: 
1 The VM can be deleted without error after step 3.
2 The VM can be deleted, and redirected to the VM list page after step 4.

Additional info:
Comment 1 Simon Kobyda 2021-01-05 13:16:39 UTC 
I cannot reproduce step 4. After step 4, do you get redirected to the page [HOSTNAME]:9090/machines or do you stay in page [HOSTNAME]:9090/machines#vm?name=[VM_NAME]&connection=[CONNECTION] ? 
Also is there any warning in browser's developer console after step 4?
Comment 2 YunmingYang 2021-01-05 23:42:23 UTC 
Hi simon, after step 4, I stayed in page [HOSTNAME]:9090/machines#vm?name=[VM_NAME]&connection=[CONNECTION].I think I miss one point. It is that I didn't close the dialog whose name is "Confirm deletion of $vm_name" after step 3, I just unchecked the disks and re-clicked the "Delete" button on the "Confirm deletion of $vm_name" dialog.
Comment 3 Simon Kobyda 2021-01-05 23:56:27 UTC 
There is a part of code which redirects you to a VM list page after successful deletion of a VM. When I reproduce your step 4 and delete the VM without deleting the disks, I get redirected to vm list page. I wonder what's different for me and you. Was the deletion a VM successful for you? Was there no warning in developer console? What browser are you using?
Comment 4 YunmingYang 2021-01-06 01:20:37 UTC 
I checked the developer console, there is an error which seems new, it is "Tried changing state of a disconnected RFB object".And the deletion in step 3 is not successful, it just change the VM status to "shut off". The deletion in step 4 is successful, I checked it by "virsh list --all". My browser is "Chrome 87.0.4280.88".
Comment 5 YunmingYang 2021-01-06 01:22:35 UTC 
Created attachment 1744740 [details]
a gif for step 3 and step 4. Hope it is helpful
Comment 6 Martin Pitt 2021-01-07 05:58:04 UTC 
Simon is working on a fix in https://github.com/cockpit-project/cockpit/pull/15102
Comment 7 Martin Pitt 2021-01-20 04:31:39 UTC 
*** Bug 1918103 has been marked as a duplicate of this bug. ***
Comment 11 YunmingYang 2021-02-07 07:09:19 UTC 
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 Prepare an environment which has no storage pool
2 Create a VM by "virsh define $xml_path && virsh start $vm_name"
3 Go to the VM detail page, then delete it with checking disks
4 Repeat step 2 to step 3,then delete the VM withouting checking disks

Test Results:
1 After step 3, the VM can be deleted without error, and then redirect to VM list page.
2 After step 4, the VM can be deleted without error, and then redirected to the VM list page.

According to the results, move the status to VERIFIED.
Comment 13 errata-xmlrpc 2021-05-18 15:53:11 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.