MAAS DNS can be configured for circular dependency
Bug #1928904 reported by
Boris Lukashev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.5 |
Won't Fix
|
Medium
|
Unassigned | |||
3.6 |
Triaged
|
Medium
|
Unassigned | |||
maas-ui |
Triaged
|
Medium
|
Unassigned |
Bug Description
MaaS DNS services have a logic flaw wherein a domain can be created with a record matching the name of a subdomain:
1. create test.tld domain
2. create fail.test.tld record within the domain
3. create fail.test.tld domain
4. observe the blank A record created in the new domain
5. try to remove the record from either location - fails
6. try to rename the 2nd domain
7. observe name of record change in 1st domain, neither can be deleted
This sort of setup comes about when Horizon is given the 1st domain and other services are subset in the parent domain. The records are needed for Vault to issue correct certificates.
affects: | curtin → maas |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: ui |
tags: | removed: ui |
Changed in maas: | |
milestone: | 3.5.0 → 3.5.x |
Changed in maas-ui: | |
milestone: | 3.5.0 → 3.5.x |
Changed in maas-ui: | |
milestone: | 3.5.x → 3.6.x |
To post a comment you must log in.
Is this still an issue in recent versions of MAAS (3.3 onwards)? Is it possible to see the issue using the CLI/API or just the UI?