The offending commit that introduced the undesired behaviour is present also in ipa-4-4, shouldn't we then re-triage to 4.4.4 Milestone?
meanwhile pushing to master:
Metadata Update from @simo: - Issue assigned to simo - Issue set to the milestone: FreeIPA 4.5
@simo / @mbabinsk is ticket fixed or we are waiting for something?
Metadata Update from @pvoborni: - Issue close_status updated to: None
Metadata Update from @mbasti: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.