[00:10] <hazmat> sarnold, answered btw re askubu
[00:12] <sarnold> hazmat: cool :)
[00:12] <sarnold> hazmat: s/your/you're/
[00:13]  * hazmat concedes an edit to the rules of a punctuation
[00:13] <hazmat> :-)
[00:15] <sarnold> yay, done within the five minute window :D
[00:15] <sarnold> "look ma, no edit" :)
[08:11]  * mariusko is really tired of Juju-gui stopping working
[08:13] <frankban> mariusko: please join #juju-gui and describe the problem
[08:18] <mariusko> frankban: ah, didn't knew there was a separate channel
[12:53] <popey> Is anyone able to address bug 1159020 ? - Juju is unusable in raring
[12:53] <_mup_> Bug #1159020: SyntaxError: invalid syntax <juju:Confirmed> < https://launchpad.net/bugs/1159020 >
[12:53] <ubot5`> bug 1159020 in juju "SyntaxError: invalid syntax" [High,Confirmed] https://launchpad.net/bugs/1159020
[12:53] <_mup_> Bug #1159020: SyntaxError: invalid syntax <juju:Confirmed> < https://launchpad.net/bugs/1159020 >
[12:53] <_mup_> Bug #1159020: SyntaxError: invalid syntax <juju:Confirmed> < https://launchpad.net/bugs/1159020 >
[13:17] <sidnei_> bothfight
[13:17] <sidnei_> bot even
[13:45] <mariusko> Okay, landscape-client kills juju-machines
[13:45] <mariusko> With its CPU and RAM usage
[13:45] <mariusko> It is not even possible to get rid of it completely
[13:49] <bbcmicrocomputer> sarnold: unattended-upgrades charm is promulgated :)
[13:52] <sidnei`> dpb_: ^
[13:58] <mthaddon> If we have a problem with a particular hook, and fix that, we can upgrade-charm to rollout the fixed version of the charm. However, how do we actually fire the hook in question?
[14:03] <marcoceppi> mthaddon: If the charm is in an error state, you can juju resolved --retry <charm>; if it's not you'll either need to change a relation or configuration (to get the hook to fire again). IIRC there's a jitsu command to "run-as-hook" that might also help achieve what you're trying to do
[14:05] <mthaddon> marcoceppi: I'd rather avoid jitsu and do it "the right way"™ if there is such a thing
[14:06] <marcoceppi> mthaddon: understood. You can't just fire off hooks arbitrarily from juju itself. You'll need to trigger the event again if possible
[14:06] <mthaddon> marcoceppi: I might just send a mail to the list, as this is kind of an interesting question - thx for your feedback
[14:06] <marcoceppi> Well, there is a way to "sort of" trap hooks and fire them off at will, using juju debug-hooks
[14:07] <mthaddon> yeah, that was one of the workarounds we'd thought of, but as I say, would like to do it "the right way"™ if there is such a thing
[14:08] <marcoceppi> The list might have more interesting feedback, to be honest (outside of jitsu) I think debug-hooks would be your next and possibly only bet
[14:08] <mthaddon> thx
[14:31] <hazmat> mthaddon, replied via email
[14:31] <mthaddon> thx
[14:32] <hazmat> marcoceppi, the run-as-hook needs a big warning in blinkies that its executing on the local machine
[14:32] <hazmat> er client
[14:33] <hazmat> i think its broken..
[14:33] <marcoceppi> hazmat: the help was slightly off-putting. I saw that it "executes locally" I just assumed that meant in relation to the machine it was referring to
[14:33] <hazmat> what would be nice is a juju-run-hook cli api on the units that admins, cron jobs can use to execute hooks
[14:34] <marcoceppi> Yeah, that would be swell
[15:08] <hazmat> argh.. pypi down