Cannot change default domain

Bug #1756745 reported by Mark Shuttleworth on 2018-03-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Mike Pontillo
2.4
High
Unassigned

Bug Description

My maas is serving a local domain 'foo'. I can create that domain and assign machines to it, but the old 'maas' domain stays around and is the default everywhere. I would like to be able to make 'foo' the default domain, and to remove the 'maas' domain altogether.

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.4.x
Andres Rodriguez (andreserl) wrote :

@Mark,

I just want to note that in the next release (likely beta1), we will have UI that will allow users to change the default domain from maas to 'foo'. It is already possible to do this over the API.

Do you think that by adding the UI to allow to change the name of the default domain, it is enough to address this issue, or do you think that we should also have the ability to set the default?

Will one be able to edit *and delete* a domain?

Mike Pontillo (mpontillo) wrote :

Yes, in MAAS 2.4 you will be able to edit any domain, and delete a domain (except the default domain). So doing what you describe should be possible if you simply rename the `maas` domain to `foo`.

Mark Shuttleworth (sabdfl) wrote :

Why not enable people to switch the default domain from one to another?

Mike Pontillo (mpontillo) wrote :

The team has always agreed that the default domain should be able to be changed; it's just a matter of priority and scope.

For MAAS 2.4, we have a partial fix for this: the model has been updated, and the API now allows the default domain to be selected.

As always, the devil is in the details: we don't have a way for a node's domain to be "unset" (which is how we would have liked to represent the concept of "default domain"). So if you change the default domain, all unallocated nodes whose domain was set to the previous default domain will be set to the new default domain.

This bug won't be considered "Fix Committed" until the UI lands (as there are more critical issues to investigate at right now), but I wanted to update this bug for your information.

Changed in maas:
status: Triaged → In Progress
assignee: nobody → Mike Pontillo (mpontillo)
Changed in maas:
milestone: 2.4.x → 2.4.0rc1
Changed in maas:
milestone: 2.4.0rc1 → 2.4.0rc2
Changed in maas:
milestone: 2.4.0rc2 → 2.5.0
Changed in maas:
milestone: 2.5.0 → 2.5.0beta2
Changed in maas:
milestone: 2.5.0beta2 → 2.5.0rc1
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 2.5.0rc1 → 2.5.0beta2
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers