Changing the dns zone name of a cluster does not remove the old zone.

Bug #1438977 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Medium
Unassigned

Bug Description

If I change the zone name of a cluster, from say 'zone1.com' to 'zone11.com', the old 'zone1.com' does not get removed and files still remain in /etc/bind/maas/.

Also, when renaming, the zone declarations name does not change:

roaksoax@unleashed:/etc/bind/maas$ grep -sr zone *
named.conf.maas:zone "zone1.com" {
named.conf.maas: file "/etc/bind/maas/zone.zone1.com";

Changed in maas:
milestone: none → 1.8.0
importance: Undecided → High
status: New → Triaged
description: updated
summary: - Changing the zone name of a cluster does not remove the old zone.
+ Changing the dns zone name of a cluster does not remove the old zone.
Revision history for this message
Raphaël Badin (rvb) wrote :

I'm not sure I understand this bug:
- You're right that old zone files are not being deleted when a zone changes. But since they are not referenced from /etc/bind/maas/named.conf.maas, it doesn't matter so much. Granted, it's probably better to remove the zone files when they are not used anymore but this is just a cleanup.
- Now the part that I don't understand is "zone declarations name does not change". I've tested renaming a zone and I see the reference to the new zone being added to /etc/bind/maas/named.conf.maas… ?

Revision history for this message
Raphaël Badin (rvb) wrote :

Reducing this to Medium, leaving a couple of files behind that are not referenced anywhere isn't really a problem.

Changed in maas:
importance: High → Medium
Changed in maas:
milestone: 1.8.0 → 1.9.0
Changed in maas:
status: Triaged → Won't Fix
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.