@Serge, Hi, had a customer ping me about this bug, any updates? Here's his explanation:
You may recall our conversation around iSCSI connectivity for binding block volume with host in OpenStack. The host is Linux container and block volume is on EMC VMAX. The I/O path is over iSCSI. The environment is Ubuntu 14.04 LTS x64. Our observation and KB found from internet is also given.
- Regular attach volume works fine (iSCSI login occurs between compute node and array target). In this context, Compute node is a physical host
- When creating bootable volume, controller node needs to perform iSCSI login for instance to copy. We are seeing issues with this. In this case, Compute node is an LXC container.
- Same isciadm commands that fail within the container, run fine when running outside the container (on physical controller host)
Looks like,
There’s a iSCSI kernel bug with mounting a target within a container
The issue is with multiple namespaces it appears.
@Serge, Hi, had a customer ping me about this bug, any updates? Here's his explanation:
You may recall our conversation around iSCSI connectivity for binding block volume with host in OpenStack. The host is Linux container and block volume is on EMC VMAX. The I/O path is over iSCSI. The environment is Ubuntu 14.04 LTS x64. Our observation and KB found from internet is also given.
- Regular attach volume works fine (iSCSI login occurs between compute node and array target). In this context, Compute node is a physical host
- When creating bootable volume, controller node needs to perform iSCSI login for instance to copy. We are seeing issues with this. In this case, Compute node is an LXC container.
- Same isciadm commands that fail within the container, run fine when running outside the container (on physical controller host)
Looks like,
There’s a iSCSI kernel bug with mounting a target within a container
The issue is with multiple namespaces it appears.
KBs found: /github. com/lxc/ lxc/issues/ 177 /bugs.launchpad .net/ubuntu/ +source/ lxc/+bug/ 1226855 /groups. google. com/forum/ #!topic/ open-iscsi/ GhKfxIix4ds
https:/
https:/
https:/
Do we know whether this is fixed?