Public bug reported:

Consider the following scenario:
Region controller with 3 interfaces:
eth1: 192.168.21.x
eth2: 192.168.22.x
eth3: 10.98.0.x

Cluster controller with 2 interfaces:
eth0: 192.168.20.x
eth1: 10.98.0.x

When I install the region controller, it autodetects 10.98.0.x (default
route) as the PXE server for the RC. I run dpkg-reconfigure and change
it to 192.168.21.5 which is the correct address

When I install the cluster controller, it asks for the publicly
accessible API of the MAAS server, which is http://10.98.0.90/MAAS

Once the cluster controller is installed, the amqp address sent from the
RC is 192.168.21.5, which is not accessible from the CC.

So, the RC uses DEFAULT_MAAS_URL as the amqp address and if there are
other clusters controllers connected to this MAAS server, they end up
with the wrong address.

Julian suggested that on dpkg-reconfigure more questions could be asked
like the address of the RC pxe server and the webui/api/amqp address.

** Affects: maas (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1068383

Title:
  package reconfiguration could ask further configuration details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1068383/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to