keystone ipv6 tests fail
Bug #1176204 reported by
Brant Knudson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Brant Knudson | ||
Folsom |
Invalid
|
Undecided
|
Unassigned | ||
Grizzly |
Fix Released
|
Undecided
|
Dolph Mathews |
Bug Description
Keystone unit tests failed when run on oneiric3 with an error that it couldn't resolve IPv6 addresses (::1).
http://
http://
The change under test wasn't related to IP changes.
For the test that fails, it's trying to start up Keystone listening on ::1 and it fails to resolve ::1.
I couldn't recreate this on my local system: ./run_tests.sh test_ipv6
summary: |
- keystone ipv6 fails on oneiric3 + keystone ipv6 tests fail |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in keystone: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
importance: | Undecided → Medium |
Changed in keystone: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
So I am not entirely convinced this is a problem with the Jenkins slaves. On oneiric3 which is where the python26 test failed `nc -l ::1 0` works fine. And looking in the eventlet source code I see that getaddrinfo (which is in the tracebacks provided by nose) does not support ipv6. https:/ /bitbucket. org/eventlet/ eventlet/ src/e0f578180d7 d82d2ed3d8a96d5 20103503c524ec/ eventlet/ support/ greendns. py?at=0. 12#cl-166
I am not sure yet why this just cropped up and why it does not fail on your local node. Maybe the test is optimistic? eg if ipv6 available then run the tests else skip. I haven't read the tests yet... I am going to add keystone to the bug for now while we sort out where the issue is.