https://bugzilla.novell.com/show_bug.cgi?id=751671 https://bugzilla.novell.com/show_bug.cgi?id=751671#c6 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #6 from Thomas Fehr <fehr@suse.com> 2012-04-11 09:24:15 UTC --- Is your decision if I should work on tghis bug or not. General rule is: No work on nontrivial YaST bugs without y2log. Nevertheless I can give some general hints, maybe these help. Otherwise you are on your own. Of course I tried already to reproduce. When I start "yast2 iscsi-client" on a standard 12.1 system where it was never used before. I get a popup that requests to install the open-iscsi package. After I said yes there, open-iscsi and some dependent packages were installed and rest of startup was fine. After I changed to the tab named "Discovered Targets" and pressed button labeled "Discovery" the pane filled with targets exported by iscsi-server. So in your case there may be either installation of open-iscsi package have been failed. YaST2 simply calls /sbin/iscsiadm (it is part of open-iscsi package) which handles the iscsi stuff on the client. So you can simply look into the y2log yourself, the executed commands are logged, also output of these commands. The command to discover targets exported by iscsi server is the following: iscsiadm -m discovery -P 1 -t st -I default -p <ipaddr_if_iscsi_server>:3260 You can simply use iscsiadm on the command line and see what happens. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.