Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trusty update is missing IPv6 addresses (no ::1 on localhost) #8891

Open
tiran opened this issue Dec 12, 2017 · 30 comments
Open

Trusty update is missing IPv6 addresses (no ::1 on localhost) #8891

tiran opened this issue Dec 12, 2017 · 30 comments

Comments

@tiran
Copy link

tiran commented Dec 12, 2017

The latest image is missing IPv6 addresses. The Kernel seems to have IPv6 enabled by no IPv6 addresses are configured. This breaks FreeIPA's test suite as we require IPv6 for some services. group: deprecated-2017Q4 fixes the problem.

In freeipa/freeipa#1391 and freeipa/freeipa#1392 we tried to set up IPv6. But the service does not have permission to modify the network stack. See https://travis-ci.org/freeipa/freeipa/jobs/315525816

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1460 qdisc mq state UP group default qlen 1000
    link/ether 42:01:0a:14:00:6b brd ff:ff:ff:ff:ff:ff
    inet 10.20.0.107/32 brd 10.20.0.107 scope global eth0
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:5d:b5:df:61 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever

$ ip addr show lo | grep -q inet6 || sudo ip addr add ::1/128 dev lo
RTNETLINK answers: Permission denied


The command "ip addr show lo | grep -q inet6 || sudo ip addr add ::1/128 dev lo" failed and exited with 2 during .
@tiran
Copy link
Author

tiran commented Dec 13, 2017

The workaround group: deprecated-2017Q4 is no longer working for us. Even images from the deprecated group are lacking IPv6 support, e.g. https://travis-ci.org/freeipa/freeipa/jobs/315776280

@aidanhs
Copy link

aidanhs commented Dec 13, 2017

Looking at that build config you're using sudo-disabled builds, apparently you need to enable sudo - https://blog.travis-ci.com/2017-12-12-new-trusty-images-q4-launch

@tiran
Copy link
Author

tiran commented Dec 13, 2017

I tried

sudo: required
dist: trusty
group: deprecated-2017Q4

but it doesn't make a difference. Loopback is still missing IPv6 address ::1. The Kernel has IPv6 support enabled, /proc/net/if_inet6 is present but empty.

@tiran tiran changed the title Latest image is missing IPv6 addresses (no ::1 on localhost) Trusty update is missing IPv6 addresses (no ::1 on localhost) Dec 13, 2017
@BanzaiMan BanzaiMan added the IPv6 label Dec 13, 2017
@aidanhs
Copy link

aidanhs commented Dec 14, 2017

Do you have a log for where you tried that (the one pasted doesn't have sudo enabled)? I'm just wondering because this did seem to fix it for the rust project.

@tiran
Copy link
Author

tiran commented Dec 14, 2017

@aidanhs thanks!

The job https://travis-ci.org/freeipa/freeipa/jobs/316348680 is running with sudo enabled and group: deprecated-2017Q4. As you can see in the before_install steps, IPv6 is enabled in the kernel (if_inet6 is present) but there is no IPv6 addressed assigned to any interface. You are running with language: shell, we are using language: python. I'll try that next.

@tiran
Copy link
Author

tiran commented Dec 14, 2017

@aidanhs With

language: shell
sudo: required
dist: trusty
group: deprecated-2017Q4

I'm still not getting ::1 or any other IPv6 address.

steveklabnik pushed a commit to steveklabnik/rust that referenced this issue Dec 14, 2017
@zuercher
Copy link

@tiran for comparison, I added your before install commands to our build (https://travis-ci.org/envoyproxy/envoy/builds/316643185). The output matches -- seemingly showing no ipv6 network. However, our ipv6-based tests definitely pass with group: deprecated-2017Q4 set where they do not without it. We only use the loopback address for ipv6 testing, but perhaps that works inside the docker container, but not on the worker that launches the container?

@BanzaiMan all that aside, can we expect a fix for this anytime soon?

@GiedriusM
Copy link

You can try the following solution: #8361 (comment)

@BanzaiMan
Copy link
Contributor

Sorry for the delay. We are removing localhost from ::1 aliases. See travis-ci/travis-build#1253 (and #8780).

@zuercher
Copy link

zuercher commented Dec 18, 2017

It's not a problem with localhost resolving to ::1. The problem is that ipv6 is disabled completely and we are running tests to explicitly test ipv6-related code.

@cotsog
Copy link

cotsog commented Dec 21, 2017

If you are running your tests in a Docker container, the following will enable back IPv6 support for Docker on Travis CI:

before_install:
  - echo '{"ipv6":true,"fixed-cidr-v6":"2001:db8:1::/64"}' | sudo tee /etc/docker/daemon.json
  - sudo service docker restart

Could you try this out and report back the result?

Thanks!

@kennytm
Copy link

kennytm commented Dec 21, 2017

Thanks @cotsog, this does work.

vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 1, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 1, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 1, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 1, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 1, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 1, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 2, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 2, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 3, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
vjuranek added a commit to vjuranek/ovirt-imageio that referenced this issue Jun 4, 2020
IPv6 tests fail on Travis as IPv6 is not available on any Travis VM [1].
However, when running tests in Docker, it can work if docker config is
adjusted. Fix is taken from [2].

[1] https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system
[2] travis-ci/travis-ci#8891 (comment)

Change-Id: I33bfec4ae8e0201ddbff2e348f6c446bfa5c2d23
Signed-off-by: Vojtech Juranek <vjuranek@redhat.com>
shramov added a commit to shramov/tll that referenced this issue Jun 12, 2020
Different solutions can be found in travis issue [1]

[1] travis-ci/travis-ci#8891
shramov added a commit to shramov/tll that referenced this issue Jun 12, 2020
Different solutions can be found in travis issue [1]

[1] travis-ci/travis-ci#8891
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 21, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 22, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 22, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
almusil added a commit to almusil/nmstate that referenced this issue Jul 22, 2020
Currently the travis IPv6 support is broken and suggestion
around this problem is stated in [0]. To enable it inside
of container we need to use a workaround.

[0] travis-ci/travis-ci#8891

Signed-off-by: Ales Musil <amusil@redhat.com>
gerrit-ovirt-org pushed a commit to oVirt/vdsm that referenced this issue Jul 22, 2020
Container that runs on Travis has disabled ipv6 [0].
A workaround to enable it is to write into sysctl
before start of any test.

This is helpful for nmstate because they are using
Travis as their CI and run functional tests regularly.

[0] travis-ci/travis-ci#8891

Change-Id: I74f206884f2b833cb85196ec303c43d0282fe1ff
Signed-off-by: Ales Musil <amusil@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests