| *** dcdamien has quit IRC | 00:14 | |
| *** chungpht_ has joined #openstack-dns | 02:03 | |
| *** chungpht_ has quit IRC | 02:07 | |
| *** chungpht_ has joined #openstack-dns | 02:48 | |
| *** chungpht_ has quit IRC | 02:53 | |
| *** ginopc has joined #openstack-dns | 08:03 | |
| *** abaindur has quit IRC | 08:36 | |
| *** chungpht_ has joined #openstack-dns | 09:24 | |
| *** dcdamien has joined #openstack-dns | 09:46 | |
| *** salmankhan has joined #openstack-dns | 10:13 | |
| *** salmankhan has quit IRC | 10:34 | |
| *** chungpht_ has quit IRC | 11:10 | |
| *** Vadmacs has joined #openstack-dns | 11:54 | |
| *** ianychoi has joined #openstack-dns | 13:17 | |
| *** ivve has joined #openstack-dns | 15:15 | |
| *** chungpht_ has joined #openstack-dns | 16:00 | |
| *** chungpht_ has quit IRC | 16:04 | |
| *** dcdamien has quit IRC | 16:26 | |
| *** chungpht_ has joined #openstack-dns | 16:40 | |
| *** ginopc has quit IRC | 16:54 | |
| *** dcdamien has joined #openstack-dns | 17:14 | |
| *** chungpht_ has quit IRC | 17:30 | |
| *** dcdamien has quit IRC | 18:00 | |
| *** bnemec has quit IRC | 18:13 | |
| *** bnemec has joined #openstack-dns | 18:26 | |
| *** bnemec has quit IRC | 18:30 | |
| *** bnemec has joined #openstack-dns | 18:34 | |
| *** bnemec has quit IRC | 18:39 | |
| *** bnemec has joined #openstack-dns | 18:52 | |
| *** bnemec has quit IRC | 18:58 | |
| *** bnemec has joined #openstack-dns | 19:14 | |
| *** KeithMnemonic has quit IRC | 19:28 | |
| *** dcdamien has joined #openstack-dns | 19:36 | |
| *** Vadmacs has quit IRC | 20:36 | |
| *** abaindur has joined #openstack-dns | 20:41 | |
| *** rektide has joined #openstack-dns | 20:41 | |
| *** ftpd has joined #openstack-dns | 22:48 | |
| ftpd | Hi everyone. Recently I've recreated my whole designate (4.0.0) setup with restoring databases 'designate' and 'designate-pool-manager' from backup. During this recreation my internal IP's have changed, from 172.16.2.0/24 to 172.16.3.0/24. Currently my mdns instance still tries to connect to 172.16.2.x for backend. I've updated my pools.yaml and did designate-manage pool update, I've also found that db had the old values, but now, after | 22:51 |
|---|---|---|
| ftpd | designate-manage database sync, it's ok. Why it's still looking for 172.16.2.x? | 22:51 |
| ftpd | Of course all services (api, mdns, central and pool-manager) were restarted. | 22:51 |
| ftpd | 2019-01-03 23:54:56.387 2935 INFO designate.mdns.notify [req-b22093e9-da9c-4b2c-ab64-e8998f574908 - - - - -] Sending 'NOTIFY' for 'domain-345233985.com.' to '172.16.2.50:53'. | 22:55 |
| ftpd | Ok, found it. For the record and channel logs: rabbit was still handling it. Clearing queues (by simply service restart) did the trick. | 23:20 |
| ftpd | ;-) | 23:20 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!