Merge lp:~allenap/maas/database-locks-rererevisited into lp:~maas-committers/maas/trunk
Proposed by
Gavin Panella
Status: | Merged |
---|---|
Approved by: | Gavin Panella |
Approved revision: | no longer in the source branch. |
Merged at revision: | 4197 |
Proposed branch: | lp:~allenap/maas/database-locks-rererevisited |
Merge into: | lp:~maas-committers/maas/trunk |
Prerequisite: | lp:~allenap/maas/database-locks-rerevisited |
Diff against target: |
247 lines (+60/-75) 4 files modified
src/maasserver/dns/config.py (+3/-7) src/maasserver/dns/tests/test_config.py (+16/-29) src/maasserver/locks.py (+2/-2) src/maasserver/security.py (+39/-37) |
To merge this branch: | bzr merge lp:~allenap/maas/database-locks-rererevisited |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Blake Rouse (community) | Approve | ||
Review via email: mp+266448@code.launchpad.net |
Commit message
Use non-transactional advisory locks for critical regions of DNS and security activity.
Previously locks were obtained after transactions had begun. This meant that, once the lock was acquired, the transaction may be working with stale data. This causes breakage when dealing with the shared-secret on the filesystem and when writing DNS zones with old data.
To post a comment you must log in.
Looks good as well. No bug for this either?