Null environment disregards admin-secret in environments.yaml

Bug #1263900 reported by @les
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Unassigned

Bug Description

Discovered this behavior when trying to deploy juju-gui in a null environment, because i had difficulties logging into the gui.. Found out that the admin-secret in .juju/environments/null.jenv was not the same as the admin-secret specified in the .juju/environments.yaml

My environments.yaml looks like this:
http://paste.ubuntu.com/6628598/

And this is the resulting null.jenv
http://paste.ubuntu.com/6628636/

Note that the two admin-secret-s are not the same..

Is this expected behavior? If so, somebody should tell juju-gui team, to update instructions on where to find the password.

Revision history for this message
@les (alesstimec) wrote :

juju version 1.17.0-percise-amd64

Curtis Hovey (sinzui)
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Andrew Wilkins (axwalk) wrote :

I suspect this was just a leftover .jenv file from a previously failed bootstrap. In any case, I've just tested on trunk that admin-secret from environments.yaml does propagate into the jenv on bootstrap.

Changed in juju-core:
status: Triaged → Fix Committed
milestone: none → 1.17.3
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → 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.