Hide Forgot
Description of problem: When a VM is shut off, create a new disk, not using existing ones, the Used and Capacity columns of the newly created disk can't be shown until the Add Disk button is clicked again. Version-Release number of selected component (if applicable): cockpit-machines-184-1.el8.noarch libvirt-dbus-1.2.0-1.module+el8+2529+a9686a4d.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare a VM, and turn it into shut off status 2. Click "Add Disk" button on its Disks subtab 3. Select "Create New" option on the Add Disk dialogue window, and complete other fields, then click Add. 4. Wait for the Used and Capacity columns of the newly created disk to appear 5. Click "Add Disk" button again Actual results: 1. After step4, the Used and Capacity columns of the newly created disk don't appear. 2. After step5, the Used and Capacity columns of the newly created disk appear immediately. Expected results: 1. The Used and Capacity columns of the newly created disk could be shown right after the disk is created, not related to "Add Disk" button. Additional info:
https://github.com/cockpit-project/cockpit/pull/10874
Test Versions: cockpit-machines-193-1.el8.noarch libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64 Test Steps: 1. Prepare a VM, and turn it into shut off status 2. Click "Add Disk" button 3. Select "Create New" option on the Add Disk dialogue window, and complete other fields, then click Add. 4. Wait for the Used and Capacity columns of the newly created disk to appear Test Results: The Used and Capacity columns of a newly added disk to a shut off VM can be shown in a while after step 4. According to the results, The Used and Capacity columns of a newly added disk to a shut off VM can be shown in a while without clicking 'Add Disk' button.So 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, 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-2019:3325