[vDNS]: Records lost on named restart if scaled configuration is present
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Nipa | |||
R2.21.x |
Fix Committed
|
High
|
Nipa | |||
R2.22.x |
Fix Committed
|
High
|
Nipa | |||
R3.0 |
Fix Committed
|
High
|
Nipa | |||
R3.0.2.x |
Fix Committed
|
High
|
Nipa | |||
Trunk |
Fix Committed
|
High
|
Nipa |
Bug Description
BUG Template : Ubuntu
OS version: 3.13.0-40-generic #69-Ubuntu
Contrail Version: 3.0.2.0-38
Setup details:
Multi node setup.
Testbed file attached
Configurations and Description:
As I was having 4 control nodes, I made contrail-dns on 2 control nodes as permanently down to focus the test on rest of the 2 nodes only.
Nodes in test : nodeg12 and nodec28
Step 1: Configured 1 VDNS server
Step 2: Configured 5000 records for that server.
Step 3: Verified that all records are present in zone file for that domain.
Step 4: Stop and Start the contrail-named of nodec28
Step 5: Verified after sometime on node28. Only 1082 records were recovered and rest of the records were lost.
Step 6: Did the same test on nodeg12. The test passed on that node. All 5000 records recovered. (May be as the node types are different.)
Logs:
Server : <email address hidden>
Path: /home/bhushana/
summary: |
- [vDNS0]: Records lost on named restart if scaled configuration is - present + [vDNS]: Records lost on named restart if scaled configuration is present |
information type: | Proprietary → Public |
We will implement an exponential backoff to retry record updates from agent.