Not all the DNS records are being added when deploying multiple nodes
Bug #1381605 reported by
Raphaël Badin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Raphaël Badin | ||
Bug Description
When deploying multiple nodes in one go, not all of the nodes got a DNS record. Restarting the cluster (which triggers a complete rewrite of the entire DNS config files) solved the problem.
Related branches
lp:~rvb/maas/lock-dns-update
- Andres Rodriguez (community): Approve
- Gavin Panella (community): Approve
-
Diff: 331 lines (+69/-19)10 files modifiedsrc/maasserver/dns/config.py (+5/-0)
src/maasserver/dns/tests/test_config.py (+34/-1)
src/maasserver/locks.py (+3/-0)
src/maasserver/models/tests/test_node.py (+2/-3)
src/maasserver/models/tests/test_timestampedmodel.py (+2/-2)
src/maasserver/rpc/tests/test_monitors.py (+2/-2)
src/maasserver/testing/testcase.py (+2/-2)
src/maasserver/tests/test_third_party_drivers.py (+6/-6)
src/maasserver/utils/dblocks.py (+9/-2)
src/maasserver/views/tests/test_nodes.py (+4/-1)
Revision history for this message
| Christian Reis (kiko) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Raphaël Badin (rvb) |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| milestone: | none → 1.7.0 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Is it very hard to add a test which spins up two threads that can forcibly race through some instrumentation?