Thursday, 2017-07-06

trungnvarbaindu, did you solve your issue?00:53
trungnvarbaindu, BIND backend which you need to provide permission for them00:54
trungnvStderr: u"rndc: 'addzone' failed: permission denied\n -------------- this is issue.00:54
trungnvarbaindu, pls perform these command: # chown bind:bind /etc/rndc.key and # chmod 644 /etc/rndc.key00:55
arbaindutrungnv: i fixed that issue, permissioned were wrong on /var/named00:56
arbainduchown named /var/named fixed it00:56
trungnvyep. sure00:56
arbaindubut i still see issue with zones/records remainging in PENDING state for a long time, until i finally see worker displaying that WARNING above00:57
trungnvdepend on your config for BIND then you take permission for them where they located.00:57
arbaindui am eventually able to verify DNS behavior - created a test record on a test zone (pointing to some remote VM IP of mine), and on same host as i'm running bind, set /etc/resolv.conf to 127.0.0.100:58
arbainduwas able to ping and resolve it via the test.testdomain.net00:58
trungnvperhaps you have a lot of record on DB then worker will call mdns to check them.00:58
arbaindubut it took a long time for zone and record to actually become ACTIVE00:58
trungnvhow many zone record in SQL?00:59
arbaindujust 100:59
trungnvLet's check with new zone?01:01
arbainduI have API/central/producer on one host (controller), same as DB.01:01
arbainduOn another host, I have worker and mdns running. I'm running bind9/named here, on localhost (127.0.0.1)01:02
arbaindujust for testing purposes for now01:02
trungnvwhy did you setup all designate service on 1 Node and remain Node for BIND?01:03
trungnvwhy didn't you setup all designate service on 1 Node and remain Node for BIND?01:03
arbaindueventually, only 1 host or some hosts may have access to backend DNS server01:03
arbaindueg, for example a network node01:03
arbaindumdns and worker need the host to have access to this subnet, right?01:04
arbainduthe rabbit connections between the services are working - openstack dns service list lists all of em as UP01:06
trungnvonly 1 rabbitmq-server. is right?01:08
arbainduin a neutron environment, we might have a network node that hosts SNAT for dvr, dhcp agent, legacy routers, etc... this host would have access to DNS backend01:08
arbainduyea01:08
arbainduhere is pools.yaml:01:08
arbainduwhere i defined a testdomain, and specified nameserver as 127.0.0.1 (since that's where bind is located on, for worker/mdns to connect to)01:09
arbainduhttps://gist.github.com/xagent003/5874e4cc82be46fbc9c42b0e5173a76f01:09
arbainduNo zones currently, I just created 1:01:10
arbainduopenstack zone create --email dnsmaster@testdomain.net testdomain123.net.01:10
trungnvI saw that you setup BIND and mdns both on the same VM. right?01:11
trungnvmasters: - host: 127.0.0.1 -port: 535401:12
trungnvthis config to mdns read BIND in local.01:12
trungnvif you separate them then you must change this config.01:13
arbainducorrect - both services are running on same hypervisor (which is a VM)01:14
trungnvand on BIND, are you accept 53 port to LISTEN on this?01:14
arbaindufor now i am just attemtping to validate designate behavior01:14
arbainduthe bind is working as mentioned. i created a zone/record and it *eventually* gets populated, and i am able to resolve my hostname01:15
arbaindufor example from that same host, i set /etc/resolv.conf nameserver to 127.0.0.101:15
arbainduthen from that host i did ping www.testdomain123.net01:15
arbaindufor which i added a record pointing to my laptop's IP01:15
trungnvyep.01:16
arbainduthe issue is worker/mdns is taking a long time to actually add these records01:16
arbaindui am tailing worker.log, and i see nothing01:16
arbainduI only see following period logs in worker:01:17
arbaindu2017-07-05 21:15:13.100 16262 DEBUG designate.plugin [-] Looking for driver sqlalchemy in designate.storage get_driver /usr/lib/python2.7/site-packages/designate/plugin.py:115 2017-07-05 21:15:13.102 16262 DEBUG designate.plugin [-] Loaded plugin storage:sqlalchemy __init__ /usr/lib/python2.7/site-packages/designate/plugin.py:39 2017-07-05 21:15:13.206 16262 DEBUG designate.worker.processing [req-d59833cb-1614-453d-ab60-be1ac1e01:17
arbainduonly after a long time, i finally seee the WARNING about PENDING for 455 seconds, then i see the DNS queries / rdnc commands being executed01:17
trungnvon the worker log still nothing when DNS query done?01:19
arbainduno, it takes a long time for it to be done:01:20
arbainduworker does nothing. then I see WARNING Found 1 zones PENDING for more than 455 seconds01:20
arbainduand immediately after i see the Attempting CREATE zone testdomain123.net.01:20
arbainduand Executing RNDC call01:20
arbaindubut worker is idle for nearly 10 minutes before that01:20
arbainduhttps://gist.github.com/xagent003/f03230d788dd66d6f7c9ce42d859ee4501:22
arbainduworker logs ^^01:22
arbaindutrungnv: notice that the actual attempts by worker to CREATE the zone, and issue the rndc calls took place at 21:19:1301:23
arbaindui created the zone at time 21:10:0901:23
trungnvarbaindu, please try with new zone to check issue again? because if you separate designate services on both Node then they also have some issues with no_proxy, host name, iptable etc01:23
arbainduso, it took about 9 minutes for zone to actually get populated in bind01:24
arbainducreating a record now: openstack recordset create --records '10.4.165.22' --type A testdomain123.net. www01:24
arbainduat time 21:24:3501:25
trungnvyep01:25
arbaindutrungnv: i tried with new zone, this was abbout the 5th zone i created/deleted01:25
arbainduworker logs are now just idle, but recordset still PENDING01:26
trungnvpls check log central?01:27
arbainduhere are logs from central: https://gist.github.com/xagent003/d096e9b1d1e1b61f4b766b6598387b5501:27
arbainduit indicates "Queueing notification for dns.recordset.create" and "Emitting dns.recordset.create notification "01:27
arbaindui did notice this:01:28
arbainduDEBUG designate.pool_manager.rpcapi [req-03f13197-4e9b-4d7c-8215-99d267261cea 5f280602772643e6a8a25900575ab11d c613941e66b247afac342cb5a11d3aca - - -] Calling designate.pool_manager.update_zone() over RPC wrapped /usr/lib/python2.7/site-packages/designate/loggingutils.py:2401:28
arbaindugiven that i have enabled service:worker, and i have producer service running as well, why is there a log from pool_manager?01:28
arbainduor is it just a misnomer?01:28
trungnvsure. if you enable worker then pool_manger going to down.01:30
arbainducorrect - then why that log about pool_manager.update_zone()?01:30
arbainduI was wondering if that had something to do with why my worker service is taking so long to actually create or update the zone/record01:30
trungnvpls show designate serivces at the moment? what are currently services?01:31
trungnvapi - central - worker -producer -agent - mdns. right?01:31
arbainduon controller node: api, central, producer01:31
arbainduon a hypervisor/network node: worker, mdns01:31
arbainduin /etc/designate/designate.conf (on both controller and hypervisor nodes), in the service:worker section, I have set enabled = True and notify = True01:32
arbainduopenstack dns service list displays all services - api, central, producer, worker, mdns - as UP01:32
trungnvon controller node pls check via ps -aux | grep designate.01:33
openstackgerritOpenStack Proposal Bot proposed openstack/designate-dashboard master: Updated from global requirements  https://review.openstack.org/48078201:33
trungnvif you can, let's stop pool-manager and zone-manager then check with new zone.01:34
arbainduhttps://gist.github.com/xagent003/d710d4808ba7755be1ad8f66c502589801:34
arbaindupool-manager and zone-manager services are not running. i never enabled them, nor started the services, nor are they running01:35
trungnvdid you try with service designate-pool-manager stop?01:36
trungnvI am not sure why pool-manger log in here.01:36
arbainducan you explain exactly what the workflow is when i create a zone?01:39
trungnvyep.01:39
arbaindui am a little unclear on what the producer does, or how the worker is supposed to get this information to issue the rndc calls to actually CREATE it01:40
arbaindualso when i create a recordset01:40
trungnvwith ocata version, api - central - worker - backend driver (agent) -calling to mdns.01:40
arbaindui understand what goes on between worker/mdns/the actual backend DNS via the notify and DNS transfers01:41
arbaindubut not the central-producer-worker communiucation01:41
arbaindufyi we are using Newton01:41
arbaindufor example i create a record - is central supposed to send a RPC call to worker to create this in backend? Or does producer send RPC call to worker?01:44
arbainduOr is it the worker that's supposed to initiate this via scanning the DB or doing some type of sync/periodic update? the docs mention for worker, "Is a generic task runner, that runs both zone create / update and deletes, and periodic tasks, from designate-producer"01:46
trungnvcentral call to worker to worker connect to backend via backend driver then worker will call mdns.01:47
trungnvI am not sure why you can setup designate-worker on newton package.01:48
trungnvVersion '1:2.0.0-0ubuntu1' for 'designate-worker' was not found01:48
*** cuongnv has joined #openstack-dns01:49
arbainduwhere are you seeing that was not found?01:52
arbaindui am able to setup designate-worker. the services is running fine on the host01:53
arbainduas mentioned, it eventually does add the zone or record. it just doesn't do it triggered by central, but only after the "WARNING designate.worker.tasks.zone [-] Found 1 zones PENDING for more than 455 seconds"01:54
arbainduso the "central call to worker" seems to not be working01:54
arbainduWhat does the producer do in this case?01:54
trungnvyep. your behavior is right.01:54
trungnvwhich version, 1:2 is mitaka version. from 1:3 we have worker and producer on it.01:57
trungnvcentral and worker have issue with  when they communicate difference host.01:59
trungnvLet's check no_proxy, network on them.02:00
openstackgerritNgo Quoc Cuong proposed openstack/designate master: Remove log translations  https://review.openstack.org/44782502:31
arbainduwhat's no_proxy and network?02:40
arbaindutrungnv: where are these set?02:40
arbainduwe havent seen any problems via RPC (using rabbitmq) and other controller-side services talking to host-side services (such as neutron-server talking to ovs-agent or l3-agent)02:42
*** cuongnv has left #openstack-dns02:44
*** renmak_ has joined #openstack-dns02:47
*** renmak__ has joined #openstack-dns02:47
*** arbaindu has quit IRC03:06
*** Krenair has quit IRC05:24
*** Krenair has joined #openstack-dns05:31
*** therve has quit IRC05:44
*** therve has joined #openstack-dns05:46
*** baffle has quit IRC06:03
*** baffle has joined #openstack-dns06:03
*** abalutoiu has joined #openstack-dns07:02
*** KeithMnemonic2 has joined #openstack-dns07:12
*** abalutoiu_ has joined #openstack-dns07:12
*** KeithMnemonic1 has quit IRC07:15
*** abalutoiu has quit IRC07:16
openstackgerritNgo Quoc Cuong proposed openstack/designate master: Remove log translations  https://review.openstack.org/44782507:31
*** egonzalez has joined #openstack-dns07:50
*** renmak__ has quit IRC07:54
*** renmak_ has quit IRC07:54
*** MarkBaker has joined #openstack-dns08:03
*** cvstealt1 has joined #openstack-dns08:17
*** cvstealth has quit IRC08:18
*** abalutoiu_ is now known as abalutoiu08:26
*** abalutoiu has quit IRC09:13
*** abalutoiu has joined #openstack-dns09:41
*** chlong_ has joined #openstack-dns12:37
*** catintheroof has joined #openstack-dns13:25
*** catintheroof has quit IRC13:36
*** catintheroof has joined #openstack-dns13:37
*** renmak__ has joined #openstack-dns13:41
*** renmak_ has joined #openstack-dns13:41
*** MarkBaker has quit IRC14:35
*** catintheroof has quit IRC14:58
*** renmak__ has quit IRC14:59
*** renmak_ has quit IRC14:59
*** catintheroof has joined #openstack-dns15:02
*** renmak_ has joined #openstack-dns15:02
*** renmak__ has joined #openstack-dns15:02
*** MarkBaker has joined #openstack-dns15:08
*** renmak__ has quit IRC15:13
*** renmak_ has quit IRC15:13
*** renmak_ has joined #openstack-dns15:14
*** renmak__ has joined #openstack-dns15:14
*** renmak__ has quit IRC15:33
*** renmak_ has quit IRC15:33
*** renmak_ has joined #openstack-dns15:37
*** renmak__ has joined #openstack-dns15:37
*** MarkBaker has quit IRC15:52
*** egonzalez has quit IRC16:05
*** MarkBaker has joined #openstack-dns16:06
*** abalutoiu has quit IRC17:21
*** hieulq has quit IRC17:33
*** daidv has quit IRC17:33
*** trungnv has quit IRC17:33
*** daidv has joined #openstack-dns17:48
*** hieulq has joined #openstack-dns17:48
*** trungnv has joined #openstack-dns17:48
*** MarkBaker has quit IRC17:54
*** MarkBaker has joined #openstack-dns18:07
*** abalutoiu has joined #openstack-dns18:12
*** hieulq has quit IRC18:51
*** daidv has quit IRC18:51
*** trungnv has quit IRC18:51
*** cliles_ has quit IRC18:52
*** cliles has joined #openstack-dns18:52
*** daidv has joined #openstack-dns19:06
*** hieulq has joined #openstack-dns19:06
*** trungnv has joined #openstack-dns19:07
*** abalutoiu has quit IRC19:11
*** pcaruana has quit IRC19:12
*** renmak__ has quit IRC19:13
*** renmak_ has quit IRC19:13
*** KeithMnemonic2 has quit IRC19:35
*** KeithMnemonic has joined #openstack-dns19:36
*** renmak_ has joined #openstack-dns19:45
*** renmak__ has joined #openstack-dns19:45
*** daidv has quit IRC20:21
*** hieulq has quit IRC20:21
*** trungnv has quit IRC20:23
*** daidv has joined #openstack-dns20:36
*** trungnv has joined #openstack-dns20:36
*** hieulq has joined #openstack-dns20:37
*** renmak__ has quit IRC20:41
*** renmak_ has quit IRC20:41
*** renmak_ has joined #openstack-dns21:48
*** renmak__ has joined #openstack-dns21:48
*** hieulq has quit IRC21:53
*** daidv has quit IRC21:53
*** trungnv has quit IRC21:53
*** catintheroof has quit IRC21:55
*** trungnv has joined #openstack-dns22:08
*** daidv has joined #openstack-dns22:08
*** hieulq has joined #openstack-dns22:08
*** abalutoiu has joined #openstack-dns22:44
*** kbyrne has quit IRC23:14
*** daidv has quit IRC23:24
*** hieulq has quit IRC23:24
*** trungnv has quit IRC23:24
*** trungnv has joined #openstack-dns23:40
*** hieulq has joined #openstack-dns23:40
*** daidv has joined #openstack-dns23:40
-openstackstatus- NOTICE: nb03.openstack.org has been cleaned up and rebooted, and should return to building rotation23:43
*** renmak__ has quit IRC23:54
*** renmak_ has quit IRC23:54
*** renmak_ has joined #openstack-dns23:55
*** renmak__ has joined #openstack-dns23:55

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