Default Zone Changes Not "Sticking"

[ferricoxide]

By default, NetworkManager is assuming partial ownership of eth0:

# nmcli dev
DEVICE  TYPE      STATE      CONNECTION
eth0    ethernet  connected  System eth0
lo      loopback  unmanaged  --

NetworkManager will tell firewalld what zone to use but firewalld won't tell NetworkManager. Upon applying salt states that update the default zone via firewalld, the active firewall state will change. However, at reboot, NetworkManager will revert the default zone. Need add logic to either:

• Wholly disable [expletive-deleted] NetworkManager
• Disable NetworkManager's management of the default interface (set NM_CONTROLLED to "false" in the /etc/sysconfig/network-scripts/ifcfg-<IF> file)
• Ensure that the equivalent of a nmcli connection modify "System eth0" connection.zone drop is run concurrent to the firewalld commands

Down-side to 2nd and 3rd options is that the default interface can vary depending on deployment-type (most cases will be eth0 [2nd bullet] or System eth0 [3rd bullet] but not all cases [mostly physical hosts and some virtalization platforms - like VirtualBox])

[ferricoxide]

@dvu70 have we seen recurrence of issues with zone-stickiness?