Sleep 60 seconds when running against vSphere 6.5 to ensure resource pool configuration settings propogate successfully.
Remove prior failed attempt to allow resource pool settings to propogate.
We've observed that on vSphere 6.5, it is possible to start a VM in a resource pool despite memory limitations if the VM is started very soon after the memory limits are changed. This causes our tests to fail. It is unlikely this will affect production 6.5 instances as the CPI does not explicitly configure resource pools (instead, a user would do this, presumedly well before BOSH begins to add VMs to the pool).
Type of change
Please delete options that are not relevant.
[X] Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration