-
Notifications
You must be signed in to change notification settings - Fork 725
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
Comments
Use it until travis-ci/travis-ci#8891 is fixed.
…image, r=aidanhs Temporarily use the old Travis image. Use it until travis-ci/travis-ci#8891 is fixed. (See also https://blog.travis-ci.com/2017-12-12-new-trusty-images-q4-launch) r? @aidanhs
The workaround |
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 |
I tried
but it doesn't make a difference. Loopback is still missing IPv6 address |
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. |
@aidanhs thanks! The job https://travis-ci.org/freeipa/freeipa/jobs/316348680 is running with sudo enabled and |
@aidanhs With
I'm still not getting |
Use it until travis-ci/travis-ci#8891 is fixed.
@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 @BanzaiMan all that aside, can we expect a fix for this anytime soon? |
You can try the following solution: #8361 (comment) |
Sorry for the delay. We are removing |
It's not a problem with |
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! |
Thanks @cotsog, this does work. |
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
Different solutions can be found in travis issue [1] [1] travis-ci/travis-ci#8891
Different solutions can be found in travis issue [1] [1] travis-ci/travis-ci#8891
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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
The text was updated successfully, but these errors were encountered: