Description of problem:
On an active overcloud deployment, changes to the nic-template settings on the director are not reflected on the overcloud nodes. The original configuration continues to be pushed out.
Changes to the nic-template settings requires a deletion and redeployment of the overcloud to become effective, which is severely disruptive. Any changes to the network settings
Version-Release number of selected component (if applicable):
This was observed with both OSPD10 and OSPD13
Steps to Reproduce:
1. Start with default nic-template (templates/nic-configs/controller.yaml) suitable for the deployment and deploy the overcloud.
2. Modify the compute or controller nic-template on the director node, eg
change the name of the bridge or the host interface to bridge association
3. Run the deployment update
/etc/os-net-config/element_config.json (OSPD12) or cat /etc/os-net-config/config.json (OSPD10) both contain the same info as pushed in step 1, after step 3.
the os-net-config json config should be updated to the latest.
We have also tried deleting the json config file on the overcloud nodes, but the same, not updated one keeps on being pushed back.
By default network changes take place on the initial deployment. In order to force network changes on a redeploy you need to set the following:
in the parameters_default section of a local network-environment.yaml file.
By default the redeploy does not have the UPDATE flag set and will not update the network settings.
Thanks. With the new setting I'm seeing the update propagate.
How about adding it as default setting in the templates?
Great, thanks for testing. Network updates are disabled by default to avoid issues that may arise from network reconfiguration. For example, when adding an additional compute node we don't want to affect networking to the existing nodes. It must be set to UPDATE when network updates are required.