Side-effect of fixing #5087 is that we now trigger deficiency in the way how FreeIPA handles automatic empty zones. As a result, zones like 10.in-addr.arpa and other reverse zones are not forwarded to the global forwarder as expected (sometimes :-).
Fix is described in
Proposing for 4.3.x because #5087 was done for 4.3.0 so this 4.3+ are affected.
other patches will follow
Patches for ipa-4-3 will come later
Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: FreeIPA 4.3.2
to comment on this ticket.