Bug 1008256
| Summary: | backend txn plugin fixup tasks should be done in a txn | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Nathan Kinder <nkinder> |
| Component: | 389-ds-base | Assignee: | mreynolds |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Sankar Ramalingam <sramling> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | mkubik, mreynolds, nsoman, rmeggins |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.1.6-5.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Adding a task entry to the server, like the task created by running the fixup-memberof.pl script.
Consequence: The task was not being done inside a transaction(if using backend transactions), and would not revert any updates if there was a failure.
Fix: Perform the updates issued by the task inside a backend transaction.
Result: The task operations perform as expected during success or failure.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 10:59:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Nathan Kinder
2013-09-16 02:03:45 UTC
Can this be verified on 389-ds-base environment? or only with IPA? Can this be verified on 389-ds-base environment? or only with IPA? This did not fix anything. We just made sure all the plugin tasks are run inside a transaction. It was originally hoped that this change would solve a deadlock issue with IPA/slapi-nis. However, even with this change, that deadlock is still occurring. (In reply to mreynolds from comment #3) > This did not fix anything. We just made sure all the plugin tasks are run > inside a transaction. It was originally hoped that this change would solve > a deadlock issue with IPA/slapi-nis. However, even with this change, that > deadlock is still occurring. Does it mean the bug is still not fixed or its a known issue? (In reply to Sankar Ramalingam from comment #5) > (In reply to mreynolds from comment #3) > > This did not fix anything. We just made sure all the plugin tasks are run > > inside a transaction. It was originally hoped that this change would solve > > a deadlock issue with IPA/slapi-nis. However, even with this change, that > > deadlock is still occurring. > > Does it mean the bug is still not fixed or its a known issue? No, it is fixed on DS, but we had hoped this DS fix would resolve an issue IPA was seeing(but it did not help IPA). Please add steps to verify this in IPA (In reply to Namita Soman from comment #7) > Please add steps to verify this in IPA There are no steps to verify this. It was a proactive change in the DS code. It was added in hopes of fixing an issue with slapi-nis. Even though it did not help with the slapi-nis issue, the code change was still appropriate to commit even though it didn't fix anything. (In reply to mreynolds from comment #8) > (In reply to Namita Soman from comment #7) > > Please add steps to verify this in IPA > > There are no steps to verify this. It was a proactive change in the DS > code. It was added in hopes of fixing an issue with slapi-nis. Even though > it did not help with the slapi-nis issue, the code change was still > appropriate to commit even though it didn't fix anything. Correct. This should be verified by sanity testing only. Sanity test/acceptance run against 389-ds-base-1.3.1.6-18.el7 doesn't seem to indicate regressions. Marking verified (sanity only) as per Sankar's instructions. This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |