Wednesday, 2019-01-30

*** jpward1981 has quit IRC03:04
*** jpward1981 has joined #openstack-dns03:24
*** pcaruana has joined #openstack-dns08:10
*** bnemec has joined #openstack-dns08:31
*** salmankhan has joined #openstack-dns10:55
*** salmankhan has quit IRC11:10
*** salmankhan has joined #openstack-dns11:22
*** salmankhan has quit IRC11:35
*** salmankhan has joined #openstack-dns11:51
*** ginopc has joined #openstack-dns12:12
*** pcaruana has quit IRC13:50
*** pcaruana has joined #openstack-dns13:57
*** jpward1981 has quit IRC14:28
*** jpward1981 has joined #openstack-dns14:29
*** my_nd has joined #openstack-dns14:46
*** jpward1981 has quit IRC14:47
my_ndHi there, Im working in a multi node openstack production environment (pike) with Designate (master) and PowerDNS (slaves) but when configuring multiple instances sequentially (10 to 20 instances).  Some of the records (A or PTR) are not created and it throws an error. Looking in PowerDNS logs "I found Unable to retrieve SOA for X.X.X.in-addr.arpa, this was the first time" and in mdns logs I got "2019-01-30 09:54:04.979 22 WAR15:50
my_ndnd in mdns logs I got "2019-01-30 09:54:04.979 22 WARNING designate.service [req-df416ff6-1478-4fa4-8fb0-40c9ecff5af4 - - - - -] Invalid packet from: Y.Y.Y.Y:61715: error: unpack requires a string argument of length 2". Sometimes it gets stable and configure all the records without error.  hope you can help with some information.15:51
fricklermy_nd: IIRC we had a fix for the mdns warning some time ago, which version of pike are you using? it should also be cosmetical only15:53
fricklermy_nd: for the first error, did you configure synchronization if you are running multiple controller nodes?15:54
*** pcaruana has quit IRC16:01
my_ndfrickler for the first error I didnt configure a parameter related with "synchronization" when deploying. is this configuration related with this link? https://docs.openstack.org/designate/latest/admin/samples/config.html16:06
fricklermy_nd: no, have a look at the "backend_url" parameter here https://docs.openstack.org/designate/latest/admin/ha.html#designate-producer16:09
fricklermy_nd: though I'm only guessing that that might be related to your issue16:09
fricklermy_nd: it's as likely that we just have a bug when doing bulk updates16:10
my_ndfrickler ok, because for few recordset creations I didnt see errors. But this deployment is for production so the customer would expect scenarios where creating multiple instances at the same time. For now, Im going to take a look to the link you sent me. Thanks!16:13
fricklermy_nd: please open a bug report on launchpad if you keep getting this issue16:14
my_ndthanks frickler!16:15
*** pcaruana has joined #openstack-dns16:17
*** salmankhan1 has joined #openstack-dns16:27
*** salmankhan has quit IRC16:28
*** salmankhan1 is now known as salmankhan16:28
*** pcaruana has quit IRC16:45
*** bnemec has quit IRC17:14
*** salmankhan1 has joined #openstack-dns17:27
*** salmankhan has quit IRC17:28
*** salmankhan1 is now known as salmankhan17:28
*** ginopc has quit IRC17:54
*** salmankhan has quit IRC18:10
*** pcaruana has joined #openstack-dns18:17
*** salmankhan has joined #openstack-dns20:21
*** salmankhan1 has joined #openstack-dns20:23
*** salmankhan has quit IRC20:25
*** salmankhan1 is now known as salmankhan20:25
*** salmankhan1 has joined #openstack-dns21:16
*** salmankhan has quit IRC21:16
*** salmankhan1 is now known as salmankhan21:16
*** salmankhan has quit IRC21:23
my_ndhi, is it necessary to have designate-producer service in a multinode openstack environment? I deployed openstack pike with kolla ansible but I didnt see this service created21:48

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!