Cannot disable DNS on MAAS cluster interface

Bug #1383768 reported by Jorge Niedbalski
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
High
Unassigned

Bug Description

[Environment]

ii maas 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS server all-in-one metapackage
ii maas-cli 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS command line API tool
ii maas-cluster-controller 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS server cluster controller
ii maas-common 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS server common files
ii maas-dhcp 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS DHCP server
ii maas-dns 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS DNS server
ii maas-region-controller 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS server complete region controller
ii maas-region-controller-min 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS Server minimum region controller
ii python-django-maas 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS server Django web framework
ii python-maas-client 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS python API client
ii python-maas-provisioningserver 1.6.0+bzr2545-0ubuntu1~ppa1 all MAAS server provisioning libraries

Description: Ubuntu 14.04.1 LTS

[Description]

There are two network interfaces on MAAS server.

1. 172.24.0.0/24 : Manage DHCP and DNS
2. 192.168.128.0/24 : Manage DHCP.

Looking to the zone configuration

/etc/bind/maas/zone.maas
---------------------------------------------------------
maas. IN A 192.168.128.11
p01-keymeter-a1-e1c7g7 IN A 172.24.0.55
p01-neutron-a1-e1c7g7 IN A 172.24.0.56
p01-storage-b5-d5c2f0 IN A 172.24.0.165
p01-storage-a1-e1c7g8 IN A 172.24.0.61
p01-compute-a13-e1c7g8 IN A 192.168.128.65
p01-db-a2-e1c7g7 IN A 172.24.0.58
p01-neutron-a2-d5c2f1 IN A 172.24.0.156
p01-hapi-a4-d5c2f1 IN A 172.24.0.154
p01-storage-a3-e1c7g8 IN A 172.24.0.63
p01-compute-a5-e1c7g8 IN A 192.168.128.104
p01-db-a1-e1c7g7 IN A 172.24.0.51
p01-compute-b5-d5c2f0 IN A 192.168.128.37
p01-mup-a1-e1c7g7 IN A 172.24.0.52
p01-compute-b23-d5c2f0 IN A 192.168.128.76
p01-storage-b4-d5c2f0 IN A 172.24.0.164
p01-storage-b1-d5c2f0 IN A 172.24.0.161
p01-keymeter-a5-d5c2f1 IN A 172.24.0.155
p01-storage-a6-e1c7g8 IN A 172.24.0.66
p01-mup-a2-d5c2f1 IN A 172.24.0.152
p01-storage-b2-d5c2f0 IN A 172.24.0.162
p01-storage-a2-e1c7g8 IN A 172.24.0.62
p01-storage-b3-d5c2f0 IN A 172.24.0.163
p01-storage-a4-e1c7g8 IN A 172.24.0.64
p01-hapi-a1-e1c7g7 IN A 172.24.0.54
p01-storage-a5-e1c7g8 IN A 172.24.0.65
p01-db-a3-d5c2f1 IN A 172.24.0.151
p01-storage-b6-d5c2f0 IN A 172.24.0.166
bootstrap01 IN A 172.24.0.100

As you can see, IP addresses of 192.168.128.0/24 and 172.24.0.0/24 are mixed up.

All the A record has to point 172.24.0.0/24 since DNS service is disabled on interface 192.168.128.0/24. However
entries for 192.168.128.0/24 are still being created.

Tags: sts
tags: added: cts
Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → next
Revision history for this message
Christian Reis (kiko) wrote :

Can you please retry this on MAAS 1.7.0 and seeing if the issue still manifests itself?

tags: added: sts
removed: cts
Revision history for this message
Andres Rodriguez (andreserl) wrote :

We believe that this issue is no longer present as it was filed against 1.7. As such, I'm marking this as a won't fix.

Changed in maas:
status: Triaged → Won't Fix
Changed in maas:
milestone: next → none
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.