Friday, 2018-05-04

*** puck has quit IRC00:37
*** puck has joined #openstack-dns00:41
*** diman has joined #openstack-dns04:18
*** diman has quit IRC04:23
*** bauruine has quit IRC05:15
*** Chealion has quit IRC05:15
*** Chealion has joined #openstack-dns05:16
*** bauruine has joined #openstack-dns05:21
*** trungnv has quit IRC06:20
*** pcaruana has joined #openstack-dns06:43
*** diman_ has joined #openstack-dns06:53
*** diman_ has quit IRC10:07
*** diman_ has joined #openstack-dns10:32
*** diman_ has quit IRC10:41
*** caowei has quit IRC10:43
*** pcaruana has quit IRC11:27
*** pcaruana has joined #openstack-dns11:39
*** pcaruana has quit IRC11:59
*** caowei has joined #openstack-dns12:05
*** caowei has quit IRC12:05
*** pcaruana has joined #openstack-dns12:12
*** MarkBaker has quit IRC12:50
*** rfreire has joined #openstack-dns13:03
*** MarkBaker has joined #openstack-dns13:16
rfreireMorning Gringoes! o/13:29
*** MarkBaker has quit IRC13:47
mugsieo/13:50
*** pcaruana has quit IRC15:13
*** b1tsh1ft3r has joined #openstack-dns15:18
b1tsh1ft3rHello all. Running into some issues with designate and powerDNS. It appears designate is looking to make the following SELECT statement when deleting a zone: [SQL: u'SELECT domains.id, domains.designate_id,   and domains.designate_id doesnt exist... in either the designate or designate_pdns database that were created.15:19
b1tsh1ft3rAm i missing something obvious here? Im running ocata release of openstack and used the version avail from the openstack repo along with power dns version 3.4.11 which is what was avail via the repo.  Anyone have any insight as to what might be wrong here?15:20
b1tsh1ft3rFull error can be seen here : http://paste.openstack.org/show/4mpfpwsBH3MOWP5m6FOb/15:22
b1tsh1ft3rThat was seen in the designate worker.log file ^^15:26
rfreireb1tsh1ft3r, o/ !15:28
rfreireb1tsh1ft3r, can you make a paste of your designate.conf ?15:28
rfreireb1tsh1ft3r, oooh boy; bailing out for customer lunch; gimmie a hour and half? Because... friday++ \o/15:30
*** b1tsh1ft3r has quit IRC15:31
rfreireb1tsh1ft3r, if that helps, Designate 3.0.1 here: http://paste.openstack.org/show/720384/15:31
rfreireoh he left15:31
rfreire:-P15:31
* rfreire goes to the chopp time15:32
*** rfreire has quit IRC15:36
*** b1tsh1ft3r has joined #openstack-dns15:41
b1tsh1ft3rrfreire sure!15:42
*** bnemec is now known as beekneemech15:42
b1tsh1ft3r@rfreire http://paste.openstack.org/show/dfa28RJ0PxOSNYuvv811/15:44
*** diman has joined #openstack-dns15:49
mugsieb1tsh1ft3r: how did you create the powerDNS db ?15:51
b1tsh1ft3rUsing powerdns docs. - https://doc.powerdns.com/md/authoritative/howtos/#basic-setup-configuring-database-connectivity15:53
mugsie(did you use designate-manage or use the powerdns provided schema?)15:53
mugsieah15:53
b1tsh1ft3rIm guessing designate-manage powerdns sync <target_id> is whats supposed to be used here in this case?15:53
mugsiehttps://docs.openstack.org/designate/latest/admin/backends/powerdns.html15:53
mugsieyeah15:53
b1tsh1ft3rhmm15:54
mugsieany reason you are using pdns 3.x ?15:54
*** diman has quit IRC15:54
b1tsh1ft3rno tbh. thats just what was avail when i used yum from the repos (running ocata release)15:54
b1tsh1ft3ri did install 4.0.5 and had the same issue, but i figured it had to be either on the designate side or the db schema itself that pdns is hitting15:55
mugsieOK. pdns4 is what we recommend, as we no longer mess with the pdns schema15:55
mugsiewe have a different driver for pdns415:55
b1tsh1ft3rah ok15:55
b1tsh1ft3rso install pdns4 and run designate-manage powerdns sync <pool_id>  ?15:55
mugsiefor pdns4 just install as normal, and follow the pdns docs for the database15:56
mugsiethen follow https://docs.openstack.org/designate/latest/admin/backends/pdns4.html15:56
b1tsh1ft3rSo for pool id... where can i find this?15:57
mugsiedesignate manage pool generate_file --file /tmp/pools.yaml15:58
mugsiethen the ID should be in that output15:59
b1tsh1ft3rExcellent, thank you for your insight16:00
mugsienp16:00
mugsieI am leaving the office now, but if you leave questions here, some of us will try and reply when we are connected :)16:01
b1tsh1ft3rSounds good! Thanks again16:01
*** diman has joined #openstack-dns16:01
*** diman has quit IRC16:10
b1tsh1ft3rmugsie when you mention pdns4 you mean version >= 4.0.x16:25
*** rfreire has joined #openstack-dns16:39
rfreireb1tsh1ft3r, hi!16:39
b1tsh1ft3rHi!16:40
rfreireb1tsh1ft3r, did you get any help?16:40
b1tsh1ft3rI did, however i still have a few questions.16:40
rfreireb1tsh1ft3r, if I can be of help... (which I doubt, but it'sok)16:40
rfreireFire it16:40
b1tsh1ft3rSounds like i need pdns4. i assume this is simple getting pdns verison 4.0.x from pdns site?16:40
rfreireah16:40
b1tsh1ft3ror is this something entirely different?16:40
* rfreire halts and catches fire16:41
*** AlexeyAbashkin has joined #openstack-dns16:43
rfreireb1tsh1ft3r, sorry bud; I have only tested (I'm a end user) the BIND scenarios16:46
rfreire;-/16:46
*** diman has joined #openstack-dns16:57
*** diman has quit IRC17:01
*** b1tsh1ft3r has quit IRC17:09
*** itlinux has joined #openstack-dns17:14
*** b1tsh1ft3r has joined #openstack-dns17:17
b1tsh1ft3rso.... im a little confused with this.17:28
b1tsh1ft3rhttps://docs.openstack.org/designate/latest/admin/backends/pdns4.html17:28
b1tsh1ft3rIs step 2 supposed to be retro-fitted into an existing pools.yaml template?17:28
* rfreire mira17:29
rfreireb1tsh1ft3r, oh I think I know this one17:29
rfreireb1tsh1ft3r, first of all, which OpenStack version?17:29
b1tsh1ft3rocata17:29
rfreirenice.17:29
rfreireis it red hat, suse, ..?17:29
b1tsh1ft3rCentos17:29
rfreirenice, RHT17:29
rfreirecan you get me a17:29
rfreire# rpm -qa | grep designate ?17:30
rfreirejust to see the designate version17:30
* rfreire turns on his Newton environment17:30
b1tsh1ft3rhttp://paste.openstack.org/show/720392/17:30
* rfreire mira17:30
rfreireb1tsh1ft3r, just so I know, did you install Designate by using any recipe?17:31
b1tsh1ft3rnope. just yum install openstack-designate\*17:31
rfreireok, DNSaaS version 4. nice, not too drifted from mine.17:31
rfreireb1tsh1ft3r, take a look at dis:17:31
rfreirehttps://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/dns-as-a-service_guide/17:31
rfreireb1tsh1ft3r, your version is OSP 11, and I have not _tested_ that verison17:31
rfreireBut in re: pools.yaml17:31
rfreireCheck step 2617:32
rfreireb1tsh1ft3r, in step 26, we create /etc/designate/pools.yaml with the suitable content for your system.17:32
rfreireTHEN17:32
rfreirein step 2917:32
rfreiresu -s /bin/sh -c "designate-manage pool update" designate17:33
rfreireIn step 29, it will READ your pools.yaml and UPDATE your database with the new YAML config17:33
b1tsh1ft3rok17:33
rfreireClear? :-)17:33
rfreireDid I help?17:33
b1tsh1ft3rso... would using this as a template (modifed) be an issue?17:33
b1tsh1ft3rhttps://docs.openstack.org/designate/latest/admin/pools.html#managing-pools17:33
b1tsh1ft3rits the only one i can find thats specific to powerdns17:33
rfreireby no means17:33
rfreireCraft yours17:34
rfreireThat one in the kb fitted mine (and my custys, heh)17:34
rfreirebut I pointed you just so you see how to use the yaml file17:34
rfreireso you write it17:34
rfreiredefine it17:34
rfreirerun the designate-manage pool update17:34
rfreireAnd poof, your yml is production.17:34
b1tsh1ft3rhttps://docs.openstack.org/designate/latest/admin/backends/pdns4.html   <--- i was referred to use this for pdns4 back end17:34
b1tsh1ft3rbut appears step 2 of this should fit in the pools.yaml also?17:35
rfreireTry the one which works17:35
rfreire;-D17:35
b1tsh1ft3ror atleast the missing configs (api content)17:35
rfreireb1tsh1ft3r, nutshell:17:35
rfreire1. Write your YAML file (should be /etc/designate/pools.yaml), crafting your values17:36
rfreire2. su -s /bin/sh -c "designate-manage pool update" designate17:36
rfreire<end<17:36
rfreire>17:36
b1tsh1ft3ri assume powerdns and designate should be using separate databses?17:50
rfreireb1tsh1ft3r, does powerdns uses a database?17:50
rfreireI don't know this tool17:50
rfreirebind does not17:50
rfreireif it uses yes, then it should be a different DB :-)17:50
b1tsh1ft3rCalling the designate-manage pool update designate fails17:53
b1tsh1ft3rRemoteError: Remote error: ProgrammingError (pymysql.err.ProgrammingError) (1146, u"Table 'designate.pools' doesn't exist") [SQL: u'SELECT pools.id, pools.created_at, pools.updated_at, pools.version, pools.name, pools.description, pools.tenant_id, pools.provisioner \nFROM pools \nWHERE pools.name = %(name_1)s AND (pools.tenant_id IS NULL OR pools.tenant_id IS NULL) \n LIMIT %(param_1)s'] [parameters: {u'name_1': u'default', u'17:53
rfreirewait17:54
*** pcaruana has joined #openstack-dns17:54
rfreirewait17:54
rfreireand wait17:54
rfreireb1tsh1ft3r, did you run:17:54
rfreiresu -s /bin/sh -c "designate-manage database sync" designate17:54
rfreiresu -s /bin/sh -c "designate-manage pool-manager-cache sync" designate17:55
rfreireafter install?17:55
b1tsh1ft3rdatabase was created (blank database with user and permissions) and designate.conf was configured and then yes i ran the first command which failed with what you see above17:55
rfreireread again17:55
rfreiredesignate-manage database sync17:55
rfreireand17:55
rfreiredesignate-manage pool-manager-cache sync17:55
rfreire--17:56
rfreirethese commands populates the database17:56
*** diman has joined #openstack-dns17:56
rfreireAFTER creating the pool yaml17:56
rfreirethen, it is designate-manage pool update17:56
rfreireso these are three entirely different commands17:56
rfreireb1tsh1ft3r, take a look at this RHT configuration from here: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/dns-as-a-service_guide/#manual_dnsaas_installation17:57
b1tsh1ft3rok so first command worked. 2nd failed17:57
b1tsh1ft3rsu -s /bin/sh -c "designate-manage pool-manager-cache sync" designate17:58
b1tsh1ft3r2018-05-04 13:57:44.527 15130 CRITICAL designate [designate-manage - - - - -] ValueError: Either database url or engine must be provided.17:58
rfreireb1tsh1ft3r, can you make a post of your designate.conf?17:59
*** diman has quit IRC18:00
b1tsh1ft3rhttp://paste.openstack.org/show/dfa28RJ0PxOSNYuvv811/18:02
* rfreire mira18:02
rfreireb1tsh1ft3r, if you want to check mine: https://pastebin.com/0FcYpvSr18:03
rfreireb1tsh1ft3r, ha. Seems that you did not configure the SQL server for your pool manager18:04
rfreiremine:18:04
rfreire--18:04
rfreire[pool_manager_cache:sqlalchemy]18:04
rfreireconnection = mysql+pymysql://designate:Corinthians@172.25.250.79/designate_pool_manager18:04
rfreire--18:04
rfreireyours:18:04
rfreire--18:04
rfreire[pool_manager_cache:sqlalchemy]18:04
rfreire#connection = sqlite:///$state_path/designate_pool_manager.sqlite18:04
rfreire--18:04
rfreireb1tsh1ft3r, follow that Red Hat step by step guide18:05
rfreireReally18:05
rfreireMore things might be missing18:05
rfreireI have triple-checked that document18:05
rfreireand that's good for RHEL/CentOS18:05
*** b1tsh1ft3r has quit IRC18:11
*** AlexeyAbashkin has quit IRC18:30
*** rfreire has quit IRC18:50
*** diman has joined #openstack-dns19:02
*** diman has quit IRC19:06
*** pcaruana has quit IRC19:10
*** rfreire has joined #openstack-dns19:45
*** b1tsh1ft3r has joined #openstack-dns19:59
*** diman has joined #openstack-dns20:00
b1tsh1ft3rIve managed to get pdns and designate somewhat working. Im running into issues still however. When a zone is created from designate dashboard, the worker.log appears to create but on removal it fails attempting to be authorized for the pdns web-server api.20:06
b1tsh1ft3rit states it is un-authorized20:06
b1tsh1ft3r2018-05-04 16:06:38.470 16619 INFO designate.worker.tasks.zone [-] Failed to DELETE zone example.com. on target ec0b70d2-13eb-4a53-b942-0a966b525258 on attempt 9, Error: 401 Client Error: Unauthorized for url: http://127.0.0.1:8081/api/v1/servers/localhost/zones/example.co20:06
rfreireb1tsh1ft3r, hey! o/20:06
rfreireb1tsh1ft3r, alrighto; question; your pdns runs in this very same server?20:07
b1tsh1ft3ryes, its a designate container with designate and pdns installed20:07
rfreire(in the same server as the Designate)20:07
rfreirehrnm okay.20:07
rfreireWhat about the keys20:07
rfreireAre they properly set?20:07
b1tsh1ft3rapi key is defined in pdns.conf20:07
rfreireOkay another question20:08
rfreireWhen you create a zone20:08
rfreireDid you ran some dig tests20:08
rfreirein order to ensure that it was indeed properly created?20:08
*** diman has quit IRC20:08
b1tsh1ft3ryes20:08
b1tsh1ft3rthey come back fine20:08
rfreireHrnm. So your problem now lies on deleting a zone20:08
rfreirewell20:08
rfreire¯\_(ツ)_/¯ now I got clueless :-(20:09
* rfreire does not knows powerdns20:09
rfreireeandersson, ^  ?20:09
rfreiretimsim, ^ ?20:10
timsimAlmost certainly a powerdns config issue "401 Client Error: Unauthorized for url: http://127.0.0.1:8081/api/v1/servers/localhost/zones/example.co". The Designate code calling the powerdns API is getting that error.20:12
rfreireb1tsh1ft3r, ^20:14
b1tsh1ft3ryeah its definately power dns20:15
b1tsh1ft3rthe delete looks like its being triggered by designate for the zone but powerdns is...... not cooperating heh20:15
rfreiredoes a hug help?20:19
* rfreire hugs powerdns20:19
rfreiredid that help?\20:19
mugsieb1tsh1ft3r: I am on a phone, but did you set the pdns config from the page I send earlier?20:20
mugsieThe webserver apikey and the then the same options in the pools.yaml for the server20:20
rfreiremugsie, the key seem to be fine, since it creates the zone20:21
rfreiremugsie, I asked if did he test, and after the zone is created, he tested and the pdns replied accordingly20:22
mugsie:/20:22
rfreiremugsie, the problem seems to be in the deletion20:23
rfreiretheres a commit about delete problems20:23
rfreirebut in the commit, looks like designate fails silently20:24
rfreirecommit defe3a8f29c70dcdb4d271613a3a32dbd3739a5a20:24
rfreireAuthor: Tim Simmons <tim.simmons@rackspace.com>20:24
rfreireDate:   Fri Jan 29 17:21:06 2016 -060020:24
rfreire    Actually poll for zone deletes20:24
rfreire--20:24
rfreire    - This originally failed in PowerDNS, because in older versions20:24
rfreire    that are still in all the distro repos, PDNS responded with a20:24
rfreire    NOERROR and empty answer section when it got a query for a zone20:24
rfreire    it knew nothing about. NEAT.20:24
rfreire    http://blog.powerdns.com/2015/03/02/from-noerror-to-refused/20:24
rfreire--20:24
rfreireBut his version (4.0.0) does contains this commit as well20:25
rfreireSom as timsim told, it might be something in the pdns side.20:25
b1tsh1ft3rIve tried many many guides manually (redhat, openstack docs, openstack-ansible guide). Nothing works with pdns sadly. each one has failed in a similar way. They seem to be able to poll but cannot actually manage20:27
mugsieThat is weird, pdns is one of the DNS servers we test every commit against20:30
mugsie(we test bind9 and pdns4)20:30
b1tsh1ft3ris there any guide for installing specifically with pdns4 or configuring with pdns4 out there? The only ones i see are bind20:39
*** rfreire has quit IRC20:42
*** b1tsh1ft3r has quit IRC20:55
*** diman has joined #openstack-dns20:57
*** diman has quit IRC21:02
*** itlinux has quit IRC21:47
*** brad[] has quit IRC21:50
*** diman has joined #openstack-dns21:54
*** diman has quit IRC21:59
*** abalutoiu_ has joined #openstack-dns22:08
*** abalutoiu__ has quit IRC22:11
*** rfreire has joined #openstack-dns22:17
*** brad[] has joined #openstack-dns22:33
*** rfreire has quit IRC22:55
*** diman has joined #openstack-dns22:59
*** diman has quit IRC23:04

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