Bug 693132 - DASD range for SCSI only not described in help
Summary: DASD range for SCSI only not described in help
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: s390x
OS: All
medium
medium
Target Milestone: rc
: ---
Assignee: David Cantrell
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 707040
Blocks: 684953 705163
TreeView+ depends on / blocked
 
Reported: 2011-04-02 21:51 UTC by IBM Bug Proxy
Modified: 2018-11-14 15:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 707040 (view as bug list)
Environment:
Last Closed: 2011-09-15 19:16:46 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 65019 0 None None None Never

Description IBM Bug Proxy 2011-04-02 21:51:02 UTC
Description of problem:

During the initial installation phase the help text for question concerning DASD range does not 
describe what needs to be done for a SCSI only installation.

if help is provided in case of SCSI installation it is very useful for user.

1-Server architecture(s) -Z.
2. Server type -s390x
3.No there is not any  Other components involved (ixgbe/java/emulex/etc.).
4.This  server have no the latest GA firmware.
5. Has the problem been shown to occur on more than one system?yes
6. "sosreport" -not required for this bug because this bug is documentation error.
7. RHEL6.0 snap7 latest official distro  which this bug has been seen 
8-Steps to Reproduce:
  1.In initial installation phase.
  2.In DASD information just ask the question for help
  
  Log:-
   DASD range (e.g. 200-203,205 or ? for help). Default is autoprobing:


------- Comment #13503703 from balkov at 2010/12/15 13:30:09 EST -------
Will submit for RHEL 6.1 documentation

------- Comment from Alkov, Benjamin at 2011-01-19T17:16:36Z -------
IBM;
How would you like to see this text changed?

At present, linuxrc offers following choice for DASD information -
DASD range (e.g. 200-203,205 or ? for help). Default is autoprobing:  

Here if User presses ? for help , it shows 
Help text for DASD range:                                                     
 Comma separated list of ranges of device bus IDs.                            
 Default is autoprobing (not recommended).                                    
 Examples would be: 200-203 or 200,201,202,203 or 0.0.0200-0.0.0203,0.0.0205  


In the Help text it would be useful to add one more line in the end like -

Enter "none" for SCSI only installation.

This will give user a clue that if he is going to install only on SCSI then he
should enter text "none" When liuxrc asks for DASD range.

Comment 4 David Cantrell 2011-05-23 19:50:01 UTC
New and extended product functionality as well as new features for this component must be implemented by IBM and accepted upstream before consideration for a RHEL backport can be made.  For your convenience, this bug has been cloned to the same component under Fedora, which serves as the upstream development area for RHEL.

Comment 5 RHEL Program Management 2011-05-23 19:54:59 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 6 Georg Markgraf 2011-06-08 10:18:17 UTC
Appeal this decision -> re-open this request

Comment 7 David Cantrell 2011-06-08 15:23:07 UTC
See comment #4.  Bug #707040 exists to track the upstream contributions for this feature request.

Comment 8 Georg Markgraf 2011-06-10 15:05:58 UTC
The Installer is the value-added code from Red Hat.
  - Red Hat have to maintain this differentiator for RHEL
  - System z cannot take ownership for the installer
For sure System z will offer help like in the past. 

If you want to track this via Fedora - fine but that makes no difference 

Although its obvious I re-call
  - it is very important that the installer get improved for our customers

Comment 9 John Jarvis 2011-09-15 19:16:46 UTC
Closing as NOTABUG.  This feature needs to be implemented in Fedora before it
will be consider for RHEL inclusion.


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