Bug 1650501 - Number of disks for VMs on vSphere shows incorrect
Summary: Number of disks for VMs on vSphere shows incorrect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.11.0
Assignee: Milan Zázrivec
QA Contact: Nandini Chandra
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-16 10:53 UTC by Saurabh Heda
Modified: 2019-12-12 13:34 UTC (History)
14 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:34:23 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screen of VM summary page for a VM with floppy disk (69.63 KB, image/png)
2019-05-20 20:24 UTC, Nandini Chandra
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:34:38 UTC

Description Saurabh Heda 2018-11-16 10:53:46 UTC
Description of problem:
Number of disks for VMs on vSphere shows incorrect
We see a additional disk on VM as :

"sio 0:0			Unknown			0.0"

Version-Release number of selected component (if applicable):
5.10.0

How reproducible:
Create a new VM on vSphere and even though there are no additional disk connected to this VM, we see 2 disks.

Steps to Reproduce:
1. Create a new VM with only 1 VMDK attach to this VM
2. In the Datastore allocation summary, under Number of disks it shows value as 2 

Actual results:
We see a new disk as :
"sio 0:0			Unknown			0.0"

Expected results:
We should only see the VMDK details here and not other devices.

Comment 2 Aziza Karol 2018-11-16 15:16:29 UTC
Restoring back the priority and severity.

Comment 3 Aziza Karol 2018-11-16 15:18:23 UTC
Can you please check if this issue is reproducible?

Comment 5 Kedar Kulkarni 2018-11-16 18:48:54 UTC
As of 5.10.0.24, I tried adding/removing the hard disk, and it was showing up correctly in CFME.

Comment 6 Adam Grare 2018-12-03 18:14:07 UTC
I was able to reproduce what you are seeing.  The number of disks is correct, sio is the controller type for a floppy disk.

What you are seeing is the controller type and location are being printed in the table but not the device type.

E.g.:
#<Disk id: 32, device_name: "Floppy drive 1", device_type: "floppy", location: "0:0", filename: "", hardware_id: 19, mode: nil, controller_type: "sio", ...

It looks like the UI isn't displaying floppy devices correctly, hard disks and cd rom drives are fine however.

Sending back to the UI team since the backend DB is correct.

Comment 7 Milan Zázrivec 2018-12-04 15:58:32 UTC
Is there perhaps an appliance or a database showing this problem?

Thank you.

Comment 9 CFME Bot 2018-12-07 12:32:46 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master:

https://github.com/ManageIQ/manageiq-ui-classic/commit/114a26235518234e49dcb1e2dfd857f6f5752e36
commit 114a26235518234e49dcb1e2dfd857f6f5752e36
Author:     Milan Zazrivec <mzazrivec>
AuthorDate: Tue Dec  4 11:14:33 2018 -0500
Commit:     Milan Zazrivec <mzazrivec>
CommitDate: Tue Dec  4 11:14:33 2018 -0500

    Fix rendering of VMware floppy drive

    https://bugzilla.redhat.com/show_bug.cgi?id=1650501

 app/helpers/vm_helper.rb | 2 +
 1 file changed, 2 insertions(+)

Comment 11 Nandini Chandra 2019-05-20 20:23:40 UTC
Verified in 5.11.0.3

Comment 12 Nandini Chandra 2019-05-20 20:24:24 UTC
Created attachment 1571388 [details]
screen of VM summary page for a VM with floppy disk

Comment 14 errata-xmlrpc 2019-12-12 13:34:23 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, 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:4199


Note You need to log in before you can comment on or make changes to this bug.