listening on ipv6 fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Medium
|
Pradeep Kumar Singh |
Bug Description
When specifying an ipv6 api_host in the [service:api] section (like ::1) I see the following in my logs:
2014-11-19 20:09:32.759 15401 ERROR designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
2014-11-19 20:09:32.759 15401 TRACE designate.
While this looks like a perfectly fine issue in greendns.py (see [1]), is it possible to change to something else? Other Openstack projects listen perfectly fine for IPv6.
I'm asuming this affects the others services as well, though I only verified/tested with api.
[1] https:/
Changed in designate: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in designate: | |
assignee: | nobody → pradeep kumar singh (pradeep-singh-u) |
tags: | added: low-hanging-fruit |
Changed in designate: | |
milestone: | liberty-2 → 1.0.0 |
I noticed Glance fixed the same issue a while back: https:/ /bugs.launchpad .net/glance/ +bug/1331885