introspectionSuite.SetUpTest unable to listen to socket

Bug #1607855 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Unassigned

Bug Description

As seen at
    http://reports.vapour.ws/releases/issue/579b8354749a563bfb200485

socket_test.go:68:
    c.Assert(err, jc.ErrorIsNil)
... value *errors.Err = &errors.Err{message:"unable to listen on unix socket", cause:(*net.OpError)(0xc82042ec30), previous:(*net.OpError)(0xc82042ec30), file:"github.com/juju/juju/worker/introspection/socket.go", line:55} ("unable to listen on unix socket: listen unix @introspection-test: bind: address already in use")
... error stack:
 listen unix @introspection-test: bind: address already in use
 github.com/juju/juju/worker/introspection/socket.go:55: unable to listen on unix socket

Curtis Hovey (sinzui)
tags: added: intermittent-failure
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta14 → 2.0-beta15
Changed in juju-core:
importance: High → Medium
milestone: 2.0-beta15 → 2.0.0
affects: juju-core → juju
Changed in juju:
milestone: 2.0.0 → none
milestone: none → 2.0.0
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue was seen several times a week, but has not been seen in the last 5 weeks. This might be fixed.

Changed in juju:
status: Triaged → Incomplete
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.0 → 2.0.1
Changed in juju:
milestone: 2.0.1 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Considering last occurrence was in late August, I agree - it looks like the issue has been fixed as part of the ongoing quality improvement effort.

Changed in juju:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.