Tuesday, 2018-07-31

« Monday, 2018-07-30 Index Wednesday, 2018-08-01 »
*** livelace has quit IRC00:30
*** livelace has joined #openstack-dns00:30
*** khushbu has joined #openstack-dns00:57
*** khushbu has quit IRC01:01
*** khushbu has joined #openstack-dns01:36
*** khushbu has quit IRC01:40
*** gongysh has joined #openstack-dns02:56
*** khushbu has joined #openstack-dns03:07
*** khushbu has quit IRC03:11
*** trungnv has quit IRC03:57
*** trungnv has joined #openstack-dns03:57
*** jmccrory has quit IRC04:09
*** gongysh has quit IRC04:11
*** jmccrory has joined #openstack-dns04:13
*** khushbu has joined #openstack-dns04:18
*** khushbu has quit IRC04:20
*** khushbu has joined #openstack-dns04:24
*** abaindur has joined #openstack-dns04:27
abaindurhello, we are running into some problems with neutron integration04:27
*** abaindur has quit IRC04:29
*** abaindur has joined #openstack-dns04:30
abaindurWe see neutron driver invoking recordset.create in the driver, and it has the correct dns_domain. But Designate is returning a 404 and a DNSDomainNotFound exception04:30
abaindurI verified that I am able to do a zone show on the same dns_domain it is being invoked in04:30
abaindurI was also able to make the exact same API call I see designate-api receiving: 2018-07-31 00:46:02.628 7623 INFO eventlet.wsgi [-] 127.0.0.1 - - [31/Jul/2018 00:46:02] "GET //zones?name=neutron1073.example.sys. HTTP/1.1" 404 342 0.00085704:31
abaindurwhen I manually curl GET https://localhost/designate/v2/zones?name=neutron1073.example.sys. it works04:32
abaindurAny idea why the zone is being returned as not found to neutron, when it clearly exists and we've created manual records in it via Designate directly?04:33
*** khushbu has quit IRC05:03
*** khushbu has joined #openstack-dns05:06
*** khushbu has quit IRC05:20
*** khushbu has joined #openstack-dns05:26
*** khushbu has quit IRC05:27
*** khushbu has joined #openstack-dns05:31
*** gongysh has joined #openstack-dns05:34
*** pcaruana has joined #openstack-dns06:37
*** peereb has joined #openstack-dns07:10
*** gongysh has quit IRC07:21
*** khushbu has quit IRC07:29
*** AlexeyAbashkin has joined #openstack-dns07:42
*** khushbu has joined #openstack-dns07:48
*** khushbu has quit IRC08:12
*** khushbu has joined #openstack-dns08:15
*** gongysh has joined #openstack-dns08:19
*** abaindur has quit IRC08:22
*** khushbu has quit IRC08:30
*** khushbu has joined #openstack-dns08:34
*** salmankhan has joined #openstack-dns08:54
*** khushbu has quit IRC09:32
*** khushbu has joined #openstack-dns09:32
*** khushbu has quit IRC09:51
mugsieandrewbogott: if you add multiple masters to the pools.yaml it should tell pdns to get updates from both minidns servers09:58
mugsieadaindur - you have gone offline - but are the port and zone owned by the same project?09:58
*** khushbu has joined #openstack-dns10:02
*** gongysh has quit IRC10:23
*** khushbu has quit IRC10:29
*** khushbu has joined #openstack-dns10:31
*** trungnv has quit IRC10:49
*** trungnv has joined #openstack-dns10:50
*** khushbu has quit IRC10:56
*** khushbu has joined #openstack-dns10:56
*** salmankhan has quit IRC11:06
*** salmankhan has joined #openstack-dns11:17
*** khushbu has quit IRC11:31
*** khushbu has joined #openstack-dns11:31
*** rfreire has joined #openstack-dns11:43
*** ginopc has joined #openstack-dns11:58
*** khushbu has quit IRC12:09
*** ginopc has quit IRC12:15
*** khushbu has joined #openstack-dns12:39
*** rfreire has quit IRC12:44
*** briner has joined #openstack-dns12:51
*** briner has quit IRC13:01
*** bnemec has joined #openstack-dns13:24
*** khushbu has quit IRC13:32
*** trondham has quit IRC13:43
*** trondham1 has quit IRC13:43
andrewbogottmugsie: I can work around the problem by adding the IPs of both minidns servers in the pdns database, like so:13:52
andrewbogotthttps://www.irccloud.com/pastebin/0EGdEoQi/13:52
andrewbogottIs that what designate should be doing already?13:53
andrewbogottor is it supposed to set up supermasters or something else?13:54
*** trondham has joined #openstack-dns13:59
*** trondham1 has joined #openstack-dns13:59
*** rfreire has joined #openstack-dns14:02
mugsieandrewbogott: yeah, designate should be doing that - we dont use supermasters (as there is no way to delete the zone if we do that_14:24
andrewbogottmugsie: ok, let me sanitize my .yaml file and you can tell me what I'm doing wrong :)14:25
andrewbogottCurrently I'm applying this exact same file on both of my designate hosts:14:26
andrewbogotthttps://www.irccloud.com/pastebin/5r4tTY5L/14:26
*** khushbu has joined #openstack-dns14:29
*** khushbu has quit IRC14:33
*** KeithMnemonic has joined #openstack-dns14:54
*** briner has joined #openstack-dns14:55
*** peereb has quit IRC15:06
*** pcaruana has quit IRC15:10
*** ginopc has joined #openstack-dns15:20
mugsieandrewbogott: http://paste.openstack.org/show/726951/15:30
mugsiesorry, was stuck on the phone15:30
andrewbogottAh!  That makes sense15:30
andrewbogottI'm in a meeting but will give it a go shortly.  Thank you :)15:30
mugsienp15:31
*** briner has quit IRC16:07
*** salmankhan has quit IRC16:37
*** AlexeyAbashkin has quit IRC16:47
*** ginopc has quit IRC17:32
*** salmankhan has joined #openstack-dns18:29
*** salmankhan has quit IRC18:33
*** abaindur has joined #openstack-dns18:39
abaindurhello, we are running into some problems with neutron integration18:40
abaindurWe see neutron driver invoking recordset.create in the driver, and it has the correct dns_domain. But Designate is returning a 404 and a DNSDomainNotFound exception18:40
abaindurI verified that I am able to do a zone show on the same dns_domain it is being invoked in18:40
abaindurI was also able to make the exact same API call I see designate-api receiving: 2018-07-31 00:46:02.628 7623 INFO eventlet.wsgi [-] 127.0.0.1 - - [31/Jul/2018 00:46:02] "GET //zones?name=neutron1073.example.sys. HTTP/1.1" 404 342 0.00085718:40
abaindurwhen I manually curl GET https://localhost/designate/v2/zones?name=neutron1073.example.sys. it works18:40
abaindurAny idea why the zone is being returned as not found to neutron, when it clearly exists and we've created manual records in it via Designate directly? I even tried it with the exact same auth_token the neutron driver uses to init the designateclient.18:41
mugsieadaindur - you have to remove the extra `/` at the end of the designate URL19:28
mugsieif you manually curl  https://localhost/designate/v2//zones?name=neutron1073.example.sys.19:29
mugsieoh, and it is missing the v219:29
mugsiecan you paste your config for the neutron integration?19:29
*** rfreire has quit IRC19:33
abaindurhang on, want me to paste it directly here?19:34
abaindurmugsie: let me remove the passwds19:34
mugsieon paste.openstack.org19:34
mugsieabaindur: ^19:35
abaindurmugsie: http://paste.openstack.org/show/726975/19:36
abaindurWe have a nginx proxy to redirect <url/IP of controller>/designate to the appropriate service port19:37
abaindurSo our URL is set to url = https://arjuntset.platform9.horse/designate19:37
*** KeithMnemonic1 has joined #openstack-dns19:39
abaindurmugsie: oh, is it because it misses the /v2 ?19:40
*** KeithMnemonic has quit IRC19:40
mugsieI think so19:40
*** KeithMnemonic2 has joined #openstack-dns19:42
*** khushbu has joined #openstack-dns19:43
*** KeithMnemonic1 has quit IRC19:44
*** khushbu has quit IRC19:47
*** briner has joined #openstack-dns19:48
*** KeithMnemonic2 has quit IRC19:53
*** KeithMnemonic has joined #openstack-dns19:57
*** briner has quit IRC20:17
*** livelace has quit IRC21:03
*** livelace has joined #openstack-dns21:04
openstackgerritArjun Baindur proposed openstack/designate master: Make update_status use synchronized_zone  https://review.openstack.org/58764221:47
abaindurmugsie: thanks! It is working now. it was the missing /v2 in endpoint url21:50
*** bnemec has quit IRC21:51
abaindurone question regarding the PTR records - is there a reason the PTR zones are created as an admin by neutron in a separate tenant (the one specified in neutron.conf's designate section)21:52
abaindurrather than the same tenant as the zone the A records are added to...21:52
abaindurSince there's no way to share zones as we can with neutron networks. No tenant admin is going to be able to even view the PTR records21:53
« Monday, 2018-07-30 Index Wednesday, 2018-08-01 »

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