Bug 148882 - "Error Cannot read current settings" when running ISCSI Client from YAST2.
Summary: "Error Cannot read current settings" when running ISCSI Client from YAST2.
Status: VERIFIED FIXED
: 150194 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Beta 3
Hardware: i386 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-07 22:10 UTC by Stewart Peatross
Modified: 2006-02-27 23:59 UTC (History)
1 user (show)

See Also:
Found By: System Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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

Note You need to log in before you can comment on or make changes to this bug.
Description Stewart Peatross 2006-02-07 22:10:00 UTC 
Problem: I'm unable to open the ISCSI Client configuration from YAST2 without receiveing the above error message soon after clicking on "ISCSI Client".  The error occurs at the "Read the previous settings process".  

To duplicate this install ISCSI Server and ISCSI Client configuration packages, load YAST2 select Micellaneous then click on ISCSI Client.
Comment 1 Stewart Peatross 2006-02-07 22:22:51 UTC 
I have 2 ISCSI files located in /etc/ they are iscsi.conf and initiatorname.iscsi.  Both files are default installed files they have not been modified in any way.  The contents of initiatorname.iscsi are:

InitiatorName=iqn.2006.02.de.suse:01.54f58b663b890.
Comment 2 Stewart Peatross 2006-02-07 22:30:02 UTC 
If I start the Open-iscsi service then I'm able to load the iscsi client configuration in Yast2.  If having the open-iscsi service loaded is a prerequisite for starting the iscsi client configuration then the error message needs to be changed to reflect that.
Comment 3 Stewart Peatross 2006-02-07 22:32:56 UTC 
Correction the file in /etc/ is iscsid.conf not iscsi.conf
Comment 4 Michal Zugec 2006-02-09 10:05:35 UTC 
fixed
Comment 5 Michael Gross 2006-02-13 11:56:10 UTC 
*** Bug 150194 has been marked as a duplicate of this bug. ***
Comment 6 Stewart Peatross 2006-02-27 23:59:26 UTC 
Works in Beta 5