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.
Created attachment 1280918[details]
Screenshot for step3.4
Description of problem:
Inaccurate information shows when reconnect to the same Floppy device
Version-Release number of selected component (if applicable):
libvirt-3.2.0-5.virtcov.el7.x86_64
virt-manager-1.4.1-4.el7.noarch
qemu-kvm-rhev-2.9.0-5.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a health guest then add a floppy device to it.
1.1 Launch virt-manager.
1.2 Double click one connection to active it.
1.3 Double click vm:beta-vnc, then turn to 'virtual machine hardware details' page.
1.4 Click 'Add Hardware' button, click 'Select or create custom storage', then input path "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd", set Device type: 'Floppy disk', click 'Apply'.
2. Disconnect to floppy image "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd".
2.1 Click Floppy 1.
2.2 Click Disconnect button at right area.
3. Reconnect to floppy image "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd" again
3.1 Click Floppy 1.
3.2 Click Connect button at right area
3.3 In put source image location "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd".
3.4 Click 'OK'
Actual results:
After step1.4, Floppy disk added to guest successfully.
After step2.2, Floppy disk source removed.
After step3.4, an error message pops up:
Disk "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd" is already in use by other guests ['beta-vnc']
Do you really want to use this disk?
If click 'No', back to 'Choose Media' page.
If click 'Yes', floppy disk will add to guest.
Expected results:
There is no inaccurate information shows when reconnect to the same Floppy device, for i have disconnect floppy device before i reconnect again.
Additional info:
I can reproduce this issue with package:
virt-manager-1.4.1-7.el7.noarch
virt-install-1.4.1-7.el7.noarch
virt-manager-common-1.4.1-7.el7.noarch
Then try to verify this bug with new build:
virt-manager-1.4.3-1.el7.noarch
virt-install-1.4.3-1.el7.noarch
virt-manager-common-1.4.3-1.el7.noarch
Steps:
1. Prepare a shutoff guest then add a floppy device to it.
1.1 Launch virt-manager.
1.2 Double click one connection to active it.
1.3 Double click vm:beta-vnc, then turn to 'virtual machine hardware details' page.
1.4 Click 'Add Hardware' button, click 'Select or create custom storage', then input path "/usr/share/virtio-win/virtio-win-1.9.3_amd64.vfd", set Device type: 'Floppy disk', click 'Apply'.
2. Disconnect to floppy image "/usr/share/virtio-win/virtio-win-1.9.3_amd64.vfd".
2.1 Click Floppy 1.
2.2 Click Disconnect button at right area.
3. Reconnect to floppy image "/usr/share/virtio-win/virtio-win-1.9.3_amd64.vfd" again
3.1 Click Floppy 1.
3.2 Click Connect button at right area
3.3 In put source image location "/usr/share/virtio-win/virtio-win-1.9.3_amd64.vfd".
3.4 Click 'OK'
Actual results:
After step1.4, Floppy disk added to guest successfully.
After step2.2, Floppy disk source removed.
After step3.4, The same Floppy disk added to guest successfully and no other infomation pops up.
So move this bug from ON_QA to VERIFIED, thanks.
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/RHEA-2018:0726
Created attachment 1280918 [details] Screenshot for step3.4 Description of problem: Inaccurate information shows when reconnect to the same Floppy device Version-Release number of selected component (if applicable): libvirt-3.2.0-5.virtcov.el7.x86_64 virt-manager-1.4.1-4.el7.noarch qemu-kvm-rhev-2.9.0-5.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare a health guest then add a floppy device to it. 1.1 Launch virt-manager. 1.2 Double click one connection to active it. 1.3 Double click vm:beta-vnc, then turn to 'virtual machine hardware details' page. 1.4 Click 'Add Hardware' button, click 'Select or create custom storage', then input path "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd", set Device type: 'Floppy disk', click 'Apply'. 2. Disconnect to floppy image "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd". 2.1 Click Floppy 1. 2.2 Click Disconnect button at right area. 3. Reconnect to floppy image "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd" again 3.1 Click Floppy 1. 3.2 Click Connect button at right area 3.3 In put source image location "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd". 3.4 Click 'OK' Actual results: After step1.4, Floppy disk added to guest successfully. After step2.2, Floppy disk source removed. After step3.4, an error message pops up: Disk "/usr/share/virtio-win/virtio-win-1.9.0_amd64.vfd" is already in use by other guests ['beta-vnc'] Do you really want to use this disk? If click 'No', back to 'Choose Media' page. If click 'Yes', floppy disk will add to guest. Expected results: There is no inaccurate information shows when reconnect to the same Floppy device, for i have disconnect floppy device before i reconnect again. Additional info: