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.
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) AF_NET
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
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
@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 device
@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
environm
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 impl
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 t
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
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 => C
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
AudioD
** Changed in: lxc (Ubuntu)
Importance: Undecided => Wishlist
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
To manage no
Aha! Attached: strace -f -o iscsi-start_f.txt service open-iscsi start
** Attachment added: "iscsi-start_f.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+attachment/3855848/+files/iscsi-start_f.txt
--
You received this bug notification because you are a member of Ubuntu
Ser
Thanks - unfortunately we need the -f flag added to strace to follow
forks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
To
Assuming I should use the init script for this, attached output from
running the following in the container:
strace -o iscsi-start.txt service open-iscsi start
** Attachment added: "iscsi-start.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+attachment/3855807/+files/iscsi-st
192.0.2.69 is the IP of the qemu VM that the LXC container is attempting
to provision.
I'll load up my test instance soon to get that additional strace.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launch
Thanks, that is an interesting strace. What is 192.0.2.69 - is that the
host? Could you also start the daemon in the container by hand under
strace for a few seconds so we can see exactly how fd 6 is created?
(Presumably it is a connection to iscsi_nl_sock, but I'm confused since
(a) it managed t
Thanks for your reply, I'll chat with Robert and Clint to see if any of
these solutions is reasonable for us.
As a reference point, here's the setup we're using:
Host has 2 VMs: An LXC and an qemu VM
The host has the iscsi_tcp module loaded, which then can be seen and
used for the iscsi daemon w
@Clint,
Thanks. Then I see three possible workarounds:
1. The simplest way would be to have iscsid running on the host, and
connect to it over tcp from the container.
2. You could also have a container without its own network namespace,
and have iscsid running there.
3. You could open the netl
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
To manage notifica
I can't answer all of the questions, but the basic idea is that an LXC
container could mount an iscsi target from inside the container with
very little if any cooperation from the host's user space.
I believe other similar systems like nbd use ioctl's to configure such
devices, but iscsi uses netl
Thanks for reporting this bug.
Your example command says '$ip:$port'. Is the iscsid running on the host
or in the container? Is $ip the ip of the host?
If $ip is the host ip and you just want iscsiadm in the guest to talk to iscsid
on the
host, that should work.
There are several ways dependi
22 matches
Mail list logo
