Re: PROPOSAL: stop recording 'executing update-status hook'

+1 On Fri, May 19, 2017 at 4:13 AM, Tim Penhey wrote: > Hi folks, > > Currently juju will update the status of any hook execution for any unit > to show that it is busy doing things. This was all well and good until we > do things based on time. > > Every five minutes

Re: PROPOSAL: stop recording 'executing update-status hook'

All agents start up in DEBUG until they can talk to the controller and read what the current logging config is set to. Otherwise you wouldn't be able to debug startup issues. That said, I think there was a request to cache the last-known value in agent.conf which would let restarts be less noisy.

Re: PROPOSAL: stop recording 'executing update-status hook'

What would happen if the update-status hook hangs here? I know it only is supposed to be for short-duration status messages (but charm bugs are known to happen). In addition, it will also block other hooks/actions from happening until completed and it will remain in a stuck state with the status

Re: PROPOSAL: stop recording 'executing update-status hook'

On 19 May 2017 at 03:13, Tim Penhey wrote: > Hi folks, > > Currently juju will update the status of any hook execution for any unit to > show that it is busy doing things. This was all well and good until we do > things based on time. > > Every five minutes (or so) each

Weekly Development Summary

Hi folks That time of the week again - almost beer o'clock for those of us in Aus/NZ timezones - and also time to recap on the happenings in the land of Juju development over the past 7 days. We're working hard to get a Juju 2.2 out the door. The week saw a release of 2.2 beta4 which included

Re: PROPOSAL: stop recording 'executing update-status hook'

On Fri, 19 May 2017 at 03:14 Tim Penhey wrote: > Hi folks, > > Currently juju will update the status of any hook execution for any unit > to show that it is busy doing things. This was all well and good until > we do things based on time. > > Every five minutes (or so)