Bug 714906

Summary: cciss bus_type disk size always display as zero in ovirt-node
Product: Red Hat Enterprise Linux 6 Reporter: Mohua Li <moli>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: apevec, cshao, gouyang, leiwang, moli, ovirt-maint, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.0.2-0.6.gitcc6ba8c.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 19:16:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 595692    
Bug Blocks:    
Attachments:
Description Flags
screenshot
none
rhevh 6.2-0.12 none

Description Mohua Li 2011-06-21 09:36:22 UTC 
Description of problem:
cciss bus_type disk size always display as zero in ovirt-node, but just display issue, could installed and boot succeed,

fdisk -l&  multipath -ll could display the correct size


Version-Release number of selected component (if applicable):
rhev-hypervisor 6.2-0.2

How reproducible:
always

Steps to Reproduce:
1.boot to ovirt-node with "install" keyword
2.choose the cciss disk, which display as /dev/cciss/c0d0
3.
  
Actual results:
disk size display as 0, but fdisk -l & multipath -ll could display the correct size, 

Expected results:


Additional info:
Comment 1 Mohua Li 2011-06-21 09:39:35 UTC 
Created attachment 505784 [details]
screenshot
Comment 7 Mohua Li 2011-08-12 05:42:33 UTC 
Created attachment 517953 [details]
rhevh 6.2-0.12
Comment 18 errata-xmlrpc 2011-12-06 19:16:31 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.

http://rhn.redhat.com/errata/RHBA-2011-1783.html