[14:02] <Hybrid512> Hi
[14:05] <Hybrid512> One small question : I sometime have some units that are stuck in "blocked" status because of apache2 not running (or ports not open but that's most of the time related to the same issue). I'm not talking anout why apache2 is not running, this is due to a known issue with HA and certificates and there is a simple workaround in that case. My
[14:05] <Hybrid512> question is, when I fix the problem and restarted Apache2, it takes sometaimes many minutes before the unit switch to the ready state because I suppose there are some scheduled checks and until that check is not triggered, status doesn't change.
[14:06] <Hybrid512> When units are in error state, I can use the "juju resolve" command that retrigger the hook immediately, is there something similar with blocked units ? Is there a way to force triggering a check so that a fixed unit can switch to the ready state immediately ?
[14:07] <Hybrid512> and not by waiting minutes
[14:29] <stickupkid> Hybrid512, that's a good question... from reading the code around resolve, it checks just for the error status... I'll ask around to see if and why that can't encompass blocked
[14:29] <Hybrid512> I found an old bug reports towards this (for juju 2.0 beta) but this was never answered
[14:30] <Hybrid512> right now, something similar to "juju resolve" would be great ... actually, I would have thought "juju resolve" would do the trick but I then get an error message saying the unit is not in an error state :/
[14:47] <stickupkid> Hybrid512, yes because we treat blocked and error as two different states
[14:47] <stickupkid> manadart, https://github.com/juju/juju/pull/12279 gce
[14:48] <Hybrid512> stickupkid agreed but then, would be great to have a similar command to do that ... something like "juju unblock" or something
[21:31] <jam> thumper: /wave
[21:56] <thumper> jam: /wave back