Starting in VSphere Plugin 2.16, the behaviour at the end of a job has broken.

I configure the node to disconnect after 1 build, and to shutdown at that point.  This, along with snapping back to the snapshot upon startup, gives me a guaranteed-clean machine at the start of every build.

Starting in version 2.16, the plugin seems to opportunistically ignoring the "disconnect after (1) builds", and is re-using the node to run the next queued job without enforcing a snap back to the snapshot.  This next build then has high odds of failing or mis-building, as the node is unclean.

WORKAROUND: Revert back to plugin version 2.15, where the error does not occur.