Comment 2 for bug 1707626

it would appear that there is something wrong with starting the apiserver

OG] 0:09.978 INFO juju.worker stopped "apiserver", err: listen tcp :41534:
bind: address already in use
 [LOG] 0:09.978 DEBUG juju.worker "apiserver" done: listen tcp :41534:
bind: address already in use
[LOG] 0:09.978 ERROR juju.worker exited "apiserver": listen tcp :41534:
bind: address already in use
 [LOG] 0:09.978 INFO juju.worker restarting "apiserver" in 3s
introspection_test.go:137:

The failure is that the string "juju_apirequests_total" is not showing up,
but presumably that's because the apiserver is not starting and collecting
those metrics.

bind failures sounds like some other test didn't finish cleaning up before
this test ran. I thought we bind with SO_REUSEADDR in the test suite so we
can have fast bind and rebind. Then again we should probably be using a
random address so maybe something else is wrong.

John
=:->

On Sep 7, 2017 03:35, "Anastasia" <email address hidden> wrote:

> Reports have been moved. New link is http://ci.jujucharms.com/job
> /github-check-merge-juju/1868/artifact/artifacts/xenial.log
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1707626
>
> Title:
> TestPrometheusMetrics failure
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1707626/+subscriptions
>