This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1307829
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1307829
Title:
network namespace error
Status in “iproute” package in Ubuntu:
New
Status in “lxc” package in Ubuntu:
Confirmed
Bug description:
Hello,
I am using latest stables lxc build from
http://ppa.launchpad.net/ubuntu-lxc/stable/ubuntu on a OpenStack controller to
run containers. The OpenStack is also using network namespaces . When I boot
the server without auto start the containers everything looks fine with the
OpenStack network namespaces. If I boot lxc container with lxc-start the
container starts and its networking is functioning, but network namespaces
created before that , by OpenStack installation for example , become unusable
with he following error:
root@osctrl3dc02:~# ip netns exec vips ip a
seting the network namespace failed: Invalid argument
Here is the strace:
open("/var/run/netns/vips", O_RDONLY) = 4
syscall_308(0x4, 0x40000000, 0x7fffc4d54e83, 0x7fffc4d54bf0, 0x430af0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0) = -1 (errno 22)
As far as I know sys call_308 should set the namespace , but it seems
it fails on accessing the /var/run/netns/vips
It is strange that the permissions are altered:
root@osctrl3dc02:~# ls -alh /var/run/netns/vips
---------- 1 root root 0 Apr 14 08:48 /var/run/netns/vips
This file have the following permission before I start the container
-r--r--r-- 1 root root 0 Apr 12 14:01 /var/run/netns/vips
If I destroy the vips namespace and create it again , keeping the lxc
containers running, everything is back to normal, both containers and
Openstack networking are working.
Best regards,
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: iproute 20111117-1ubuntu2.1
ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Tue Apr 15 00:30:18 2014
InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release
amd64 (20140204)
MarkForUpload: True
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: iproute
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/1307829/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
