We are not specifying controller at the commandline, and it is failing
to use the default. This is atypical-- we are usually explicit about
the controller, so it doesn't matter what the default is. I suspect if
we fix the test to be explicit about the controller, we will no longer
be affected by the bug in register.
On 2016-08-17 12:28 PM, Nicholas Skaggs wrote:
> This behavior has started between commit
> 2f3dc472edc8825d0fdd5cf8683432c3820e5f99 and
> c143850d69db1fccf7cd5dc3ecb6ab80739dbd61.
>
> I suspect the c143850d69db1fccf7cd5dc3ecb6ab80739dbd61 commit is the
> cause of the issue. Either the test itself is using a model connection
> (and thus this fails?), or something is wrong within juju-core itself.
>
We are not specifying controller at the commandline, and it is failing
to use the default. This is atypical-- we are usually explicit about
the controller, so it doesn't matter what the default is. I suspect if
we fix the test to be explicit about the controller, we will no longer
be affected by the bug in register.
On 2016-08-17 12:28 PM, Nicholas Skaggs wrote: d0fdd5cf8683432 c3820e5f99 and cf7cd5dc3ecb6ab 80739dbd61. cf7cd5dc3ecb6ab 80739dbd61 commit is the
> This behavior has started between commit
> 2f3dc472edc8825
> c143850d69db1fc
>
> I suspect the c143850d69db1fc
> cause of the issue. Either the test itself is using a model connection
> (and thus this fails?), or something is wrong within juju-core itself.
>