Change BIND config to use inclusive language

Bug #2039889 reported by Adam Vest
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Status tracked in 3.6
3.5
Won't Fix
Low
Unassigned
3.6
Triaged
Low
Unassigned

Bug Description

Hello,

I was noticing that the bind config as shipped with MAAS (the snap version, anyway) still uses master/slave references. The version of bind that's shipped with the MAAS 3.3 snap appears to be 9.18.12, and according to this[1], using such terminology is slated for deprecation and ultimate removal in a couple more versions.

Since the version of bind that's shipped supports primary/secondary terminology, just proposing that we update MAAS to use this terminology in the configs.

Thank you!

Current Version:
:~# snap list maas
Name Version Rev Tracking Publisher Notes
maas 3.3.4-13189-g.f88272d1e 28521 3.3/stable canonical✓ -

--
[1] https://lists.isc.org/pipermail/bind-users/2020-June/103303.html

Revision history for this message
Anton Troyanov (troyanov) wrote :

Hi Adam,

Thank you for the bug report.

FTR:
My guess is that to address this issue we need to:
1. Change src/provisioningserver/templates/dns/named.conf.template
2. Update tests at src/provisioningserver/utils/tests/test_isc.py

Changed in maas:
importance: Undecided → Low
milestone: none → 3.5.0
status: New → Triaged
Changed in maas:
milestone: 3.5.0 → 3.5.x
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.