Currently the Tracker base class forces the underlying entry to exist when an update method is called.
The underlying entry should not be created silently and the operation should fail if called on non-existent entry.
The issue is present in most of already implemented tracker classes that reimplement the update method.
Metadata Update from @mkubik:
- Issue assigned to someone
- Issue set to the milestone: FreeIPA 4.5 backlog
Can you provide more details on this?
Metadata Update from @rcritten:
- Issue close_status updated to: None
to comment on this ticket.