Inconsistent validation of A DNS records

Bug #1905610 reported by Nikolay Vinogradov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Medium
Unassigned
2.9
Won't Fix
Medium
Unassigned
3.0
Won't Fix
Undecided
Unassigned
maas-ui
Won't Fix
Undecided
Unassigned
2.9
Won't Fix
Undecided
Unassigned
3.0
Won't Fix
Undecided
Unassigned

Bug Description

Running snapped MAAS 2.9 (2.9.0~rc1 (9117-g.ae6569d91).

MAAS allowed me to create an A DNS record with a dot in the middle, but it won't allow to edit or remove it until the record is renamed (see the DNS resource editing on the attached screenshot).

The validation behaviour should be made more consistent in this scenario.

Thanks.

Tags: ui
Revision history for this message
Nikolay Vinogradov (nikolay.vinogradov) wrote :
description: updated
Alberto Donato (ack)
Changed in maas:
milestone: none → 2.10-next
Alberto Donato (ack)
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
no longer affects: maas/2.8
Changed in maas:
milestone: 3.0.0 → 3.0.1
Revision history for this message
Alberto Donato (ack) wrote :

This might be a UI bug. Via API I can add and remove the record

tags: added: ui
Changed in maas:
status: Triaged → New
Changed in maas-ui:
importance: Undecided → Unknown
Changed in maas:
status: New → Triaged
Changed in maas:
milestone: 3.0.1 → none
Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

Might be that we're not validating against dots in the "add form" but we do in the "edit form". In that case all we need to do is remove this validation in "edit".

Changed in maas-ui:
status: New → Triaged
milestone: none → 3.4.x
Changed in maas:
milestone: none → 3.4.x
Changed in maas-ui:
assignee: nobody → Nick De Villiers (nickdv99)
Revision history for this message
Thorsten Merten (thorsten-merten) wrote :

We noticed that we already changed the MAAS UI and users cannot add records with dots anymore. That said, for existing records this inconvenience is still true but for new ones the situation cannot occur anymore.

Changed in maas-ui:
assignee: Nick De Villiers (nickdv99) → nobody
importance: Unknown → Undecided
status: Triaged → Won't Fix
Changed in maas:
status: Triaged → Won't Fix
Changed in maas:
milestone: 3.4.x → none
Changed in maas-ui:
milestone: 3.4.x → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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