Bug 63599 – >26 scsi devices not handled correctly

Bug 63599 - >26 scsi devices not handled correctly

Summary:	>26 scsi devices not handled correctly

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Network
Classification:	Red Hat
Component:	RHN/Web Site (Show other bugs)
Sub Component:
Version:	RHN Stable
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bret McMillan
QA Contact:	Red Hat Satellite QA List
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-04-16 00:22 EDT by Need Real Name
Modified:	2007-04-18 12:42 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-04-09 15:03:05 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2002-04-16 00:22:26 EDT

Description of Problem:

The display of data on the web site for a machine with >26 scsi drives is not
correct.

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

Current web site code.

How Reproducible:

Every system that has >26 scsi drives exhibits this behavior.

Steps to Reproduce:
1. register a system with >26 scsi drives
2. pull up the hardware profile for that system on the rhn web site

Actual Results:

What should be sdaa is displayed as sd{

Expected Results:

The drive mapping/display code should match the actual device name (sdaa in this
case)


Additional Information:

Comment 1 Greg DeKoenigsberg 2002-12-18 01:55:17 EST

aja, got a profile (RHN systemid) that you can point us to that displays this
behavior?

Comment 2 Need Real Name 2003-04-09 15:03:05 EDT

It was 1000360470, but the drive data appears correct now.  I'm not certain when
the issue was corrected, though.

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