#3415 [RFE] Enclose DNS operations in LDAP transaction
Closed: wontfix 5 years ago Opened 11 years ago by pspacek.

E.g. adding a new DNS zone is compound from two writes to separate LDAP objects.

The database is in invalid state in time between those steps and this invalid state affects bind-dyndb-ldap. (See bind-dyndb-ldap ticket #102)

Enclosing all steps in single LDAP transaction should solve this and similar problems.

Transactions could be handy e.g. if user with own private group is being created and so on.

389 has some support for transactions internally, but transaction control is not visible to clients at the moment (AFAIK). 389 ticket is needed for addressing this deficiency.


Moving my tickets back to free-to-take pool.

Metadata Update from @pspacek:
- Issue assigned to someone
- Issue set to the milestone: Ticket Backlog

7 years ago

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata