Juju does not remember controller after register

Bug #1614161 reported by Aaron Bentley
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Horacio Durán

Bug Description

After a controller has been set with juju-register, change-user-password dies with:
no controller

Please either create your own new controller using "juju bootstrap" or
connect to another controller that you have been given access to using "juju register"

It appears that juju is no longer tracking the current controller.

As seen in:
http://reports.vapour.ws/releases/issue/57b489fe749a5611d0fafc16
(Note: only the end of the error message is shown in the console output.)

Aaron Bentley (abentley)
Changed in juju-core:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Richard Harding (rharding)
summary: - Juju does not remember controller after register
+ Juju does not remember controller after add-user
summary: - Juju does not remember controller after add-user
+ Juju does not remember controller after register
tags: added: ci jujuqa register regression
Aaron Bentley (abentley)
Changed in juju-core:
milestone: none → 2.0-beta16
Revision history for this message
Nicholas Skaggs (nskaggs) 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.

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 1614161] Re: Juju does not remember controller after register

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.
>

Changed in juju-core:
assignee: Richard Harding (rharding) → Ian Booth (wallyworld)
Ian Booth (wallyworld)
Changed in juju-core:
assignee: Ian Booth (wallyworld) → Horacio Durán (hduran-8)
Changed in juju-core:
status: Triaged → In Progress
Revision history for this message
Horacio Durán (hduran-8) wrote :

I am using the modified version of this test (for the new add-user signature) but I need to fix https://bugs.launchpad.net/juju-core/+bug/1613444 before being able to either reproduce or mark it as fixed.

affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta16 → none
milestone: none → 2.0-beta16
Revision history for this message
Horacio Durán (hduran-8) wrote :

I believe this is fixed, but to confirm its pending a change by @veebers to the CI test which in turn is waiting for http://reviews.vapour.ws/r/5517/ to land

tags: added: blocker
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0-beta16 → 2.0-beta17
Revision history for this message
Horacio Durán (hduran-8) wrote :

Fix committed pending a patch in CI by @veebers

Changed in juju:
status: In Progress → Fix Committed
tags: removed: blocker
Curtis Hovey (sinzui)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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