MAAS

[1.9 UI] UI doesn't make it clear that you can only change hostname and not domain (fqdn) prior to 2.0

Bug #1581562 reported by Jacek Nykis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Medium
Unassigned
MAAS 1.9.5

Bug Description

When changing a machine hostname, it is not clear for the user that they cannot change the FQDN. It should be cleararer for the user that they can only change the hostname in 1.9.

[old report]
I can't find a way to update FQDN for my servers in MAAS.

If I open a host its hostname is editable, I can click on it and edit text but "Save" button next to it is inactive. I tired clicking it anyway but nothing happens. I attached screenshot to show what I can see

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===========================================================-=============================================-============-===============================================================================
un maas <none> <none> (no description available)
ii maas-cli 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS command line API tool
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server common files
un maas-dhcp <none> <none> (no description available)
ii maas-dns 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server provisioning libraries

See original description
Tags: ux
Revision history for this message
Jacek Nykis (jacekn) wrote :
Revision history for this message
Blake Rouse (blake-rouse) wrote :

This is expected behavior. MAAS now only allows the hostname of a node to be just that the hostname. You need to remove the ".internal" to be able to save the name. We did this on purpose and did not perform a data migration as it would cause current deployments to break.

If you want to place that node into the internal domain then you need to change the domain of the cluster controller or add another cluster controller with that domain and assign that node to it.

In 2.0 you can just create the domain and assign the node to it. That is not available in 1.9.

Changed in maas:
status: New → Invalid
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Jacek,

The FQDN in MAAS <2.0 is composed by:

<node hostname>.<DNS zone name defined in the cluster controller>.

As such, you cannot change the FQDN in a node, You can only change the <hostname>. If you want it to change the domain seciton, you';ll have to change that in the Cluster Controller that the node is PXE booting from.

In 2.0, you'll have the ability to add multiple DNS domain names and select the one you want to use per machine.

Revision history for this message
Jacek Nykis (jacekn) wrote :

Blake,

Thanks, understood however I respectfully disagree with this approach. I think it perfectly reasonable to expect MAAS cluster controller in one domain to control hosts from another one. For example one might want to have single controller for .internal and .canonical.com and .devel domains to save hardware.

If this behaviour is here to stay then maybe this bug is usability one.
In MAAS 1.9 nodes list first column is labelled "FQDN" and my hosts contain .internal suffix there. When I switch to the node view I see the same name with .internal suffix so it all looks like it _should_ work.
I think short error message indicating what's wrong should help.

Changed in maas:
status: Invalid → New
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Jacek,

MAAS 1.x was designed like this. This goes all the way from the very beginning of MAAS. This is what MAAS 2.0 solves. If you would like to use the way you are describing, you should use MAAS 2.0. As such, this bug as it is, is 'Invalid'.

I'll re-purpose the bug for the latter.

summary: - Can't change FQDN
+ [1.9 UI] UI doesn't make it clear that you can only change hostname and
+ not domain (fqdn)
Changed in maas:
milestone: none → 1.9.3
importance: Undecided → Medium
status: New → Confirmed
Andres Rodriguez (andreserl)
description: updated
tags: added: ux
LaMont Jones (lamont)
summary: [1.9 UI] UI doesn't make it clear that you can only change hostname and
- not domain (fqdn)
+ not domain (fqdn) prior to 2.0
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 1.9.3 → 1.9.4
Gavin Panella (allenap)
Changed in maas:
status: Confirmed → Triaged
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 1.9.4 → 1.9.5
Revision history for this message
Andres Rodriguez (andreserl) wrote :

We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.

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.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.