Comment 5 for bug 1695335

Revision history for this message
Menno Finlay-Smits (menno.smits) wrote :

I've tried to replicate this with the LXD provider and I see the instance-status changes.

See the test client I used and observed output here: https://gist.github.com/mjs/484dd863dd6bc593bb2690f7450d7cc6

This was tested with the latest "develop" branch (what will become 2.3) and 2.2.2.

The odd thing I do see is that the instance status is reported as changing from pending to running and then back to pending before going to running again. Checking the status history for the machine in the DB reveals that the instance status never actually made these transitions so it appears there is an allwatcher bug lurking there but not the one that was reported.