[11:52] <freak_> i have deployed juju-gui and also expose it..but when i type watch juju status i get this outputn: http://paste.ubuntu.com/15667891/
[11:52] <freak_> anyone please help
[11:53] <rick_h_> freak_: seems like it's still going. 
[11:53] <rick_h_> freak_: if it hung for some reason would have to peek at the logs by juju ssh juju-gui/0
[11:54] <rick_h_> freak_: and then checking out /var/log/juju/unit-XXXXX where the XXXX is the unit log for the juju gui unit 0
[11:55] <urulama|eod> rick_h_, freak_: it looks like machine is in error state ... 
[11:56] <rick_h_> urulama|eod: oh doh, yea. 
[11:56] <rick_h_> freak_: can you run juju status --format=yaml ?
[11:56] <rick_h_> freak_: this is juju 2.0? 
[11:57] <freak_> yes juju2.0
[11:57] <rick_h_> freak_: on which cloud?
[11:57] <freak_> machine state is in error
[11:57] <freak_> local.maas
[11:57] <freak_> local.maas cloud
[11:57] <rick_h_> freak_: which version of maas?
[12:00] <freak_> output of juju status --format=yaml is http://paste.ubuntu.com/15668019/
[12:00] <freak_> can you tell me where this yaml file is located whose output its showing
[12:00] <rick_h_> freak_: it's generated yaml
[12:01] <rick_h_> freak_: so not a file on disk there
[12:01] <freak_> MAAS version 1.9.0+bzr4533-0ubuntu1~trusty1
[12:01] <rick_h_> freak_: are any of the nodes in the 'ready' state?
[12:02] <rick_h_> freak_: it looks like the maas has no nodes in the ready state and off for Juju to take from the pool of nodes?
[12:03] <freak_> I have 1 node in deployed state which is bootstrap node 
[12:03] <freak_> i want juju-gui to be colocated with bootstrap node
[12:04] <rick_h_> freak_: did you deploy it with --to:0 ?
[12:05] <freak_> i had only 1 node in the pool so thats why i did not added --to=0 
[12:05] <rick_h_> right, but the bootstrap node is machine 0
[12:05] <rick_h_> so the --to:0 will put it on that machine #0
[12:05] <freak_> so how can i revert the deployment
[12:06] <rick_h_> juju destroy-service juju-gui
[12:08] <freak_> when i run command destroy-service   it shows error http://paste.ubuntu.com/15668159/
[12:12] <freak_> dear rick_h i destroyed juju-gui
[12:12] <freak_> and deployed again
[12:12] <freak_> now below is the state http://paste.ubuntu.com/15668222/
[12:14] <rick_h_> freak_: it's just --to=0 I think
[12:15] <freak_> is it --to=0 or --to:0
[12:16] <rick_h_> sorry, =0 or --to 0
[12:16] <freak_> in the start i did --to=0 this is the output http://paste.ubuntu.com/15668288/
[12:18] <freak_> my machine name in maas is node0.maas
[12:19] <rick_h_> freak_: sorry, I see what's up. so machine 0 is only in the admin model. You're in the default which is meant to be the place to work on things so you can destroy-model
[12:20] <rick_h_> freak_: so to deploy to the bootstrap machine, machine 0, you have to be in the admin model
[12:20] <rick_h_> freak_: so I think it might be worth doing a 
[12:20] <rick_h_> juju switch admin
[12:20] <rick_h_> juju destroy-model default
[12:21] <rick_h_> and then if you want it all on one machine you'll have to use the admin model, though it's tough because you can't remove that model without destroying the controller and rebootstrapping
[12:25] <freak_> rick_h  now this is the status after switching to admin http://paste.ubuntu.com/15668416/
[12:25] <freak_> now how can i access the juju in my browser
[12:35] <freak_> rick_h i want to change my public address in yaml file ..how can i change that
[12:36] <freak_> i can only see that through juju status --format=yaml
[12:39] <rick_h_> freak_: that IP is assigned from MAAS i believe. You can't go in and change it as it's the IP the machine has
[12:47] <freak_> dear rick_h   check this http://paste.ubuntu.com/15668791/
[12:47] <freak_> my public ip is in unresolved endpoints can this be the reason
[12:47] <freak_> because in browser 192.168.6.193/JUJU doesn't open
[12:48] <rick_h_> freak_: so if you go to https://192.168.6.193/ you don't get the GUI/
[12:48] <rick_h_> freak_: ?
[12:48] <freak_> no
[12:48] <rick_h_> freak_: do you get a 404 or 500 or ?
[12:49] <freak_> when i type 192.168.6.193 in browser it ask for username and password
[12:50] <freak_> i opened file accounts.yaml
[12:50] <freak_> and used that username and password
[12:50] <rick_h_> freak_: ah ok, but on that form in text at the bottom shold be a juju command to get your password for the GUI
[12:50] <urulama> freak_: you should do "juju show-controller --show-passwords" 
[12:51] <hatch> hello
[12:52] <freak_> http://paste.ubuntu.com/15668875/
[12:52] <freak_> rick_h this is the output http://paste.ubuntu.com/15668875/
[12:52] <freak_> i used the admin@local and password mentioned in this url
[12:53] <hatch> freak_: when you entered those credentials did you get in?
[12:54] <freak_> no it does loading and again show prompt for username password
[12:54] <hatch> does it say the username and password is invalid?
[12:56] <freak_> no it does not say invalid password or username
[12:57] <freak_> it simple do some loading and then again show prompt for username and password
[12:57] <hatch> ok that's quite odd, are there any console errors?
[12:57] <hatch> when you say prompt do you see a page which says "Juju" on it, or is this a browser authentication input?
[12:59] <freak_> its browser authentication input which says your connection to this site is not private and then ask for username and password
[12:59] <hatch> ok that's not provided by the gui
[12:59] <rick_h_> hatch: I think it might be http access to the state server or something. 
[12:59] <hatch> I am not sure where that's comign from
[12:59] <rick_h_> hatch: this is deployed on machine 0 in juju 2.0
[13:00] <hatch> into the admin model? That doesn't work 
[13:00] <hatch> at least it didn't for me yesterday on tip
[13:00] <freak_> i'm in admin model
[13:00] <rick_h_> hatch: ok, can you help him get the gui in 2.0 installed them as an alternative so the juju gui command runs properly?
[13:00] <rick_h_> freak_: what version of juju are you on exactly? juju --version
[13:02] <freak_> juju version 2.0-beta3-trusty-amd64
[13:03] <hatch> alright so for some reason on that version installing to the admin model doesn't work
[13:03] <hatch> if you run `juju list-models` you will see two models
[13:03] <hatch> `juju switch default`
[13:03] <hatch> then deploy the gui to that one
[13:03] <hatch> `juju deploy juju-gui`
[13:04] <freak_> so how to resolve that ..earlier i was in default ....and that was not working machine was in admin and it was not deploying juju-gui
[13:04] <rick_h_> hatch: he has one machine on maas
[13:04] <rick_h_> hatch: and so we removed default and used admin
[13:04] <hatch> oh..I didn't know maas worked with one machine 
[13:04] <hatch> hah, learn something new every day
[13:04] <hatch> anyways
[13:05] <hatch> hmm
[13:05] <hatch> I unfortunately haven't had enough time to investigate why it won't deploy to admin
[13:06] <rick_h_> hatch: so the question is can you get him a working juju gui command on beta3 please
[13:06] <hatch> that is the question...
[13:06] <freak_> actually hatch situation is like that we have one machine which is the bootstrap node we want juju-gui on same machine colocated
[13:06] <rick_h_> hatch: I thought the upgrade-gui command worked in beta3 with the tarball
[13:07] <hatch> I didn't think it landed until beta4
[13:08] <hatch> things are in heavy flux right now, hard to keep all the pieces straight :)
[13:08] <hatch> there are only like 30 developers landing code every day ;)
[13:09] <hatch> freak_: sorry, I'm just thinking about how this could work for you
[13:16] <freak_> hatch whenever i'm in admin my machine state is error  when i issue command juju status
[13:17] <hatch> freak_: in a little bit here this will be a non-issue as juju 2 will ship with a gui by default :) Right now I'm just waiting for a response from another dev about this issue
[13:17] <freak_> but when i move to admin machine status changesto started
[13:17] <hatch> yeah I'm actually not sure if maas and juju 2 work with only a single machine
[13:17] <hatch> I really have no idea, never tried it
[13:17] <hatch> I had just assumed not
[13:18] <freak_> no i think you misunderstood, i have 3 machines 1 is region controller , 2nd is cluster controller and 3rd is the node which i have bootstrapped for juju
[13:19] <freak_> and on node 3 i'm colocating juju-gui
[13:19] <hatch> ohh
[13:20] <freak_> so actually under cluster controller we have pool of machines in pool i have added only 1 node
[13:20] <freak_> and on that i boot strapped JUJU and want to colocate juju-gui
[13:20] <hatch> right alright, let me spin up juju 2 and see if I can deploy to admin 0
[13:22] <hatch> you might be just in a wierd time of flux :) 
[13:28] <freak_> http://paste.ubuntu.com/15669492/
[13:28] <freak_> may be this will help http://paste.ubuntu.com/15669492/
[13:30] <hatch> freak_: yeah the gui isn't actually installed
[13:31] <hatch> "theres your problem!"
[13:31] <hatch> ;)
[13:31] <hatch> but I'm actually trying to figure out why for you first
[13:31] <freak_> no i destroyed the service juju-gui
[13:31] <freak_> and then deploy it again and expose
[13:31] <freak_> and share log with you
[13:32] <hatch> oh ok
[13:32] <freak_> still i cannot access gui through ip 
[13:32] <hatch> does it still say it's "Waiting for agent initialization to finish"
[13:33] <freak_> yes
[13:33] <hatch> yeah so it's not done installing, and I"m pretty sure it's hanging
[13:33] <hatch> my new model just came up and am deploying the gui
[13:33] <hatch> I'll know shortly
[13:35] <freak_> ok
[13:36] <hatch> freak_: ok so it looks like that issue has been resolved in juju tip
[13:36] <hatch> with tip I'm able to deploy the gui properly into machine 0 in the admin model
[13:37] <hatch> how familiar are you with golang? :)
[13:38] <freak_> no, and also don't know what is juju tip
[13:38] <freak_> can you explain juju tip
[13:38] <hatch> tip, head, trunk :) where everyone is landing code
[13:39] <hatch> basically to fix the issue you're running into you need to either a) not use the admin model or b) build juju from source 
[13:39] <hatch> or c) wait until the next beta is released
[13:39] <hatch> but c is the least fun
[13:40] <freak_> but when i do not use admin mode my machine status is error
[13:40] <hatch> yeah I'm not sure about that, that's beyond my expertise 
[13:41] <freak_> could you please guide me how to build that juju tip ?
[13:42] <freak_> you are referring to and exactly what procedure did you follow to build the juju tip that you just built ? 
[13:42] <hatch> if you're not familiar with the golang flow it's going to be a long process
[13:42] <freak_> could you please share it ? appreciate the help
[13:43] <hatch> your best bet might be to ask in #juju about what might be going wrong with your other machines 
[13:43] <freak_> Also, would Beta 4 address this issue ? If yes, then can you share the ppa/repository to install that
[13:43] <hatch> and if that doesn't work out then you might just be in a broken spot and will need to revert back to juju 1.25
[13:43] <hatch> beta 4 can only be built from source right now
[13:44] <freak_> ok.thanks for support
[13:44] <freak_> its better that i should revert to 1.25
[13:45] <hatch> yeah 1.25 works really well, juju 2.0 is _really_ close to a stable release :) but not quite yet and it seems like you hit one of the rare edge cases
[13:50] <freak_> any approximate or wild guess about the expected date of release ?
[13:50] <hatch> it'll be coming out with the xenial release
[13:50] <hatch> so I think that's April 21
[13:51] <freak_> thanks for help a great deal. Appreciate it ! 
[13:51] <freak_> have a good one !
[13:51] <freak_> see you around 
[13:52] <hatch> no problem, have a good day!
[13:53] <urulama> freak_: beta4 is just around the corner, it'll be out next week. the PPA to use, check out this page https://jujucharms.com/docs/devel/reference-releases#development
[13:54] <urulama> freak_: and that one will also include gui, so you'll just run "juju gui" and that's it, no need to deploy gui charm anymore