[03:12] <mxc> been banging my head against the wall on this for a while:
[03:12] <mxc> 2013-12-07 02:21:11 INFO juju.environs open.go:156 environment info already exists; using New not Prepare
[03:12] <mxc> 2013-12-07 02:21:13 ERROR juju supercommand.go:282 failed to get blob "provider-state": Azure request failed: AuthenticationFailed - Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
[03:12] <mxc> RequestId:75c99034-8f50-452f-bb47-a948949e6fba
[03:12] <mxc> trying to bootstrap in azure using the same set up that has worked on an azure machine before
[03:12] <mxc> the difference is that i'm trying to run this from a non-azure machine
[03:12] <mxc> could that be part of the problem?
[03:13] <mxc> also, is there a way to get more verbose output?  I've tried -v and -vvv
[03:44] <mxc> ugh, timezone issue
[03:44] <mxc> the time on my virtual machine got out of sync
[10:35] <_bjorne> are that someone here who can some of cloud-init and maas? why the nodes fail read user-data.
[12:28] <_bjorne> is that some one here? that can explane if im need to make user-data file and cloud-config.txt on maas server?
[14:51] <_bjorne> someone live?
[20:29] <ashipika> hi guys..
[20:29] <ashipika> having problems deploying juju-gui charm
[20:29] <ashipika> here's the log: http://paste.ubuntu.com/6537049
[20:30] <ashipika> seems to fails when it wants to chown something to a nonexistent "ubuntu" user
[20:38] <ashipika> anybody?
[20:40] <InformatiQ> ashipika: what rovider ?
[20:40] <ashipika> null
[20:51] <ashipika> ?
[20:58] <InformatiQ> ashipika: i meant provider
[20:58] <InformatiQ> local or aws or what?
[21:02] <ashipika> null..
[21:03] <ashipika> you mean environment
[21:07] <rick_h__> ashipika: yea, it's expecting an ubuntu user account on the system, which might not be true in your own systems.
[21:07] <rick_h__> ashipika: can you file a bug with your paste https://bugs.launchpad.net/juju-gui please?
[21:07] <ashipika> sure! thnx for the info
[21:07] <rick_h__> ashipika: to work around it you can create an ubuntu user on the system for now
[21:08] <rick_h__> ashipika: not sure what else you'll hit as you're hitting a code path not planned for in the charm atm
[21:08] <ashipika> rick_h: is there another way to install juju-gui?
[21:09] <rick_h__> ashipika: hmmm, I mean you can manually install things, but it's non-trivial compared to the charm
[21:09] <rick_h__> the best thing I can think to do would be to duplicate the environment expected with an ubuntu user with sudo permissions
[21:09] <rick_h__> I don't recall if it uses the sudo permissions for anything, but that's the only other thing I can see hitting compared to say aws, openstack, etc
[21:10] <rick_h__> on most cloud systems the ubuntu user has password-less sudo access
[21:11] <ashipika> hmmm.. not the safest thing imo
[21:11] <ashipika> ok.. filed a new bug https://bugs.launchpad.net/juju-gui/+bug/1258827
[21:11] <_mup_> Bug #1258827: Juju-gui deploy requires an "ubuntu" user <juju-gui:New> <https://launchpad.net/bugs/1258827>
[21:11] <rick_h__> ashipika: thanks, I'll bring it up on Monday to the team
[21:11] <ashipika> thanks.. for now i will follow your advice and create an ubuntu user with sudo permissions..
[21:14] <rick_h__> ashipika: cool, sorry you hit it. that provider is kind of new and we've not tested with it much. I think when we have, we've brought up ec2 instances which have the ubuntu user and haven't hit it.
[21:15] <ashipika> i know i know :) love playing with cutting edge things ;_