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
Notice we are still hitting that from time to time, this is from the last 14 days: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/15029/rehearse-15029-pull-ci-openshift-installer-release-4.4-e2e-ovirt/1351493342176743424 https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_installer/4524/pull-ci-openshift-installer-master-e2e-ovirt/1351175558989352960 https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/14922/rehearse-14922-pull-ci-openshift-csi-livenessprobe-release-4.8-e2e-ovirt/1350172015276855296 the error is is "Cannot run VM. VM is being updated", probably we need to add a check before starting the VM in the ovirt_vm resource in terraform: https://github.com/oVirt/terraform-provider-ovirt/blob/master/ovirt/resource_ovirt_vm.go#L614
due to capacity constraints, we will be revisiting this bug in the upcoming sprint
This will be resolved automatically when we switch to the new client library.
Fixed in 2082283
(In reply to Janos Bonic from comment #6) > Fixed in 2082283 Fixed in bz 2082283
The issue is gone. Such terraform errors no longer visible in the installer. Verified on - 4.11.0-0.nightly-2022-06-22-235234 and rhvm-4.5.1.2-0.11.el8ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069