| [21:19] <rharper> ahosmanMSFT: ok, I'm making some progress on your issue; so should have an update to the bug later today; | |
| [21:20] <ahosmanMSFT> rharper: Thanks, is this the ssh issue, I'm still looking into _img_instance | |
| [21:24] <rharper> ahosmanMSFT: I think they are related; in that, what I saw was that during "run" we don't make a custom image, but only launch the base image as the setup_image stage doesn't have anything to do unless you wan to upgrade/install-deb etc to the base image | |
| [21:24] <rharper> and the name of the VM if it's the same on subsequent runs, the image.py _instance() method was not starting the image; which lead to ssh timeouts | |
| [21:24] <rharper> I could observe the VM in the portal in Stopped state while the tests were attempting to ssh into it | |
| [22:20] <ahosmanMSFT> rharper: Let me know if you need anything from my side, I'll do some tests later today and let you know what I find. | |
| [22:32] <rharper> ahosmanMSFT: ok | |