Disable consecutive_build_service_disable_threshold

Set consecutive_build_service_disable_threshold to 0
as it was observed that some nodes on a cluster were
disabled after a certain amount of build failures, overloading
the other healthy nodes in the cluster causing a bunch of issues.

Sem-Ver: fix
Change-Id: Id9bedac9710d1f82d4d9bc30a268fd9c14308f9e
diff --git a/releasenotes/notes/consecutive_build_service_disable_threshold-ba461187507bdb43.yaml b/releasenotes/notes/consecutive_build_service_disable_threshold-ba461187507bdb43.yaml
new file mode 100644
index 0000000..11952e9
--- /dev/null
+++ b/releasenotes/notes/consecutive_build_service_disable_threshold-ba461187507bdb43.yaml
@@ -0,0 +1,8 @@
+---
+
+fixes:
+  - |
+    Set consecutive_build_service_disable_threshold to 0
+    as it was observed that some nodes on a cluster were
+    disabled after a certain amount of build failures, overloading
+    the other healthy nodes in the cluster causing a bunch of issues.
diff --git a/roles/openstack_helm_nova/vars/main.yml b/roles/openstack_helm_nova/vars/main.yml
index aa7785d..54f90b5 100644
--- a/roles/openstack_helm_nova/vars/main.yml
+++ b/roles/openstack_helm_nova/vars/main.yml
@@ -86,6 +86,8 @@
         catalog_info: volumev3::internalURL
       conductor:
         workers: 8
+      compute:
+        consecutive_build_service_disable_threshold: 0
       cors:
         allowed_origin: "*"
         allow_headers: "X-Auth-Token,X-OpenStack-Nova-API-Version"