Closed tomck closed 8 years ago
Possible duplicate of https://github.com/juju/juju-gui-charm/issues/45
@tomck Can you tell me which version of the juju-gui charm you have?
@tomck Can you paste the output of
juju status juju-gui
here please?
:ssh $ juju status juju-gui
[Services]
NAME STATUS EXPOSED CHARM
juju-gui maintenance true cs:trusty/juju-gui-50
[Units]
ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
juju-gui/0 maintenance executing 2.0-alpha2 1 168.61.x (install) installing charm software
[Machines]
ID STATE DNS INS-ID SERIES AZ
1 started 168.61.x machine-1 trusty
Thanks @tomck. There is a known problem with juju-gui-50. If you can redeploy you'll get the new one and it will work.
I'll leave this issue open until @tomck you can confirm juju deploy juju-gui
now works for you and deploys -51.
This issue is sorted, it does install and open. I can't login because show-controller is no longer a command, however, but that is a separate bug.
$ juju show-controller --show-passwords
ERROR unrecognized command: juju show-controller
@hatched could you provide @tomck with the new command?
@tomck This release of the juju gui is geared to the Juju 2 beta release which is coming out today. The method for getting the username and password we document is for that version of juju. I don't have access to the alpha version you have. You might try juju api-info --password password
. I can't guarantee that it'll work but it might.
It did not, now trying juju 2 beta 1, which is for some reason not recognizing the existing config at all. Tried informing it that I have the azure config up but that's unacceptable. Is there a list of changes between versions somewhere? There seems to be big jumps each time, to where "init" isn't an option anymore in the 2.x series even though it shows up in juju help.
ERROR unrecognized command: juju init
$ juju switch azure
ERROR "azure" is not the name of a model or controller
Fortunately I still have the alpha 2 binaries, but it's confusing that beta 1 can't takeover from alpha 2.
Sorry, yes. Please see the release notes and we've got a new beta coming out today with more progress on the front.
https://lists.ubuntu.com/archives/juju/2016-February/006618.html
On Thu, Mar 10, 2016 at 2:29 PM Tom Koch notifications@github.com wrote:
It did not, now trying juju 2 beta 1, which is for some reason not recognizing the existing config at all. Tried informing it that I have the azure config up but that's unacceptable. Is there a list of changes between versions somewhere? There seems to be big jumps each time, to where "init" isn't an option anymore in the 2.x series even though it shows up in juju help.
ERROR unrecognized command: juju init $ juju switch azure ERROR "azure" is not the name of a model or controller
Fortunately I still have the alpha 2 binaries, but it's confusing that beta 1 can't takeover from alpha 2.
— Reply to this email directly or view it on GitHub https://github.com/juju/juju-gui-charm/issues/47#issuecomment-195010414.
The commands to get your credentials are as follows:
// Juju 1.x
juju api-info --password password
// Juju 2.0-beta1
juju show-controller --show-passwords
It's possible that you were using an older version of Juju 2.0. As @mitechie said, you should expect to see a new beta being released very soon.
On the azure-provider, the first thing I set up after bootstrapping was juju-gui. However, the install hook would fail. I tried debugging it, and here's my output:
The log files don't seem to contain any useful data, and I'm not sure what from them would be considered insecure to share (api keys etc).