lxc python api test failed on KVM hosts #2
Comments
|
On Tue, Apr 17, 2018, 08:47 P.-H. Lin ***@***.***> wrote:
With a KVM node running with the Xenial KVM kernel (4.4.0-1021-kvm), the
python API test in lxc test will failed with interface assertion:
assert(set(container.get_interfaces()) == set(('lo', 'eth0')))
The actual container.get_interfaces() output on this instance is:
('eth0', 'lo', 'sit0')
The extra sit0 cause the problem here.
BugLink: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1764618
Is there anything actionable for LXC itself? Doesn't look like there is.
… |
|
Now an additional interface tunl0 appears inside the container as well when kernel module ipip is inserted in the host side. I think we should include such checks in the |
vicamo
added a commit
to vicamo/python3-lxc
that referenced
this issue
Sep 18, 2019
When the host has kernel module sit or ipip inserted, additional network interfaces sit0 and/or tunl0 would appear inside the container by default as well, which fails the api_test. This change append sit0/tunl0 to expected interfaces when applicable. Closes: lxc#2 Signed-off-by: You-Sheng Yang <vicamo@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With a KVM node running with the Xenial KVM kernel (4.4.0-1021-kvm), the python API test in lxc test will failed with interface assertion:
The actual container.get_interfaces() output on this instance is:
The extra sit0 cause the problem here.
BugLink: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1764618
The text was updated successfully, but these errors were encountered: