IPv6 test are not skipped when ipv6 is disabled
Bug #1263663 reported by
mouadino
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
mouadino |
Bug Description
A platform can still have ipv6 disable for example by doing "sudo sysctl -n net.ipv6.
I am proposing in this patch a better way to detect wether ipv6 is enabled or no in a machine.
description: | updated |
Changed in keystone: | |
status: | New → In Progress |
Changed in keystone: | |
importance: | Undecided → Medium |
Changed in keystone: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
A bit of context from other OpenStack project:
* Nova landed recently a change that fix this issue here: https:/ /review. openstack. org/#/c/ 38070/ and the changes is not good IMHO check below for why. tests/test_ wsgi.py, same thing that was added to nova.
* Cinder doesn't take in consideration host that support ipv6 instead it look wether host has an interface with ipv6 address, check class TestWSGIServer in cinder/
Which basically mean that both nova and cinder end up skipping tests when they shouldn't, the correct way to do this is to check whether we can bind a socket to ::1 if not the ipv6 is not supported, this is the same thing that cPython do: http:// hg.python. org/cpython/ file/eae6966d97 34/Lib/ test/support/ __init_ _.py#l613.
But at least both nova and cinder doesn't fail like keystone :)