agent-state pending

Gustavo Niemeyer gustavo.niemeyer at canonical.com
Mon Aug 5 17:01:51 UTC 2013


Dimiter spotted the probable issue that is causing the bug:

--upload-tools doesn't rebuild the tools anymore, and I wasn't
rebuilding the jujud tool locally before deploying. The remote version
told me it was a new release, but it was actually a lie, being forced
by the FORCE-VERSION file.

I'll destroy and retry.  Thanks Dimiter.


On Mon, Aug 5, 2013 at 5:21 PM, Gustavo Niemeyer
<gustavo.niemeyer at canonical.com> wrote:
> On Mon, Aug 5, 2013 at 5:03 PM, Dimiter Naydenov
> <dimiter.naydenov at canonical.com> wrote:
>> - From 1.12 onwards the machiner uses the API and SetAgentAlive logic
>> changed, so now by having an active API connection the agent is deemed
>> alive. The agent-state is set using a Machiner SetStatus API call. If
>> you check the all-machines.log on machine 0, you can probably find if
>> lines like these can be found:
>>
>> [LOG] 47.41701 DEBUG juju rpc/jsoncodec: <-
>
> There are no lines with rpc/jsoncodec at all in that file.
>
> I'm running:
>
>     revision-id: tarmac-20130805111317-geb3dyacpuhzw6p1
>     timestamp: Mon 2013-08-05 11:13:17 +0000
>
>
> gustavo @ http://niemeyer.net



-- 
gustavo @ http://niemeyer.net



More information about the Juju-dev mailing list