[00:43] <Tug> so I tried to deploy the "mongodb-cluster" in a vagrant vm, how can I check that it's up and running ?
[00:43] <Tug> I cannot ssh to the mongos unit
[00:43] <Tug> vagrant@vagrant-ubuntu-precise-64:~$ juju ssh mongos/0
[00:43] <Tug> ERROR unit "mongos/0" has no public address
[00:43] <sarnold> have you exposed the unit?
[00:43] <sarnold> s/unit/service/
[00:43] <Tug> yes
[00:43] <sarnold> can you connect a mongo client to the address specified?
[00:43] <Tug> using the web ui first
[00:44] <Tug> then with juju expose mongos
[00:45] <Tug> sarnold, which address are you talking about ?
[00:46] <Tug> (my machine is really unstable atm, but I can understand as the vm runs 13 units)
[00:47] <davecheney> sarnold: this is different
[00:47] <davecheney> open-port / juju expose is for network connections of the service
[00:47] <davecheney> juju ssh, ewll, ssh's to that unit
[00:48] <davecheney> but it looks like there is no public address available
[00:48] <davecheney> so it cannot route to that machine
[00:48] <davecheney> Tug: you could try, juju ssh $THE NUMBER OF THE MACHINE
[00:48] <sarnold> which could be if using the local provider (lxc), right?
[00:48] <davecheney> look in juju status
[00:48] <sarnold> (at least I think I heard 'juju ssh' doesn't work with lxc..)
[00:48] <davecheney> sarnold: i'm not sure qhat 'deplou in a vagrant vm' means in the context of juju
[00:48] <davecheney> sarnold: nah, it works
[00:49] <sarnold> davecheney: oh hooray :) what am I thinking of then? :)
[00:49] <davecheney> sarnold: if there is a problem creating hte lxc container
[00:50] <davecheney> then that error is common
[00:50] <davecheney> because we need hte agent to start up inside the containter to report back the ip addresses it sees
[00:50] <sarnold> ahh
[00:50] <Tug> please wait, system is reeeeaaally sloww
[00:51] <Tug> $ juju ssh 5
[00:51] <Tug> Warning: Permanently added '10.0.2.15' (ECDSA) to the list of known hosts.
[00:51] <Tug> Permission denied (publickey,password).
[00:53] <davecheney> ok, this is a bit different
[00:53] <marco-traveling> davecheney: sarnold  juju ssh machine number on local does not work
[00:53] <Tug> It's my first time using juju so I don't really understand what you are saying ^^
[00:53] <davecheney> marco-traveling: it does
[00:53] <marco-traveling> you have to use unit
[00:53] <Tug> hte agent ?
[00:53] <marco-traveling> davecheney: that output suggests otherwise
[00:53] <davecheney> marco-traveling: it really really does
[00:53] <marco-traveling> davecheney: when was that fixed?
[00:53] <Tug> yes it's on the vagrant documentation page
[00:53] <davecheney> ubuntu@winton-02:~/charms/trusty$ juju ssh 1 -- bash -c 'whoami;hostname'
[00:53] <davecheney> ubuntu
[00:53] <davecheney> ubuntu-local-machine-1
[00:53] <davecheney> Connection to 10.0.3.42 closed.
[00:53] <Tug> it's supposed to be mongos/0
[00:54] <davecheney> marco-traveling: not sure
[00:54] <marco-traveling> Tug: what does juju status say
[00:54] <davecheney> maybe not fixed in 1.16
[00:54] <davecheney> it's been a long time since I used 1.16
[00:54] <davecheney> absolutely fixed in 1.17/18
[00:54] <Tug> sorry what ? you need my juju version ?
[00:55] <Tug> 1.16.6-saucy-amd64
[00:55] <marco-traveling> okay let's take a Stroo back
[00:55] <sarnold> Tug: can you pastebin your juju status output? (the pastebinit program can be quite helpful for using pastebins)
[00:55] <marco-traveling> step*
[00:56] <Tug> yep yes wait a bit browser is laggy
[00:56] <Tug> http://pastebin.com/5MfLUWs4
[00:58] <Tug> so, lot of "pending", is that good ?
[00:59] <marco-traveling> Tug: it means what you'd expect, things are still being setup
[01:00] <Tug> ok, thx marco-traveling !
[01:01] <Tug> It's been an hour now though
[01:01] <marco-traveling> Tug: you may have exceeded the limits of the vagrant box
[01:01] <marco-traveling> that's a lot of services
[01:01] <Tug> yeah my machine's
[01:02] <Tug> *or my machine's
[01:02] <sarnold> oww :)
[01:02] <marco-traveling> Tug: you might want to try with less units next time
[01:02] <Tug> ok I'll shut it down now and try in a real cloud
[01:02] <marco-traveling> or that
[01:04] <Tug> thanks for your help guys
[01:04] <Tug> (or girls)
[01:04] <sarnold> have fun Tug :)
[01:05] <Tug> I will sarnold, I will
[01:22] <marcoceppi> well I'll be damned, davecheney 1.17.5 fixes juju ssh <machine>
[01:22] <marcoceppi> I'll make sure the next version of the docs have that caveat removed \o/
[01:27] <marcoceppi> davecheney: I just double checked all the release notes, I didn't see it mentioned :\
[01:31] <davecheney> marcoceppi: emoji crying
[04:59] <bloodearnest> \o/
[04:59] <bloodearnest> lxc-clone: true baby!
[05:33] <bloodearnest> oh boy, lxc cloning is a game changed. 10 machines in 10s
[05:33] <bloodearnest> s/changed/changer
[10:08] <gsamfira> Hey there folks. Quick question: Is there any way to force remove a unit in dying state?
[10:09] <gsamfira> without clobbering the machine preferably :)
[11:35] <gsamfira> never mind. Apparently if a machine agent gets interrupted while killing a unit and doesn't manage to report back, it can't recover. It only checks if life == params.Dead
[11:35] <gsamfira> and not ==params.Dying
[12:06] <Tug> I try to understand juju's best practices
[12:06] <Tug> so if I get it right, the documentation say I should not write a charm to deploy my application
[12:10] <Tug> It's unclear to me how I can configure the whole machine then
[12:11] <Tug> for instance, at the moment I have a bash script which copies a nginx.conf which points to a specific path to serve static files and to specific ports where my node.js app is running
[12:11] <Tug> plus nginx is doing extra work like handling ssl, etc
[12:12] <Tug> what should I get started on to port this to juju ?
[12:27] <marcoceppi> Tug: what do you mean? charms should do whatever they need to in order to set up your service
[12:30] <Tug> marcoceppi, ok, then I don't understand where I can set the configuration for the nginx charm
[12:31] <marcoceppi> don't use the nginx charm, just have your charm install ngimx and configure it
[12:31] <Tug> marcoceppi, ok so I do need to write a charm
[12:33] <marcoceppi> yes, it sounds like it. the ngomx charm is more of a microcache + loadbalancer
[12:33] <Tug> I don't know, is it common to write your own charm ?
[12:33] <marcoceppi> very
[12:33] <Tug> or is it supposed to be for service only
[12:33] <Tug> ok
[12:33] <marcoceppi> apt-get is for packages, charms are for deployments
[12:34] <Tug> so to get started, I can just write a charm which executes my bootstrap script
[12:34] <marcoceppi> if you want to think of it like that
[12:34] <Tug> I see
[12:34] <marcoceppi> what bootstrap script?
[12:35] <Tug> the one I'm using atm to configure a new machine, it's just a bash script
[12:35] <marcoceppi> oh, the yes, basically
[12:36] <marcoceppi> bleh, sorry, my swipe keyboard is just not hacking it this morning.
[12:36] <zchander> ping marcoceppi
[12:36] <Tug> alright, thx marcoceppi
[12:37] <marcoceppi> Tug: if you have a script, you basically have like 85-90% of a charm. You might need to tweak it a bit to work with configurations so you can pass configuration variables to the charm, handle relations, etc
[12:37] <marcoceppi> zchander: o/
[12:37] <zchander> Good afternoon (it is here, at least ;) )
[12:37] <overm1nd> for me it would be useful to have a general charm for example to add a php virtual host to apache service
[12:37] <overm1nd> i'm just new to juju
[12:38] <overm1nd> I will try to write my own and experiment
[12:38] <zchander> May I bother you (again) with a 'noob' question? I am trying to deploy Ceph on my MaaS, with Juju. So far, I have managed to get Ceph running, with storage, but how can I make this available through e.g. NFS (or something similar)
[12:39] <marcoceppi> overm1nd: that's not a bad idea, it opens some issues, like some php applications require specific packages, etc, but having a generic php container charm (like we do for tomcat) would be cool
[12:39] <marcoceppi> overm1nd: we have similar examples for rails, node.js, and tomcat* I'd be happy to help answer questions if you want to try to tackle that though
[12:40] <overm1nd> thx marcoceppi, I think it's a very common deployment
[12:41] <marcoceppi> zchander: so, ceph charm exposes a ceph-client interface that you can communicate with from your charm
[12:41] <marcoceppi> zchander: there's an example of how to communicate with ceph in your charm in this example (non-working) charm: http://manage.jujucharms.com/~james-page/quantal/ceph-client
[12:42] <overm1nd> in the docs I cannot find the answer to a simple question
[12:42] <marcoceppi> overm1nd: PHP is a /very/ popular deployment strategy in this day and age of the web. having something like a charm which installed php5-fpm, nginx, etc and configured it with the abiility to co-locate multiple php apps would be really nice
[12:42] <marcoceppi> overm1nd: which question is that?
[12:43] <overm1nd> how we can deal with migration of db from a machine to another?
[12:43] <marcoceppi> overm1nd: as in, you deploy a database charm, and want to migrate the database on it to another deployment of that database charm?
[12:43] <overm1nd> exactly
[12:44] <marcoceppi> overm1nd: well, that varies depending on the charm
[12:44] <overm1nd> suppouse a forum like discourse
[12:44] <zchander> Going to have a look at that. The reason I asked this, The OwnCloud charm only accepts NFS as shared storage.
[12:44] <marcoceppi> overm1nd: the postgresql charm, for example, contains information in the README about how to achieve this
[12:44] <overm1nd> (by the way I really appreciated your work)
[12:44] <marcoceppi> zchander: ah, adding ceph as an option would be really awesome
[12:45] <overm1nd> thx marcoceppi I will dig in to this
[12:45] <marcoceppi> overm1nd: oh dear, sorry you're using that charm, it needs a bit of work to be compatible with latest upstream sadly
[12:45] <overm1nd> I'm planning to use it
[12:45] <overm1nd> now I'm using the docker from sam
[12:46] <overm1nd> but I would like to move everything on juju
[12:46] <marcoceppi> overm1nd: the change isn't that drastic, if you get to it before I do, but ever since Discourse started tracking database settings for production in a different file than database.yml the charm has become broken
[12:47] <marcoceppi> I haven't had time to look at it, but someone with time and knowledge of discourse could patch it pretty quickly
[12:47] <overm1nd> I will wait :P
[12:47] <marcoceppi> The charm's on github if you want to give it a crack, otherwise I'll try to fix it next week
[12:47] <overm1nd> I still need to experiment making my own charm
[12:48] <overm1nd> and understand migrations
[12:48] <marcoceppi> overm1nd: cool, well if you have any questions while writing your own charm feel free to let us know!
[12:48] <overm1nd> the real value for me is not to have to deploy everything again and again moving from an hosting to another
[12:49] <overm1nd> thx your support is precious
[12:50] <marcoceppi> overm1nd: so, doing backups up until recently was painful because we had no real way to just run commands against a charm unless we piped them through ssh, now there's a juju run command which lets us just fire arbitrary commands against the environment. So it'd be easy to just say `juju run --unit mysql/0 mysqldump my-db > /tmp/db.sql` then rsync that file to a new mysql server and restore
[12:50] <themonk> marcoceppi: hi
[12:51] <marcoceppi> not super sexy as far as commands go, but easier. Charms should start having their readmes updated to reflect this new ability in the near future
[12:51] <marcoceppi> themonk: o/
[12:51] <overm1nd> this sounds great
[12:51] <themonk> marcoceppi: in subordinate charm install scripts runs after add-relation ryt?
[12:51] <marcoceppi> overm1nd: there's also work on a generic backup charm. So you could just deploy this backup charm to your db service, configure it to put the backups in say s3, then in your new deployment, deplyo the backup charm in a restoration mode and it'll pull the backup from s3
[12:52] <overm1nd> sounds greater
[12:52] <lazyPower> themonk: not unless the add-relation script implicitly calls the instal hoook.
[12:52] <marcoceppi> themonk: the subordinates install runs first. It follows the same routine a normal charm does, install -> config-changed -> start THEN relation-* hooks, but it only gets added to a service after you run juju add-relation
[12:52] <overm1nd> you guys are doing really good stuff
[12:52] <marcoceppi> overm1nd: I'd like to think so :D
[12:53] <themonk> lazyPower: hi
[12:54] <themonk> marcoceppi: hmm thanks
[13:25] <lazyPower> marcoceppi: is there an env var that juju-deployer can read for local charm store path?
[13:25] <marcoceppi> lazyPower: no idea
[13:25] <lazyPower> ppetraki: ^
[13:26] <marcoceppi> JUJU_REPOSITORY is the juju env variable I think
[13:26] <marcoceppi> lazyPower: why not just make a path to the charm teh branch?
[13:26] <marcoceppi> I think deployer does relative paths
[13:26] <ppetraki> tried that, maybe I messed it up
[13:26] <ppetraki> actually, nm, I messed up, I had branch paths defined and... found a bug in my local bundler :)
[13:28] <hazmat> overm1nd, ping..
[13:37] <overm1nd> hi hazmat
[13:38] <overm1nd> when you have time I will appreciate your help
[13:59] <hazmat> overm1nd, greetings.. got meetings for the next 3hrs :-( would you have time this afternoon?
[13:59] <hazmat> er.. relatively afternoon ;-)
[13:59] <hazmat> dk
[13:59] <overm1nd> yes
[13:59] <hazmat> i can make some time in an hr
[14:00] <overm1nd> just ping me
[14:00] <hazmat> cool
[14:00] <overm1nd> thx you very much
[14:03] <zchander> :q
[14:04]  * zchander forgot, once more to select the correct window
[14:05] <overm1nd> this mistakes can lead you to big troubles with people :P
[14:15] <Tug> Does it matter if I user a System V init script in my charm, or there a reason I should really use upstart ?
[14:16] <marcoceppi> Tug: you can use whichever makes sense for your
[14:16] <marcoceppi> you*
[14:16] <Tug> ok :)
[14:16] <marcoceppi> Tug: there are only a few policies a charm must follow, and that's only if you want it to be in the charm store, otherwise you can pretty much do *anything*
[14:17] <Tug> I see! that's why almost all charms I saw used upstart ?
[14:18] <marcoceppi> Tug: well, upstart is the Ubuntu init system, so people writing charms typically target them to Ubuntu hence the upstart script. But there are charms that create init.d systemv scripts instead
[14:18] <marcoceppi> it's all up to the charm authors preferences, upstart is not a required charm store policy
[14:18] <marcoceppi> Tug: this is the policy, btw, https://juju.ubuntu.com/docs/authors-charm-policy.html
[14:18] <Tug> ok cool, I was just checking I wasn't missing out on big features
[14:19] <marcoceppi> Tug: again, that's just if you want it in the charm store, if it's just for personal use  you can do whatever you like
[14:20] <Tug> alright
[14:20] <Tug> thx, you're being really helpful
[14:42] <Tug> something I don't get in node-app charm: the `app_user` config parameter defaults to `ubuntu` but I don't see the script trying to create the user
[14:45] <Tug> I don't think `ubuntu` is a default user, so how is it going to work out of the box ?
[15:16] <marcoceppi> Tug: the ubuntu user is the default user in all Ubuntu Cloud images
[15:17] <Tug> ok marcoceppi
[15:17] <Tug> does it have a home ?
[15:18] <marcoceppi> Tug: yes, /home/ubuntu
[15:19] <Tug> ok good to know :)
[15:21] <hazmat> overm1nd, pong
[15:22] <overm1nd> hi
[15:23] <overm1nd> you asked me 3 question
[15:23] <overm1nd> but How I can log to the juju bootstrap machine if the bootsrap fails?
[15:28] <hazmat> overm1nd, using your ssh key
[15:28] <overm1nd> yes of course
[15:28] <overm1nd> i connect to the droplet via putty using my ssh-imported key
[15:29] <overm1nd> and the key is present in juju/ssh also
[15:29] <overm1nd> so this part is working
[15:31] <hazmat> overm1nd, putty means the private key is on your desktop
[15:31] <hazmat> overm1nd, is the private key on the droplet your using as a juju client?
[15:31] <hazmat> overm1nd, can we do a hangout/screenshare?
[15:32] <overm1nd> yes is the same key
[15:32] <overm1nd> I have it on the docean panel
[15:32] <overm1nd> and a file on my desktop for putty
[15:32] <overm1nd> we can do if you like
[15:32] <overm1nd> maybe I'm missing something really stupid
[15:33] <overm1nd> in the droplet i'm using to start the boostrap machine
[15:33] <overm1nd> i have a file in juju/evnirometnt/local.jenv
[15:34] <overm1nd> the key is also present there
[15:34] <overm1nd> you can't reproduce the problem?
[15:39] <hazmat> overm1nd, the problem is you also need to have it in ~/.ssh of the machine your droplet your using on the client
[15:40] <hazmat> er... the problem is you also need to have it in ~/.ssh of the machine/droplet your using as the client
[15:40] <overm1nd> ehm I think I have otherwise I could not connect right?
[15:41] <hazmat> overm1nd, right.. but your saying your connecting with putty from your desktop
[15:41] <hazmat> which is not the same at all
[15:41] <hazmat> the key has to be accessible to where the ssh client is being run
[16:17] <overm1nd> guys you rock! thanks hazmat so much for the help!
[16:18] <hazmat> overm1nd, np.. enjoy..  bug/feature suggestions welcome as well.
[16:19] <overm1nd> of course I will spread the juju verb
[19:16] <cjohnston> are there any docs for charm helpers?
[19:18] <marcoceppi> cjohnston: not yet
[19:19] <cjohnston> awesome
[19:25] <overm1nd> guys which is the preferred way to install multiple wordpress site on the same node?
[19:26] <overm1nd> I see a lot of charms for wordpress
[19:26] <overm1nd> wordpress-mu is still the way to go?
[19:29] <sarnold> actually thikning of wordpress, marcoceppi, is this something that could be fixed in our wordpress charms? :) http://blog.sucuri.net/2014/03/more-than-162000-wordpress-sites-used-for-distributed-denial-of-service-attack.html
[19:30] <marcoceppi> overm1nd: wordpress-mu has been built in to wordpress for a while
[19:30] <marcoceppi> overm1nd: the charm would need to be reworked, I've been planning to rewrite it for a while but haven't gotten around to ityet
[19:31] <overm1nd> I see, this is why I was asking
[19:31] <marcoceppi> sarnold: good fine, open a bug and I can have default installs disable that
[19:32] <overm1nd> mmm, I have a service stuck in dying since 10 minutes
[19:32] <overm1nd> is normal?
[19:37] <marcoceppi> overm1nd: is the agent-state in error?
[19:37] <marcoceppi> overm1nd: to answer your question, no
[19:37] <overm1nd> yes
[19:37] <overm1nd> first deploy ever of mysql failed
[19:37] <overm1nd> lol
[19:38] <marcoceppi> overm1nd: do, destroy-server requests are queued just like any other
[19:38] <marcoceppi> if the service or unit is in an error state, it won't process any events
[19:38] <marcoceppi> run juju resolved mysql/0
[19:38] <marcoceppi> to clear the error flag and proceed to the other events
[19:38] <marcoceppi> overm1nd: https://juju.ubuntu.com/docs/charms-destroy.html#caveat-dying
[19:39] <overm1nd> ok
[19:39] <marcoceppi> overm1nd: you may have to run resolved several times if more errors occur
[19:39] <overm1nd> I did destroy-service before but it was not processing
[19:39] <overm1nd> I should read more docs :P
[19:39] <marcoceppi> overm1nd: in 1.17.4 and above there's a --force flag that will allow you to remove services bypassing the state of the service/unit
[19:40] <overm1nd> ok thx
[19:41] <overm1nd> worked
[19:41] <overm1nd> I was a bit worried about it was not doing anything
[19:47] <overm1nd> mmm it's still failing to start
[19:47] <overm1nd> but I have to go now, I will dig in the problem tomorrow, thx for you help
[19:47] <overm1nd> see you
[20:05] <Tug> I'm trying to debug a charm on local
[20:05] <Tug> $ juju debug-log
[20:05] <Tug> Permission denied (publickey,password).
[20:05] <Tug> ERROR exit status 255
[20:05] <Tug> same error as in the vm
[20:05] <lazyPower> Tug: local provider right? those logs are actually stored in $HOME/.juju/local/logs
[20:06] <lazyPower> there's an open bug against debug-log not working properly on local deployments.
[20:06] <Tug> ok thanks lazyPower, I'm going to check
[20:08] <jose> hey marcoceppi! I was wondering if you would like to do another openweek session on juju charming
[20:11] <lazyPower> jose: we have our charm school schedule posted on the fridge
[20:11] <lazyPower> http://fridge.ubuntu.com/calendars/
[20:13] <jose> lazyPower: openweek is a different classroom team event, where we have a week full of sessions on how to get involved with the community, see https://wiki.ubuntu.com/UbuntuOpenWeek :)
[20:13] <lazyPower> Hmm... I'd do that.
[20:13] <lazyPower> an hour long session right?
[20:13] <jose> oh, really? that'd be awesome!
[20:13] <jose> yep, you get to choose your slot
[20:14] <lazyPower> jose: before i fully commit let me pick a small app to charm
[20:14] <lazyPower> we'll live-dev a charm
[20:14] <jose> sure, we can use on-air for that
[20:14] <lazyPower> I'll follow up Monday?
[20:14] <jose> sure, sounds good
[20:15]  * lazyPower thumbs up
[20:15] <jose> thank you :)
[20:26] <lazyPower> jose: I'll do a demo charm for Piwik - the open analytics platform
[20:27] <jose> lazyPower: sounds good! which slot would you like to grab?
[20:27] <jose> open slots are the blanks here https://wiki.ubuntu.com/UbuntuOpenWeek
[20:28] <lazyPower> 1800UTC on Thursday
[20:28] <lazyPower> jose: Actually, lets go Tuesday. Get it out of the way early
[20:29] <lazyPower> so if you want to do another other juju topics, someone can follow the charm school
[20:29] <jose> ok, tuesday at 18 utc?
[20:29]  * lazyPower nods
[20:29] <lazyPower> sounds good to me
[20:29] <jose> cool, do you have a wiki page?
[20:30] <lazyPower> i do not
[20:30] <jose> ok, I'll just link to LP
[20:31] <jose> and it's on the schedule now, thanks a lot! :)
[20:35] <Tug> sorry I don't get it: http://pastebin.com/y75UbaGS
[20:35] <Tug> install: line 27: syntax error in conditional expression
[20:36] <Tug> looks like a bash error
[20:36] <Tug> but I can't see any
[20:38] <lazyPower> Tug: and line 27 that i see is [[ -x /usr/sbin/nginx ]] || install_nginx
[20:38] <Tug> yes
[20:38] <Tug> same syntax as install from node-app charm
[20:38] <lazyPower> hmm
[20:39] <lazyPower> the syntax looks fine
[20:40] <Tug> yeah really weird
[20:41] <lazyPower> when you enable the xtrace, is that indeed where its choking?
[20:42] <Tug> I'll try but I just realized I may have forgot to install juju-local
[20:43] <Tug> is there a way to remove the failed service without destroying environment ?
[20:44] <Tug> destroy service set the service to "life: dying"
[20:44] <Tug> but it's not removed from the environment
[20:49] <lazyPower> Tug: are you on stable or devel series of juju?
[20:49] <Tug> lazyPower, xtrace you meant with "set -eux" ?
[20:49] <lazyPower> yeah, adding the x flag.
[20:49] <Tug> lazyPower, yes
[20:50] <lazyPower> Tug: i meant, ar eyou on stable? or are you on devel?
[20:50] <Tug> $ juju --version
[20:50] <Tug> 1.16.6-saucy-amd64
[20:50] <Tug> stable I think
[20:50] <lazyPower> ok, you dont have the force flag on that version of juju
[20:50] <lazyPower> :(
[20:50] <Tug> I can go to devel if you want
[20:50] <lazyPower> i dont recommend it
[20:50] <lazyPower> theres no upgrade path for deployments made with devel
[20:51] <Tug> what is the force flag going to dio ?
[20:51] <lazyPower> you could force destroy the machine, then the service would remove itself
[20:51] <lazyPower> there's got to be a failed hook in your env if its not clearing itself up and stuck in dying
[20:51] <lazyPower> you'll have to resolve it using juju resolve service/#  until it goes away.
[20:52] <lazyPower> if its a dependent service, i recommend looking at why it failed on the dependent service
[20:52] <Tug> yeah, that's how I'm doing: "juju destroy-environment"
[20:53] <Tug> yeah I'm actually debugging it
[20:53] <Tug> and it's the bash error
[20:53] <lazyPower> you cant destroy a service while you're in debug-hooks :|
[20:53] <Tug> but I can't figure it out
[20:53] <lazyPower> the hook execution doesn't complete until you leave that context, which is why it would be stuck in a dying state.
[20:54] <Tug> I'm not using degub-hooks
[20:54] <Tug> I'm on the local provider
[20:54] <Tug> so it does not work
[20:54] <Tug> I'm just tailing the log file
[20:54] <lazyPower> ... debug-hooks work son local provider last i checked
[20:55] <lazyPower> remoting into my 1.16 farm, 1 moment. I'll validate that statement
[20:55] <Tug> oh sorry I was mixing with debug-log
[20:55] <Tug> never tried debug-hooks actually
[20:55] <lazyPower> yeah :) debug-log is bugged atm
[20:55] <lazyPower> oh man its great
[20:55] <lazyPower> run your hooks in interactive mode to dbug
[20:56] <lazyPower> make live edits to your hooks and re-run them
[20:56] <lazyPower> its actually how i write 3/4 of my charms when i'm prototyping.
[20:56] <Tug> ok let's try :)
[20:57] <Tug> wow!
[20:57] <lazyPower> pretty neat huh?
[20:57] <Tug> it logged me in the machine ?
[20:57] <Tug> yeah
[20:57] <lazyPower> yeah, you're in an interactive tmux session. as hooks execute, you'll see the context of the tmux session change
[20:57] <lazyPower> so, to run your hooks you just call
[20:57] <lazyPower> hooks/hookname
[20:58] <lazyPower> (From within the hook context, that does nothing if you're not in an executing hook context)
[20:59] <Tug> mmm
[20:59] <Tug> How can I run it again now that it has errored ?
[21:00] <lazyPower> juju resolved -r service/#
[21:00] <lazyPower> the -r is shorhand for --retry
[21:01] <Tug> so cool !
[21:01] <Tug> yeah so I'm back to that bash error ^^
[21:01] <Tug> but it sure is better than tailing logs
[21:05] <lazyPower> Tug: start peeling away the layers of complexity
[21:06] <Tug> yeah I think the error is misleading
[21:06] <Tug> install % [[ -x /usr/sbin/nginx ]] || echo "hello"
[21:06] <Tug> hello
[21:07] <lazyPower> so its in that method
[21:07] <lazyPower> ?
[21:07] <Tug> neither
[21:07] <Tug> I just copy pasted it in the shell and it worked
[21:07] <lazyPower> hmm
[21:08] <lazyPower> did you set eux on your shell?
[21:08] <Tug> yes
[21:08] <sarnold> hey Tug :)
[21:08] <Tug> hi sarnold
[21:27] <Tug> lazyPower, how can I resume debugging ?
[21:27] <lazyPower> Tug: beg pardon?
[21:28] <Tug> I want to try again
[21:28] <Tug> $ juju resolved -r nirror-front/0
[21:28] <Tug> ERROR cannot set resolved mode for unit "nirror-front/0": already resolved
[21:28] <lazyPower> ah, well since its in the install hook
[21:28] <lazyPower> and its very difficult to attach to the unit before it kicks off the install hook
[21:28] <lazyPower> i would temporarilly return an exit code > 0
[21:28] <lazyPower> eg: return 1 from your install hook
[21:28] <lazyPower> then you can attach to it and repeat the steps
[21:30] <Tug> mm, it's marked as installed now
[21:30] <Tug> agent-state: installed
[21:30] <lazyPower> destroy and try again :)
[21:30] <Tug> ok :)
[21:42] <lazyPower> ok, i'm out for now
[21:42] <Tug> thanks for your help lazyPower
[21:42] <lazyPower> Tug: if you get stuck and nobody's responsive in #juju over the weekend try the list.
[21:42] <Tug> ok
[21:43] <lazyPower> and no problem :) Happy to help
[21:43] <lazyPower> feel free to ping me if you need anything
[21:44] <Tug> thank you :)
[22:52] <Tug> is manual provisioning not available in stable version ?
[22:52] <Tug> $ juju switch manual
[22:52] <Tug> ERROR "manual" is not a name of an existing defined environment
[22:56] <marcoceppi> Tug: it is, but you have to edit the environments.yaml file
[22:57] <marcoceppi> I think in 1.16 it's called "null" which is dumb
[22:57] <marcoceppi> just change "null" to manual
[22:58] <Tug> yeah I saw the "null" entry, wonder what it was for
[22:58] <Tug> thx marcoceppi I'll do that
[22:58] <marcoceppi> Tug: we renamed null to manual provider
[23:04] <Tug> I set "bootstrap-user: root" but it's trying to connect using my current user
[23:10] <Tug> found this bug https://bugs.launchpad.net/juju-core/+bug/1280432 it's probably related
[23:10] <_mup_> Bug #1280432: manual provider regression on bootstrap-user <manual-provider> <juju-core:New> <https://launchpad.net/bugs/1280432>
[23:15] <blackboxsw> marcoceppi, still workin on getting that review through ou team for block-storage-broker charm in shape for charmstore. thanks for the comments. we'll have something merged in next week for that to also include EC2 support and copyright files and I'll ping you on that review
[23:15] <marcoceppi> blackboxsw: sweet
[23:19] <blackboxsw> interesting juju destroy-service question for folks for a principal and subordinate relationship.
[23:19] <blackboxsw> the subordinate provides a mounted volume to the principal, and will not unmount that volume until the principal's service is stopped
[23:19] <blackboxsw> but relation-departed fires first on the subordinate during juju destroy-service principal-service
[23:20] <blackboxsw> so I'm wondering if there is a way I can make the subordiante's departed hook wait or replay after the principal's
[23:20] <blackboxsw> the principal's departed relation will stop the service in question
[23:21] <blackboxsw> I was wondering if juju-run would give me this functionality from the subordinate (to call the principal's stop hook) but I can't run juju-run from within a hook context
[23:22] <blackboxsw> just musing about how to solve the subordinate/principal hook ordering dependency
[23:23] <blackboxsw> just a note: juju remove-relation principal-service subordinate-service seems to fire the principal's departed hook 1st, so this didn't cause a problem. just juju destroy-service I think
[23:23] <blackboxsw> again it's friday, so I was dropping this bomb out there to see if there were any wild ideas