Browse Source

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 92dcffc714)
changes/77/775777/1
ramishra 4 months ago
parent
commit
58825e4736
1 changed files with 2 additions and 0 deletions
  1. +2
    -0
      overcloud-resource-registry-puppet.j2.yaml

+ 2
- 0
overcloud-resource-registry-puppet.j2.yaml View File

@ -349,8 +349,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 %}

Loading…
Cancel
Save