[2.4b1] DNS triggers not working

Bug #1761326 reported by Andres Rodriguez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Blake Rouse

Bug Description

It seems that DNS triggers are no longer working. I set two machines to deploy, and DNS was never updated. I restarted maas-regiond and the entries were updated in bind. Logs would normally show when DNS triggers were updated, but in this case they dont anymore:

==> /var/log/maas/maas.log <==
Apr 4 22:51:50 localhost maas.node: [info] node02: Status transition from ALLOCATED to DEPLOYING
Apr 4 22:51:50 localhost maas.node: [info] node01: Status transition from ALLOCATED to DEPLOYING
Apr 4 22:51:50 localhost maas.power: [info] Changing power state (on) of node: node02 (67t43n)
Apr 4 22:51:50 localhost maas.power: [info] Changing power state (on) of node: node01 (wecac3)

==> /var/log/maas/regiond.log <==
2018-04-04 22:51:51 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-04 22:52:10 regiond: [info] 192.168.1.13 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-04 22:52:16 maasserver.rpc.leases: [info] Lease update: commit for 10.90.90.178 on b8:ae:ed:7d:17:d2 at 2018-04-04 22:52:16 (lease time: 30s)

==> /var/log/maas/maas.log <==
Apr 4 22:52:17 localhost maas.power: [info] Changed power state (on) of node: node01 (wecac3)
Apr 4 22:52:17 localhost maas.power: [info] Changed power state (on) of node: node02 (67t43n)

==> /var/log/maas/regiond.log <==
2018-04-04 22:52:18 maasserver.rpc.leases: [info] Lease update: commit for 10.90.90.179 on b8:ae:ed:7d:6:2d at 2018-04-04 22:52:18 (lease time: 30s)
2018-04-04 22:52:21 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-04 22:52:32 regiond: [info] 192.168.1.73 GET /MAAS/static/partials/subnet-details.html?v=2.4.0~beta1(6799-g391e5f16d-0ubuntu1) HTTP/1.1 --> 200 OK (referrer: http://192.168.1.13:5240/MAAS/; agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36)
2018-04-04 22:52:40 regiond: [info] 192.168.1.13 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2018-04-04 22:52:51 regiond: [info] 192.168.1.73 POST /ping HTTP/1.1 --> 404 NOT_FOUND (referrer: -; agent: PycURL/7.43.0.1 libcurl/7.58.0 GnuTLS/3.5.18 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3)
2018-04-04 22:52:57 maasserver.rpc.leases: [info] Lease update: commit for 10.90.90.178 on b8:ae:ed:7d:17:d2 at 2018-04-04 22:52:57 (lease time: 600s) (hostname: node01)
2018-04-04 22:52:58 maasserver.rpc.leases: [info] Lease update: commit for 10.90.90.179 on b8:ae:ed:7d:6:2d at 2018-04-04 22:52:58 (lease time: 600s) (hostname: node02)

Related branches

summary: - [2.4b1] DNS triggers not updating zone files
+ [2.4b1] DNS triggers not working
Changed in maas:
importance: Undecided → Critical
status: New → Triaged
milestone: none → 2.4.0beta2
Changed in maas:
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.