Comment 22 for bug 1643911

Hi Davidchen - Thank you to provide the info on your repro:
m1.nano is really small, I'd hope that with a slightly bigger size of 512M and 10 instead of 5 systems I might crash it earlier.
If not triggering I will modify to follow the smaller sizes you had.

I wanted to get openstack out of the equation here, since in these cases it doesn't do a lot more than forwarding commands which hopefully works.
Also I wonder why that would trigger the issue when the fixes are around "asynchronizing" blockjobs, but I take every chance at a test - maybe I overlook such a job at startup/shutdown.

I have started a slightly modified version and will let it run for a few days - hopefully hitting the issue as well.