Comment 1 for bug 1635415

If you see network configuration parameters which resemble to network isolation in network configuration tab, it means that default environment (overcloud-resource-registry-puppet.j2.yaml) references templates which already define those parameters. This might be the problem, but it needs to get resolved in the templates.

About the defaults for network configuration parameters - when you look at templates reefrenced in network-configuration.yaml, you can see, that their default value is set to ''. Which is what GUI displays when you enable network isolation. AFAIK, it is expected that in addition to network-isolation, user also enables additional environments from the 'Single NIC or Bonding group' when you do this, you can see how the parameters get populated with default values in 'Network Configuration' tab.

The conclusion should IMHO be that to achieve the desired behavior, we need to make sure, the environments and templates are better structured. The environment dependency problem has been discussed on Barcelona Summit and plan is to improve this. Although, the root of the problem seems to be in isolation parameters being defined in templates referenced by default environment.