CRC is a tool to help you run containers. It manages a local OpenShift 4.x cluster, Microshift or a Podman VM optimized for testing and development purposes
When running nightly integration tests the integration scenario for change memory cpus and disk is failing as we are using a custom bundle for testing.
After the first cluster initialization the scenario changes the config and start the cluster to ensure those changes take effect, but on the 2nd start the custom bundle is not honored and the test ends up failing:
Bundle 'crc_vfkit_4.15.10_amd64' was requested, but the existing VM is using 'crc_vfkit_4.15.12_amd64'. Please
The custon bundle option should be checked on the 2nd start
When running nightly integration tests the integration scenario for change memory cpus and disk is failing as we are using a custom bundle for testing.
After the first cluster initialization the scenario changes the config and start the cluster to ensure those changes take effect, but on the 2nd start the custom bundle is not honored and the test ends up failing:
The custon bundle option should be checked on the 2nd start