"iscsiadm discovery" succeeds but "iscsiadm login" fails inside ubuntu container.

[abhijit taware]

Here is output of commands -

root@hytrust:~# iscsiadm -m discovery -t st -p 192.168.100.81
192.168.100.81:3260,1 iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server

root@hytrust:~# ps -ef | grep iscsi
root 398 1 0 13:58 ? 00:00:00 /usr/sbin/iscsid
root 1305 1 0 14:06 ? 00:00:00 /usr/sbin/iscsid
root 10744 1 0 16:15 ? 00:00:00 /usr/sbin/iscsid
root 12899 10720 0 16:43 pts/1 00:00:00 grep --color=auto iscsi

Now login fails -
root@hytrust:~# iscsiadm -m node --targetname "iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server" --portal "192.168.100.81:3260" --login
Logging in to iface: default, target: iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server, portal: 192.168.100.81,3260
iscsiadm: got read error (0/0), daemon died?
iscsiadm: Could not login to [iface: default, target: iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server, portal: 192.168.100.81,3260].
iscsiadm: initiator reported error (18 - could not communicate to iscsid)
iscsiadm: Could not log into all portals

Same thing work if I do it from a Virtual Machine.

I followed tutorial @ this link : http://www.heath-bar.com/blog/?p=184
It works perfect for virtual machines.
We need this working as we are trying replace VMs with containers due to hardware limitation for scalability testing.

[abhijit taware (abhijit-taware)]

related bug could be # 1226855

[Stéphane Graber (stgraber)]

I'm pretty sure we've completely disabled iscsid inside containers at this point due to its tight link to un-namespaced kernel features.

Some specific server use cases should be possible, but anything client related is unlikely to succeed without some major kernel work.