[09:51] <Bofu2U> is there an easy way to just deploy a KVM VPS? with juju?
[09:51] <Bofu2U> just with a stock centos image or something like that
[11:02] <Laney> hi
[11:02] <Laney> I defined a new action in my charm and then upgraded it (juju upgrade-charm), but I can't run it (status: failed, script never run)
[11:02] <Laney> is this known to not work?
[13:27] <bloodearnest> Laney, what's the error output when you try to run the action?
[13:27] <Laney> bloodearnest: I don't see any output, where might it be?
[13:28] <Laney> wait
[13:28] <Laney> I do!
[13:28] <Laney> 'action not implemented on unit ...#
[13:28] <Laney> so you can't upgrade and get new actions?
[13:29] <bloodearnest> Laney, what does this say: juju action defined <svc>
[13:30] <Laney> bloodearnest: It's in there
[13:31] <bloodearnest> Laney, and juju action do <svc> <action> gave you 'action not implemented on unit'
[13:31] <bloodearnest> ?
[13:31] <Laney> right
[13:31] <bloodearnest> so if the action is defined, then the upgrade worked and it's available
[13:32] <Laney> well it's <unit> in one case and <svc> in the other
[13:32] <Laney> If I ssh in I can see that actions.yaml was indeed updated
[13:33] <bloodearnest> Can you try invoke the action manually?
[13:33] <bloodearnest> when ssh'd in?
[13:34] <Laney> yes, but the first line is a juju-log which I never see in the debug-log
[13:34] <Laney> so I suspect it's not running
[13:35] <bloodearnest> Laney, what version of juju is your environment?
[13:35] <Laney> 1.25.0
[13:36] <bloodearnest> it's odd that it;s defined, but then can't be executed
[13:37] <bloodearnest> Laney, is actions/<your-action> executable?
[13:38] <Laney> yup
[13:38] <Laney> I can't run it manually, don't know how to set the environment up
[13:38] <Laney> JUJU_CONTEXT_ID
[13:40] <bloodearnest> Laney, I think you should be able to run it like so, from the unit: juju-run <unit> action/<your-action>
[13:41] <bloodearnest> Laney, if you want to check/rulle out the upgrade-charm being an issue, simply add a new unit, and see if the actions works on that.
[13:46] <Laney> bloodearnest: bleh, juju-run doesn't seem to ever do anything, is that because config-changed is still running?
[13:46] <Laney> (the failure was from before this)
[13:49] <bloodearnest> Laney, ah, we have a stuck unit
[13:50] <Laney> it's meant to still be running
[13:50] <bloodearnest> Laney, juju serializes hooks/actions on a unit. So if one is stuck, blocks all else. Any ideas why config-changed is still running?
[13:50] <Laney> still grinding away
[13:50] <bloodearnest> it's deliberate?
[13:51] <Laney> but when I tried the action it was before I changed the config, nothing was running then
[13:51] <Laney> just means I can't try juju-run now
[13:51] <bloodearnest> Laney, ack
[14:08] <gnuoy> jamespage, https://code.launchpad.net/~gnuoy/charms/trusty/nova-compute/no-hugepages/+merge/279245 to unbreak nova-compute if you have a moment. The amulet fail is odd as I can't actually see a failed test
[14:24] <bloodearnest> another charm layers question: I have charm layer at ./layers/x509-cert: It's layer.yaml has: includes: ['layer:basic', 'interface:x509-paths']
[14:25] <bloodearnest> I have interface defined at ./interfaces/x509-paths/
[14:25] <bloodearnest> the charm builds fine
[14:26] <bloodearnest> but, the built charm output, the hooks/relations/x509-paths directory containes the x509-cert *charm* code, not the interface code, as I was expecting
[14:26] <bloodearnest> am I doing something wrong?
[14:27] <bloodearnest> charm layer: http://bazaar.launchpad.net/~bloodearnest/charms/trusty/x509-cert/trunk/files
[14:27] <bloodearnest> interface layer: http://bazaar.launchpad.net/~bloodearnest/+junk/x509-paths/files
[14:29] <bloodearnest> output looks like: http://paste.ubuntu.com/13623707/
[15:58] <JoseeAntonioR> marcoceppi: ping
[16:41] <Laney> if I mess up an upgrade-charm hook how can I push a new version and retry?
[16:41] <Laney> I tried upgrade-charm again and resolved --retry but it has the old version still
[16:48] <Laney> I got it, upgrade-charm --force && resolved --retry
[16:51] <asanjar> kwmonroe: hey ugly
[16:52] <asanjar> kwmonroe: the latest spark-bench code should get uploaded to github
[16:52] <asanjar> soon
[22:57] <thomi> Hi, my juju deployment is stuck, and I see this error in 'juju debug-log' every few seconds:
[22:57] <thomi> machine-0: 2015-12-02 22:56:15 ERROR juju.worker runner.go:223 exited "toolsversionchecker": cannot update tools information: cannot get latest version: cannot find available tools: no tools available
[22:57] <thomi> any ideas?
[23:02] <jrwren> chamers: requesting requeue: http://review.juju.solutions/review/2357