Bug 1896181

Occasionally in 4.7+ CI:

$ w3m -dump -cols 200 'https://search.ci.openshift.org/?search=VM+is+being+updated.*409+Conflict&maxAge=48h&context=1&type=build-log' | grep 'failures match' | sort 
pull-ci-openshift-installer-master-e2e-ovirt - 9 runs, 89% failed, 13% of failures match
release-openshift-ocp-installer-e2e-ovirt-4.7 - 12 runs, 67% failed, 13% of failures match

Example job [1]:

level=error
level=error msg=Error: Fault reason is "Operation Failed". Fault detail is "[Cannot run VM. VM is being updated.]". HTTP response code is "409". HTTP response message is "409 Conflict".
level=error
level=error msg=  on ../tmp/openshift-install-072387181/masters/main.tf line 1, in resource "ovirt_vm" "master":
level=error msg=   1: resource "ovirt_vm" "master" {
level=error
level=error
level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change

Not sure if that's "file a ticket with the provider" or "installer's Terraform should be more robust about retries in the face of conflicts", but filing a bug so other folks who hit this failure mode can find whatever the plan ends up being.

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-ovirt-4.7/1325865204830965760