Browse Source

Introduce execution restriction on nsx-t-neutron-network-create task

Deployment task nsx-t-neutron-network create make two tenant networks
that are used for OSTF checks (test launch instances in internal network
and verify that VMs can successfulyy reach each other and external IP
addresses).

Root cause of the problem is that if we try to create networks twice
(run deployment task two times) it will fail with error that
"physical_network_type does not support being update". It is not
possible to run this task twice, to avoid such behaviour YAQL condition
prevents task from being run no more than one time. Task is executed
only when 'quantum' value (which determines that Neutron is enabled for
current environment) is changed, which should not happen during normal
operation (it is possible to switch this setting via fuel CLI, but not
through web UI).

Change-Id: Idd3000cdec0ef0c990c352d2cb7814fb4743d6f2
Closes-bug: #1626927
master
Igor Zinovik 2 years ago
parent
commit
42e87317d6
1 changed files with 3 additions and 1 deletions
  1. 3
    1
      deployment_tasks.yaml

+ 3
- 1
deployment_tasks.yaml View File

@@ -247,7 +247,7 @@
247 247
     timeout: 120
248 248
 
249 249
 - id: nsx-t-neutron-network-create
250
-  version: 2.0.0
250
+  version: 2.1.0
251 251
   type: puppet
252 252
   groups:
253 253
     - primary-controller
@@ -257,6 +257,8 @@
257 257
     - nsx-t-primary-neutron-server-start
258 258
     - nsx-t-configure-agents-dhcp
259 259
     - primary-openstack-network-agents-metadata
260
+  condition:
261
+    yaql_exp: "changed($.quantum)"
260 262
   parameters:
261 263
     puppet_manifest: puppet/manifests/neutron-network-create.pp
262 264
     puppet_modules: puppet/modules

Loading…
Cancel
Save