OpenStack Compute (Nova)

Nova API does not listen on IPv6

Reported by Kevin Mancuso on 2011-09-14
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Unassigned
python-eventlet (Ubuntu)
High
Dave Walker

Bug Description

Nova API service does not bind to IPv6 interfaces. When specifying v6 address using ec2_list or osapi_listen, it returns "gaierror: [Errno -9] Address family for hostname not supported"

Are you using an old incompatible version of eventlet?

This used to happen before this patch:

https://bitbucket.org/which_linden/eventlet/changeset/a8b259177024

On Sep 14, 2011, at 3:13 PM, Kevin Mancuso wrote:

> Public bug reported:
>
> Nova API service does not bind to IPv6 interfaces. When specifying v6
> address using ec2_list or osapi_listen, it returns "gaierror: [Errno -9]
> Address family for hostname not supported"
>
> ** Affects: nova
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Nova Bug
> Team, which is subscribed to OpenStack Compute (nova).
> https://bugs.launchpad.net/bugs/850443
>
> Title:
> Nova API does not listen on IPv6
>
> Status in OpenStack Compute (Nova):
> New
>
> Bug description:
> Nova API service does not bind to IPv6 interfaces. When specifying v6
> address using ec2_list or osapi_listen, it returns "gaierror: [Errno
> -9] Address family for hostname not supported"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/850443/+subscriptions

Kevin Mancuso (kremlinkev) wrote :

I am running the following: eventlet==0.9.17.dev

I have verified that the changes relavent to the patch listed is present in the version I have.

Kevin L. Mitchell (klmitch) wrote :

I encountered this same issue while working on another project: it turns out that eventlet monkey-patches getaddrinfo() and friends with a version that does not understand IPv6. I solved the issue in my case by writing my own resolver, since my project was eventually going to need one; but until eventlet catches up, any project that uses eventlet's (or monkey-patched standard library) name resolution routines will encounter problems trying to run on IPv6.

(For reference, the DNS library that eventlet actually uses fully understands IPv6, and that is in fact what I used inside my resolver…)

Kevin L. Mitchell (klmitch) wrote :

Reported as a critical enhancement to eventlet; link to issue:

    https://bitbucket.org/which_linden/eventlet/issue/105/name-resolution-needs-to-support-ipv6

Brian Waldon (bcwaldon) wrote :

So is this a bug we need to address in our codebase, or do we wait on eventlet?

Changed in nova:
status: New → Incomplete
Dave Walker (davewalker) wrote :

It does look like the upstream bug report is making progress.

Changed in python-eventlet (Ubuntu):
importance: Undecided → High
status: New → Triaged
Dave Walker (davewalker) on 2012-02-14
Changed in python-eventlet (Ubuntu):
assignee: nobody → Dave Walker (davewalker)
tags: added: rls-p-tracking
Tom Fifield (fifieldt) wrote :

This is still not fixed upstream.

Thierry Carrez (ttx) wrote :

Nothing to fix in Nova here... closing that subtask. Please set it back to New if you disagree.

Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers