Bug 672885

Summary: yast2-iscsi-client drops authentication parameters.
Product: [openSUSE] openSUSE 11.3 Reporter: Eifren X <r469712>
Component: YaST2Assignee: Thomas Fehr <fehr>
Status: VERIFIED WONTFIX QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: hare
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Eifren X 2011-02-17 06:16:22 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13

In a configuration where multiple iscsi targets are defined as manual with CHAP authentication required, every time the yast2-iscsi client is used and you do not logon to every single entry the node.session.authmethod is changed to NONE and the node.session.auth.username/password entries are deleted. Even if you go into the filesystem and chmod 400 default to each parameter file, the yast2 process forces the files to rw and overwrites the file with the wrong/missing settings. 

Reproducible: Always

Steps to Reproduce:
1.Define multiple iscsi targets as manual and CHAP authentication with yast2
2.Restart the yast2 iscsi client and only logon to 1 of the targets
3.exit yast
3.Issue iscsiadm command to to logon to other iscsi target not used in step 2 above.
Actual Results:  
logon to iscsi target fails because the authmethod is change and username/password options are deleted.

Expected Results:  
Expected that the yast2 client would preserve all settings for iscsi targets and not force the user to reenter the security options for every iscsi definition every time the yast2 iscsi client is used.
Comment 1 Michael Calmer 2011-02-24 09:17:04 UTC 
Please provide the logfiles. Please attache an archive with the complete content of /var/log/.

Thanks.
Comment 2 Thomas Fehr 2011-03-14 10:56:45 UTC 
Hannes,

To be able to debug and fix this I would need a server with at least two nodes where CHAP authentication
is required. All the nodes on 10.11.136.70 and 10.11.136.71 seem not to need any authentication
at all. 

Please set up some nodes that need CHAP authentication and mail me authentication parameters,
so that I can reproduce and fix this.
Comment 3 Lukas Ocilka 2014-04-11 07:16:30 UTC 
No logs provided, too old product to reproduce.
No activity for ages, closing as WONTFIX.