Closed Kalmalyzer closed 3 years ago
This is likely a cascade effect; #49 occurred for an instance, then that instance is not completely initialized, then this occurs.
It was a separate bug; fixed in https://github.com/falldamagestudio/UE-Jenkins-Images/commit/b76a6cbebc5ceed082fc21bd89ab0d292b7b4e88.
This happens after starting a linux non-docker dynamic VM job (waiting for a node to get provisioned - it fails with #49 - a second node gets provisioned successfully). The second time I'm triggering the same job, Jenkins spits out these when trying to provision:
What's going on? Why does the zone field no longer contain a sensible string? Should this prevent the provisioning from proceeding, or should the plugin catch these errors, print them to the log, and carry on?