Changing hostname after deployment breaks maas install

[Jay Kuri]

When deploying maas 2.3 on ubuntu xenial, the machines hostname was changed. Specifically, upon initial config, the machine had a full hostname:

bob.region.stack

This was accepted as the hostname during the UI config portion of the install. When the hostname was changed to bob.internal, several services stopped working in spite of the fact that bob.region.stack was still a valid name for the host.

Changing the hostname in config files /etc/maas/rackd.* /etc/maas/region* as well as manipulating it directly in the database had no effect. The rack daemon and region controllers were unable to connect to the original name.

Eventually had to completely purge maas from the machine and re-install it to get to a working state.

How to reproduce:

1) Install Ubuntu Xenial on a server
2) Set the hostname.
3) Install maas package via apt.
4) Complete maas installation steps via UI
5) Change hostname, set original hostname in hosts.
6) reboot / restart rack / region services.
7) Watch as UI and rackd / region services fail to talk to each other.

[David Lawson (deej)]

Of particular frustration with this bug is the fact that the rack controller name is editable but MaaS refuses to save the edits because it can't look up the _existing_ name you're trying to correct. That is not a great UX experience.

[Andres Rodriguez (andreserl)]

Hi Jay,

Is this still an issue? Can you provide logs on /var/log/maas/*.log ?

Thanks!

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team