Comment 9 for bug 1619812

@Andrew, I have been trying to recreate with 2.2 but not having any success which is good if this means the problem has been fixed. Do you know whether this hardcode was added recently? However, do note that the hardcode to a default network would work for a lot of vsphere environments, but "VM Network" is just a default name for the default portgroup. There is nothing preventing a user from renaming it and I've verified that the bootstrap will fail if I do rename it to say VMNetwork. Typically, I'd name my portgroup based on the network that they connect to.

I'll keep trying to reproduce until I can either get it to fail or conclude that the issue is no longer reproducible. If I see it again, then it should not be any problem to give you access to that environment.