From b894347cb91ad34d09288935fbdc1d8390eb1683 Mon Sep 17 00:00:00 2001
From: ramishra <ramishra@redhat.com>
Date: Sat, 13 Feb 2021 11:37:36 +0530
Subject: [PATCH] Always set NetworkDeploymentActions to its default

There are instances users use ``NetworkDeploymentActions`` to
do network configuration during update, but just drop the
parameter for subsequent updates. This sometimes results in
network configuration changes in existing nodes and disruptions.
Let's always set them to defaults unless overridden explicitly.

Change-Id: Ibe7925e4ee568d3d45e138d543b6d7064a8503a3
Related: https://bugzilla.redhat.com/1928055
(cherry picked from commit 92dcffc714bc92a28f610bf0322f04551aade758)
---
 overcloud-resource-registry-puppet.j2.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/overcloud-resource-registry-puppet.j2.yaml b/overcloud-resource-registry-puppet.j2.yaml
index de87d38149..bd762b43e1 100644
--- a/overcloud-resource-registry-puppet.j2.yaml
+++ b/overcloud-resource-registry-puppet.j2.yaml
@@ -366,8 +366,10 @@ parameter_defaults:
   ContainerCli: podman
   EnablePackageInstall: false
   SoftwareConfigTransport: POLL_TEMP_URL
+  NetworkDeploymentActions: ['CREATE']
 
 {% for role in roles %}
   # Parameters generated for {{role.name}} Role
   {{role.name}}Services: {{role.ServicesDefault|default([])}}
+  {{role.name}}NetworkDeploymentActions: []
 {% endfor %}