Tested on both LXD and AWS. There is a test case in libjuju for this at https://github.com/juju/python-libjuju/blob/49fe19ff5754ae8ce9365cd7bddbcd33f565bd69/tests/integration/test_machine.py#L10 (libjuju current has a work-around to make this test case pass, but if you comment out https://github.com/juju/python-libjuju/blob/49fe19ff5754ae8ce9365cd7bddbcd33f565bd69/juju/machine.py#L14 it will fail).
On a side note, there seems to be a difference in the info / message field for the instance-status between providers, with the LXD provider giving a message of "Ready" while the AWS provider gives a message of "ready", hence the need for normalizing it in the test (https://github.com/juju/python-libjuju/blob/49fe19ff5754ae8ce9365cd7bddbcd33f565bd69/tests/integration/test_machine.py#L35). However, since this is just an informational message, I don't think that really matters.
Tested on both LXD and AWS. There is a test case in libjuju for this at https:/ /github. com/juju/ python- libjuju/ blob/49fe19ff57 54ae8ce9365cd7b ddbcd33f565bd69 /tests/ integration/ test_machine. py#L10 (libjuju current has a work-around to make this test case pass, but if you comment out https:/ /github. com/juju/ python- libjuju/ blob/49fe19ff57 54ae8ce9365cd7b ddbcd33f565bd69 /juju/machine. py#L14 it will fail).
On a side note, there seems to be a difference in the info / message field for the instance-status between providers, with the LXD provider giving a message of "Ready" while the AWS provider gives a message of "ready", hence the need for normalizing it in the test (https:/ /github. com/juju/ python- libjuju/ blob/49fe19ff57 54ae8ce9365cd7b ddbcd33f565bd69 /tests/ integration/ test_machine. py#L35). However, since this is just an informational message, I don't think that really matters.