Closing the LXC side of this bug as there's nothing we can really do here.
It's either a kernel issue (needs support for their socket option within a
network namespace) or an open-iscsi issue where they could have some kind of
fallback mechanism.
** Changed in: lxc (Ubuntu)
Status:
Adding Bootstack to watch this bug, as we are taking ownership of charm-
iscsi-connector which would be ideal to test within lxd confinement, but
requires VM or metal for functional tests.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Still seems to be a problem in 18.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
Status in linux package in
Is this still a problem on Ubuntu 18.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
Status in linux package in
Is there any progress on this issue? Is there a workaround to make open-
iscsi work inside LXC container?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot
Chris Leach started posted patches that would fix some of what is needed
to support this on open-iscsi mailing list
(https://groups.google.com/d/msg/open-iscsi/vWbi_LTMEeM/P8-oUDkb14YJ )
but they stalled and are incomplete (https://groups.google.com/d/msg
/open-iscsi/kgjck_GixsM/U_FqTbYhCgAJ ).
Quoting M.Morana (1226...@bugs.launchpad.net):
@Serge, Hi, had a customer ping me about this bug, any updates? Here's
his explanation:
Sorry, no, I have not spent any time on this. As far as I know neither
has anyone on the kernel team, and I haven't seen it discussed on any
mailing lists.
@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
@m.morana - to my knowledge modern kernel's still don't have a namespace
aware ISCSI netlink implementation. In an OpenStack context, I recall
seeing something about changing nova's volume attach code to use qemu's
native iSCSI support which may be a workaround for iscsiadm and native
block
This is a blocking issue for users of iscsi-based storage HW on
Openstack; is there any way of re-prioritizing this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Bump if anyone has time to work on this it would be a huge benefit to
the OpenStack community.
This is a blocking issue for us too as we're not able to fully use LXC
containers in our OpenStack deployments. Specifically we can not run
nova-compute in an lxc container due to issues with (RW)
Quoting Jason Harley (ja...@breqwatr.com):
I'm also curious about an update on this issue. I'm running 14.04.1,
Kernel 3.13.0-39-generic and LXC 1.0.6-0ubuntu0.1. 'strace' output of
open-scsi looks basically the same as above.
As I understand it, this is related to iSCSI's Netlink
I'm also curious about an update on this issue. I'm running 14.04.1,
Kernel 3.13.0-39-generic and LXC 1.0.6-0ubuntu0.1. 'strace' output of
open-scsi looks basically the same as above.
As I understand it, this is related to iSCSI's Netlink implementation
not being namespace aware? I would love
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jul 31 21:36 seq
crw-rw 1 root audio 116, 33 Jul 31 21:36 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
strace -f -o open-iscsi-start-lxc.txt service open-iscsi start
** Attachment added: strace -f service open-iscsi start
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+attachment/4167066/+files/open-iscsi-start-lxc.txt
** Changed in: linux (Ubuntu)
Status: Incomplete =
This is still an impacting issue, Curious if there has been any progress on it
on any front?
Being that apport information was requested I've provided it from my running
systems.
The apport information attached to this issue is from within the LXC container.
The host system is:
Ubuntu 14.04.01
16 matches
Mail list logo
