Description of problem:
zone bindings are not recreated on reload, if they are managed by NM. This bug was introduced with new option FlushAllOnReload set to default 'yes'.
Interfaces configured to be bound to specific zones internally in firewalld are not impacted. (zone.xml file). This binding type is not default as NM is usually running and let to manage those bindings.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
(optionally set up 'br' interface and binding in zone.xml)
have NM and firewalld up
interface 'eth0' is not bound to any zone (default) on reload
interface contained within internal configuration gets loaded
all interfaces NM/non-NM managed that are present on service start are also present after reload
cd97204a06f3 ("fw: on reload() retain interfaces from NetworkManager")
blocker+ per Dec 13th blocker meeting
Additional upstream commit:
2c003eefff31 ("fw: On reload, when restoring NM interfaces also consider default zone")