Bug 741838 - Serial number is not complete on disk select page
Summary: Serial number is not complete on disk select page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-28 05:18 UTC by Guohua Ouyang
Modified: 2011-12-06 19:28 UTC (History)
7 users (show)

Fixed In Version: ovirt-node-2.0.2-0.9.git9048c81.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 19:28:33 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1783 0 normal SHIPPED_LIVE rhev-hypervisor6 bug fix and enhancement update 2011-12-06 15:10:54 UTC

Description Guohua Ouyang 2011-09-28 05:18:43 UTC
Description of problem:
on disk select page, the detail serial number isn't complete, it seems the first character is not there.


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

How reproducible:
Always.

Steps to reproduce:
1.  install rhev-h-6.2-0.17.2

Actual results:
the detail serial number display "6090a038d0f7b10e4de4d456d0003037".

Expected results:
It should display "36090a038d0f7b10e4de4d456d0003037" in this machine.

Comment 2 Joey Boggs 2011-09-28 12:51:03 UTC
This is data we pull from gudev, so it's not outputting correctly, will investigate this further


import gudev
client = gudev.Client(['block'])
for device in client.query_by_subsystem("block"):
    dev_name = device.get_property("DEVNAME")
    dev_serial = device.get_property("ID_SERIAL_SHORT")
    if "sd" in dev_name:
        print dev_name
        print dev_serial


/dev/sdc
50060160c460219850060160c4602198
/dev/sdd
50060160c460219850060160c4602198
/dev/sda
600c0ff000d7955714c86c4d01000000
/dev/sdb
600c0ff000d7a2a5f976bc4a01000000
/dev/sdb1
600c0ff000d7a2a5f976bc4a01000000
/dev/sdb2
600c0ff000d7a2a5f976bc4a01000000
/dev/sdb3
600c0ff000d7a2a5f976bc4a01000000
/dev/sdg
50060160c460219850060160c4602198
/dev/sdh
50060160c460219850060160c4602198
/dev/sde
600c0ff000d7a2a5f976bc4a01000000
/dev/sde1
600c0ff000d7a2a5f976bc4a01000000
/dev/sde2
600c0ff000d7a2a5f976bc4a01000000
/dev/sde3
600c0ff000d7a2a5f976bc4a01000000
/dev/sdf
600c0ff000d7955714c86c4d01000000

Comment 3 Alan Pevec 2011-09-28 15:36:46 UTC
Leading "3" is coming from scsi_id, which was supposed to be source for udevdb

From scsi_id(8):
       Identifiers  based  on page 0x80 are prefixed by the character ’S’, the
       SCSI vendor, the SCSI product (model) and then the  the  serial  number
       returned by page 0x80. For example:

       # /lib/udev/scsi_id --page=0x80 --whitelisted --device=/dev/sda
       SIBM     3542           1T05078453

       Identifiers based on page 0x83 are prefixed by the identifier type fol-
       lowed by the page 0x83 identifier. For example, a  device  with  a  NAA
       (Name  Address  Authority)  type  of 3 (also in this case the page 0x83
       identifier starts with the NAA value of 6):

       # /lib/udev/scsi_id --page=0x83 --whitelisted --device=/dev/sda
       3600a0b80000b174b000000d63efc5c8c

Not sure how is ID_SERIAL_SHORT generated, but looking at udevdb I think ID_SCSI_COMPAT seems to be full wwid.

Comment 6 Guohua Ouyang 2011-10-09 05:17:06 UTC
verified on 6.2-20111006 build, th serial number display completely.

Comment 7 errata-xmlrpc 2011-12-06 19:28:33 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


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