Default zone cannot be renamed

Bug #1381125 reported by Andres Rodriguez on 2014-10-14
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
High
Unassigned

Bug Description

MAAS Default Zone cannot be renamed.

Related branches

tags: added: ui
Changed in maas:
status: New → Triaged
importance: Undecided → Wishlist
Christian Reis (kiko) on 2014-10-16
Changed in maas:
milestone: none → next
Carla Berkers (carlaberkers) wrote :

This got slightly worse in 1.8b3,

on the zones page there is no edit icon on the default row
there is an edit button if I go to the default zone page
If I click that button there is a form field indicating I can change my zone name
If I change it and click save I get an error explaining that I can't change it.

Dimiter Naydenov (dimitern) wrote :

Same issue here:

$ maas hw-root zone update default name="foo"
{"name": ["This zone is the default zone, it cannot be renamed."]}

Using the setup described in bug #1513373.

Dimiter Naydenov (dimitern) wrote :

At least I should be able to change which zone is considered the default, otherwise I end up with an empty "default" zone, which I have no use for.

Jason Hobbs (jason-hobbs) wrote :

Due to bug 1706196, we have to always use this default zone because other wise juju tries to allocate nodes there and MAAS will create it based on pods.

tags: added: cdo-qa
tags: added: internal
tags: added: cpe-onsite
tags: added: foundations-engine
Changed in maas:
milestone: next → 2.4.0rc2
importance: Wishlist → High
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: 2.4.0rc2 → 2.4.0beta3
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