Recordsets are going in error status.

[selvakumar]

Hi All,
DNSaas: Recordsets are going in error status.
1. Create a zone
2. Create a new recordset
openstack recordset create --records 10.0.0.231 --type A alok.com. server1
3. First Recordset become Active , this recordset can be resolved using nslookup
4. Now delete this record set
5. Now try to create a new recordset
Newly created recordsets are going in error state .
$ openstack recordset list b4d55e71-9c0e-4967-9d37-ad5882ccb19e
----------------------------------------------------------------------------------------------------------+
id name type records status action
----------------------------------------------------------------------------------------------------------+
2a6bb887-b308-4011-8ca5-6b88ae9ea69 alok.com. SOA ns1-1.example.org. ERROR UPDATE
4 hostmaster.alok.com. 1471944276 3573
      600 86400 3600
6041812e-4d99-46e9-91cf- alok.com. NS ns1-1.example.org. ACTIVE NONE
5e3b5048a188 ns1-2.example.org.
f150edeb-6133-4b5f- ns1.alok.com. A 10.0.0.1 ACTIVE NONE
9b13-7a40231d55b6
98e0ddcd-ff05-44fc-952e- akm.alok.com. A 10.0.0.230 ERROR CREATE
dcdc876e428f
7acf44de- server3.alok.com. A 10.0.0.231 ERROR CREATE
ad64-4f39-92a5-bef783afe571
----------------------------------------------------------------------------------------------------------
+
Activity

However I found that mdns sends NOTIFY message to the backend dns server and could not get the reply.

2016-08-26 14:33:56.074 56960 INFO designate.mdns.notify [req-d3ce4d4c-2b97-41c8-96fc-c9425519932c a618ec0fbc744ef6b2ebed81d8d2d461 d7ce7be3bd61442bbf5b556b54780320 - - -] Sending 'NOTIFY' for 'example4.com.' to '127.0.0.1:53'.
2016-08-26 14:33:56.107 56960 INFO designate.mdns.notify [req-d3ce4d4c-2b97-41c8-96fc-c9425519932c a618ec0fbc744ef6b2ebed81d8d2d461 d7ce7be3bd61442bbf5b556b54780320 - - -] Sending 'SOA' for 'example4.com.' to '15.212.221.25:53'.
2016-08-26 14:33:56.111 56960 DEBUG designate.mdns.notify [req-d3ce4d4c-2b97-41c8-96fc-c9425519932c a618ec0fbc744ef6b2ebed81d8d2d461 d7ce7be3bd61442bbf5b556b54780320 - - -] Got lower serial for 'example4.com.' to '15.212.221.25:53'. Expected:'1472222030'. Got:'1472220262'.Retries left='9' get_serial_number /opt/stack/venv/designate-20160815T061034Z/lib/python2.7/site-packages/designate/mdns/notify.py:161

2016-08-26 14:34:11.113 56960 INFO designate.mdns.notify [req-d3ce4d4c-2b97-41c8-96fc-c9425519932c a618ec0fbc744ef6b2ebed81d8d2d461 d7ce7be3bd61442bbf5b556b54780320 - - -] Sending 'SOA' for 'example4.com.' to '15.212.221.25:53'.
2016-08-26 14:34:11.118 56960 DEBUG designate.mdns.notify [req-d3ce4d4c-2b97-41c8-96fc-c9425519932c a618ec0fbc744ef6b2ebed81d8d2d461 d7ce7be3bd61442bbf5b556b54780320 - - -] Got lower serial for 'example4.com.' to '15.212.221.25:53'. Expected:'1472222030'. Got:'1472220262'.Retries left='8' get_serial_number /opt/stack/venv/designate-20160815T061034Z/lib/python2.7/site-packages/designate/mdns/notify.py:161

How to debug the DNS response reachability in the controller ?

Thanks
Selvakumar

[selvakumar (selvakumar-nms)]

only first recordset able to create and goes to ACTIVE and the subsequent record goes to ERROR state.

Got Timeout while trying to send 'NOTIFY' for 'example4.com.' to '127.0.0.1:53'. Timeout='30' seconds. Retry='5'

 openstack recordset list example6.com.
+--------------------------------------+-----------------------+------+---------------------------------------------------+--------+--------+
| id | name | type | records | status | action |
+--------------------------------------+-----------------------+------+---------------------------------------------------+--------+--------+
| afbdebc0-c513-47dd-ba98-de01f7abd763 | example6.com. | SOA | ns1-2.example.org. admin.example6.com. 1472225050 | ERROR | UPDATE |
| | | | 3593 600 86400 3600 | | |
| e202be70-14e2-4e31-8d89-65afd4058b67 | example6.com. | NS | ns1-1.example.org. | ACTIVE | NONE |
| | | | ns1-2.example.org. | | |
| a685dea2-5461-4ee2-8b41-61a5f1107d27 | ns1143.example6.com. | A | 10.0.0.29 | ACTIVE | NONE |
| 6971bc6e-ddf6-4aaa-bf16-e5a8f1436168 | ns11443.example6.com. | A | 10.0.0.30 | ERROR | CREATE |
+--------------------------------------+-----------------------+------+---------------------------------------------------+--------+--------+
stack@helion-cp1-c1-m1-mgmt:/usr/bin$ ^C

[selvakumar (selvakumar-nms)]

one more observation after some times the ERRORed recordset status changed to 'ACTIVE'.

[Murali Annamneni (murali.annamneni)]

I'm also observing the same with stable/queens I had allow-notify configured with 'worker' ip.