[2.4] After a fresh MAAS install MAAS cannot create domains nor update records
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
Critical
|
Unassigned |
Bug Description
After installing a fresh 2.4 version of MAAS, it wouldn't be updating anything to DNS and likely anything else at all.
Error
-----
1. Installed maas and checked the zones:
root@maas-
total 28
drwxr-xr-x 2 maas root 4096 Dec 10 22:57 ./
drwxr-sr-x 3 root bind 4096 Dec 10 22:56 ../
-rw-r--r-- 1 maas maas 305 Dec 10 22:57 named.conf.maas
-rw-r--r-- 1 maas maas 110 Dec 10 22:57 named.conf.
-rw-r----- 1 maas bind 257 Dec 10 22:56 named.conf.
-rw------- 1 maas root 539 Dec 10 22:56 rndc.conf.maas
-rw-r--r-- 1 maas maas 304 Dec 10 22:57 zone.maas
2. Then created a domain named 'first':
root@maas-
Success.
Machine-readable output follows:
{
"authoritat
"ttl": null,
"is_default": false,
"resource_
"id": 3,
"name": "first",
"resource_uri": "/MAAS/
}
NOTE: After creating the domain there was *NO* error log, only thing in regiond.log was:
2018-12-10 23:00:29 regiond: [info] 127.0.0.1 POST /MAAS/api/
3. Checked if the zone file was created, and it wasnt:
root@maas-
total 28
drwxr-xr-x 2 maas root 4096 Dec 10 22:57 ./
drwxr-sr-x 3 root bind 4096 Dec 10 22:56 ../
-rw-r--r-- 1 maas maas 305 Dec 10 22:57 named.conf.maas
-rw-r--r-- 1 maas maas 110 Dec 10 22:57 named.conf.
-rw-r----- 1 maas bind 257 Dec 10 22:56 named.conf.
-rw------- 1 maas root 539 Dec 10 22:56 rndc.conf.maas
-rw-r--r-- 1 maas maas 304 Dec 10 22:57 zone.maas
4. Created a device, and see if it would be added to the default zone, which the machine wasn't added:
root@maas-
root@maas-
root@maas-
root@maas-
NOTE: When doing the above, the error log I saw was:
2018-12-10 23:06:51 maasserver.
Restarting maas-regiond
-------
4. I restarted maas-regiond and now the zone file was there:
root@maas-
root@maas-
total 44
drwxr-xr-x 2 maas root 4096 Dec 10 23:08 ./
drwxr-sr-x 3 root bind 4096 Dec 10 22:56 ../
-rw-r--r-- 1 maas maas 719 Dec 10 23:08 named.conf.maas
-rw-r--r-- 1 maas maas 110 Dec 10 23:08 named.conf.
-rw-r----- 1 maas bind 257 Dec 10 22:56 named.conf.
-rw------- 1 maas root 539 Dec 10 22:56 rndc.conf.maas
-rw-r--r-- 1 maas maas 339 Dec 10 23:08 zone.122.
-rw-r--r-- 1 maas maas 317 Dec 10 23:08 zone.123.
-rw-r--r-- 1 maas maas 281 Dec 10 23:08 zone.first
-rw-r--r-- 1 maas maas 412 Dec 10 23:08 zone.maas
5. Checked if the previously created device was there, and it was:
root@maas-
zone.122.
zone.maas:device01 30 IN A 192.168.122.189
6. Added a new domain, and this time it was added correctly
root@maas-
total 44
drwxr-xr-x 2 maas root 4096 Dec 10 23:08 ./
drwxr-sr-x 3 root bind 4096 Dec 10 22:56 ../
-rw-r--r-- 1 maas maas 719 Dec 10 23:08 named.conf.maas
-rw-r--r-- 1 maas maas 110 Dec 10 23:08 named.conf.
-rw-r----- 1 maas bind 257 Dec 10 22:56 named.conf.
-rw------- 1 maas root 539 Dec 10 22:56 rndc.conf.maas
-rw-r--r-- 1 maas maas 339 Dec 10 23:08 zone.122.
-rw-r--r-- 1 maas maas 317 Dec 10 23:08 zone.123.
-rw-r--r-- 1 maas maas 281 Dec 10 23:08 zone.first
-rw-r--r-- 1 maas maas 412 Dec 10 23:08 zone.maas
-rw-r--r-- 1 maas maas 282 Dec 10 23:08 zone.second
7. Added a new device, and the device was there:
root@maas-
root@maas-
root@maas-
root@maas-
zone.122.
zone.maas:device02 30 IN A 192.168.122.190
So it seems that there's an error with MAAS in that it is either not dealing with triggers correctly, or it is ignoring the triggers or the code that handles the triggers is not running.
summary: |
- [2.4] After a fresh MAAS install MAAS cannot create + [2.4] After a fresh MAAS install MAAS cannot create domains nor update + records |
Changed in maas: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in maas: | |
milestone: | 2.5.2 → 2.5.3 |
no longer affects: | maas/2.4 |
Changed in maas: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in maas: | |
milestone: | 2.5.4 → none |
The work around to solve this issue is to restart maas-regiond.