Tuesday, 2022-07-19

opendevreviewErik Olof Gunnar Andersson proposed openstack/designate master: Cleaned up and fixed record objects and tests  https://review.opendev.org/c/openstack/designate/+/84983101:23
opendevreviewErik Olof Gunnar Andersson proposed openstack/designate master: Cleaned up and fixed record objects and tests  https://review.opendev.org/c/openstack/designate/+/84983101:24
opendevreviewMerged openstack/designate master: Cleaned up adapter code  https://review.opendev.org/c/openstack/designate/+/84984202:19
opendevreviewErik Olof Gunnar Andersson proposed openstack/designate master: Cleaned up and fixed record objects and tests  https://review.opendev.org/c/openstack/designate/+/84983102:58
opendevreviewErik Olof Gunnar Andersson proposed openstack/designate master: Add basic information to represent DesignateObjects  https://review.opendev.org/c/openstack/designate/+/84984704:20
opendevreviewErik Olof Gunnar Andersson proposed openstack/designate master: Added additional test coverage for adapters  https://review.opendev.org/c/openstack/designate/+/84984804:33
*** tkajinam is now known as Guest543507:14
*** Guest5435 is now known as tkajinam07:36
opendevreviewAndre Aranha proposed openstack/designate stable/wallaby: Change FIPS jobs to centos-9-stream  https://review.opendev.org/c/openstack/designate/+/85033311:39
ozzzo_workeandersson: Here's what I see in designate-api.log: https://paste.openstack.org/show/bSVwBcGWuQGGhrilEOCT/14:15
ozzzo_workI don't see any new entries in designate-central.log when I reproduce the issue14:16
ozzzo_workIn designate-sink.log I see lots of "NameError: name 'ptr_recordset' is not defined" and "designate.exceptions.DuplicateRecord: Duplicate Record"14:23
ozzzo_workExample: https://paste.openstack.org/show/brCAoLhDPsPdY9LG2mIv/14:28
ozzzo_workI'm not sure that this is related to the other symptom, but the initial complaint about this region was that DNS entries were not created for new VMs. When I investigated then i saw the "recordset list" failure14:30
ozzzoWe found that a customer who has tenant networking enabled has huge numbers of entries in the Designate database although they have no active VMs. It appears that, when they delete VMs, the corresponding Designate database entries do not get deleted. This causes the original symptom that the customer reported. I suspect that this deletion failure caused the Designate database to swell to the point where it causes "recordset 14:43
ozzzolist" failures.14:43
ozzzoHow does tenant networking interact with Designate?14:44
ozzzoActually I'm not sure that "huge" is accurate; there are 32K entries in the DB and 16K of them belong to this customer14:44
ozzzoour non-broken region has 3K entries in the same DB14:45
johnsomozzzo That is handled by the neutron DNS extensions. They call the Designate API (in newer versions) or in older versions it puts messages on the messaging bus for Designate.15:01
ozzzowe're on Train; is that using the API?15:02
johnsomI would have to dig in the neutron release notes to see when that switched. However, I did see this that might be related to your issue if you ran train older than 15.2.0: https://bugs.launchpad.net/neutron/+bug/187598115:28
johnsomhttps://docs.openstack.org/releasenotes/neutron/train.html#relnotes-15-2-0-stable-train15:28
opendevreviewMerged openstack/designate master: Remove logic for Python < 3.2  https://review.opendev.org/c/openstack/designate/+/85009216:40
eanderssonozzzo: If you are using the older, sink version it's possible that the notification queue stopped working17:50
eanderssondesignate-sink17:50
eanderssonWhat orchestration are you using? e.g. kolla?17:51
ozzzoyes17:51
ozzzowe're using redhat's RHOSP 16.217:51
eanderssonInteresting error btw. That looks to be something between haproxy and designate17:52
eanderssonMaybe the call is taking too long to return and you have set haproxy to not wait long enough17:52
eanderssonYep that is it17:52
eandersson> time: 61.750123317:52
eanderssonYour haproxy is configured to kill the TCP connection after 60 seconds17:52
eanderssonhttps://stackoverflow.com/questions/32634980/haproxy-closes-long-living-tcp-connections-ignoring-tcp-keepalive17:52
eanderssonI see that you figured out the cause already :D 17:55
ozzzoI think so. We're going to identify and delete the bad entries in the Designate DB and see if that fixes it, then we just have to figure out (and fix) why tenant-networked VM entries are failing to delete when the VM is deleted17:57
ozzzoour other region with tenant networking enabled is less used; it has the same problem but hasn't escalated to the point where "recordset list" fails yet17:58
opendevreviewManish Honap proposed openstack/designate master: Validate matching double quotes in TXT recordsets.  https://review.opendev.org/c/openstack/designate/+/84954118:23

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!