[2.5] dnssresources read outputs nothing when there are machines with assigned IP's and records in the zone file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
High
|
Unassigned |
Bug Description
I have a MAAS were there are multiple resource records for both, machines and controllers. These are listed in the UI just fine, however they are not exposed over the API (see screenshots for comparison).
ubuntu@maas00:~$ maas user1@ldap dnsresources read
Success.
Machine-readable output follows:
[]
ubuntu@maas00:~$ maas user1@ldap dnsresource-records read
Success.
Machine-readable output follows:
[]
ubuntu@maas00:~$ maas user1@ldap domains read
Success.
Machine-readable output follows:
[
{
"ttl": null,
"name": "maas",
"id": 0,
},
{
"ttl": null,
"name": "maaslab",
"id": 1,
},
{
"ttl": null,
"name": "foo.com",
"id": 2,
},
{
"ttl": null,
"name": "gate.local",
"id": 3,
}
]
ubuntu@
zone.90.
zone.maaslab:node01 30 IN A 10.90.90.3
ubuntu@
zone.90.
zone.maaslab:node02 30 IN A 10.90.90.4
description: | updated |
summary: |
- [2.5] dnssresources read outputs nothing + [2.5] dnssresources read outputs nothing when there are machines with + assigned IP's and records in the zone file |
description: | updated |
This is because the UI also presents synthetic records that are not actually in the database and cannot be changed by the user.
A change was recently landed that allows those to be seen in "dnsresources read" if the "all=true" parameter is specified. Unfortunately, it seems a separate bug may be preventing the implicit resources from being presented - if no non-implicit records exist. So you still might not see anything even if you run that.
We could investigate what it would take to make *real* DNS records instead of implicit ones, but it could be a very significant change - possibly not sufficiently small in scope to be a bug fix.