error: Failed to connect to 2001:4800:7813:516:3bc3:d7f6:ff04:aacb: Network is unreachable while accessing

Bug #1266616 reported by Clint Byrum
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Revision history for this message
Florent Flament (florentflament) wrote :

Same issue there:
2014-01-23 14:20:21.164 | fatal: unable to connect to
2014-01-23 14:20:21.164 |[0: 2001:4800:7813:516:3bc3:d7f6:ff04:aacb]: errno=Network is unreachable

Revision history for this message
Jeremy Stanley (fungi) wrote :

I've added to help us collect some more details the next time this happens. My best guess is some other tenant in that same flat network has a rogue IPv6 router advertisement daemon running.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to elastic-recheck (master)

Related fix proposed to branch: master

Revision history for this message
Jeremy Stanley (fungi) wrote :

Grabbing this one since I want to see if we're still getting any similar incidents now that we've added more diagnostics so as to hopefully be able to identify the source.

tags: added: gate-failure
Changed in openstack-ci:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Jeremy Stanley (fungi)
milestone: none → icehouse
Revision history for this message
Clark Boylan (cboylan) wrote :

Is this possibly a git bug? The host didn't appear to have an ipv6 interface but git decided to talk ipv6 anyways. Should we consider a A record that slaves can talk to instead of the git.o.o name which has a AAAA record?

Revision history for this message
Jeremy Stanley (fungi) wrote :

This hasn't happened in two weeks according to elastic-recheck (and much longer than that from what I know), so I think it's safe to not care about tracking this for now.

Changed in openstack-ci:
status: In Progress → Incomplete
importance: High → Undecided
assignee: Jeremy Stanley (fungi) → nobody
milestone: icehouse → none
Revision history for this message
Besmir Zanaj (besmirzanaj-gmail) wrote :

I recreated the by downloading the devstack repository in another folder other than "/opt/stack".
When I ran ./ from "devstack" folder in /opt/stack then the error was not present anymore

Changed in devstack:
assignee: nobody → Besmir Zanaj (besmirzanaj-gmail)
assignee: Besmir Zanaj (besmirzanaj-gmail) → nobody
status: New → Opinion
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers