[00:10] sarnold, answered btw re askubu [00:12] hazmat: cool :) [00:12] hazmat: s/your/you're/ [00:13] * hazmat concedes an edit to the rules of a punctuation [00:13] :-) [00:15] yay, done within the five minute window :D [00:15] "look ma, no edit" :) === thumper-gym is now known as thumper === JoseAntonioR is now known as JoseeAntonioR === SpamapS_ is now known as SpamapS === defunctzombie is now known as defunctzombie_zz === mthaddon` is now known as mthaddon [08:11] * mariusko is really tired of Juju-gui stopping working [08:13] mariusko: please join #juju-gui and describe the problem [08:18] frankban: ah, didn't knew there was a separate channel === andrewdeane is now known as awd === salgado` is now known as salgado === lborda is now known as lborda_afk [12:53] Is anyone able to address bug 1159020 ? - Juju is unusable in raring [12:53] <_mup_> Bug #1159020: SyntaxError: invalid syntax < https://launchpad.net/bugs/1159020 > [12:53] bug 1159020 in juju "SyntaxError: invalid syntax" [High,Confirmed] https://launchpad.net/bugs/1159020 [12:53] <_mup_> Bug #1159020: SyntaxError: invalid syntax < https://launchpad.net/bugs/1159020 > [12:53] <_mup_> Bug #1159020: SyntaxError: invalid syntax < https://launchpad.net/bugs/1159020 > [13:17] bothfight [13:17] bot even === salgado` is now known as salgado [13:45] Okay, landscape-client kills juju-machines [13:45] With its CPU and RAM usage [13:45] It is not even possible to get rid of it completely [13:49] sarnold: unattended-upgrades charm is promulgated :) [13:52] dpb_: ^ === sidnei` is now known as sidnei [13:58] 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] mthaddon: If the charm is in an error state, you can juju resolved --retry ; 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] marcoceppi: I'd rather avoid jitsu and do it "the right way"™ if there is such a thing [14:06] 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] marcoceppi: I might just send a mail to the list, as this is kind of an interesting question - thx for your feedback [14:06] Well, there is a way to "sort of" trap hooks and fire them off at will, using juju debug-hooks [14:07] 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 === rvba` is now known as rvba [14:08] 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] thx === defunctzombie_zz is now known as defunctzombie [14:31] mthaddon, replied via email [14:31] thx [14:32] marcoceppi, the run-as-hook needs a big warning in blinkies that its executing on the local machine [14:32] er client [14:33] i think its broken.. [14:33] 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] 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] Yeah, that would be swell [15:08] argh.. pypi down === salgado is now known as salgado-lunch === salgado-lunch is now known as salgado === BradCrittenden is now known as bac === BradCrittenden is now known as bac === ubot5` is now known as ubot5