[ui][2.4][2.5] maas ignores ttl parameter for address records

Bug #1802505 reported by Dmitrii Shcherbakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Unassigned
maas-ui
Fix Released
Unknown

Bug Description

Even if ttl is specified for an A record (via UI) MAAS creates it with a default of 30 seconds.

It is also not possible to update it afterwards via UI.

Tags: cpe-onsite ui
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

From the zone file:

test 30 IN A 10.100.1.2

Changed in maas:
status: New → Incomplete
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

Subscribed ~field-high due to the fact that this bug affects high-availability in L3-oriented FCB deployments that cannot rely on VIPs.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Please provide:

1. Exact commands executed over the CLI
2. Where does the IP come from
3. Have you confirmed this is the case in 2.4/2.5?

Changed in maas:
milestone: none → 2.5.0
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

1. Haven't tried CLI initially - UI and API only. The API part was also gated by the pacemaker resource agent operation - it looks like it did not try to apply TTL once the record was already in place.

API call that was used:
https://github.com/openstack/charm-hacluster/blob/stable/18.08/ocf/maas/maasclient/apidriver.py#L164-L183
                              ip_addresses=ip_address,
                              address_ttl=address_ttl)

After testing via CLI I can see that it actually works but I have used an incorrect parameter at first ("ttl" vs "address_ttl").

maas ubuntu dnsresources create fqdn=test.maas ip_addresses=10.100.3.2 ttl=0
https://paste.ubuntu.com/p/6NdQWvQ6bY/
    "address_ttl": null,

maas ubuntu dnsresources create fqdn=test1.maas ip_addresses=10.100.3.2 address_ttl=0
https://paste.ubuntu.com/p/vc42xhwc98/
    "address_ttl": 0,

grep test /etc/bind/maas/zone.maas
test1 0 IN A 10.100.3.2
test 30 IN A 10.100.3.2

2. In this case this is an IP of the region controller itself.

3. 2.4.2-7034-g2f5deb8b8-0ubuntu1, 2.5.0~beta4-7361-g401d6c73d-0ubuntu1~18.04.1

~~~

So, it looks like this is a UI-only problem then because:

1) TTL cannot be set;
2) cannot be updated for existing records;
3) Is incorrectly displayed (as "(default)") in the list of records when set via API or CLI (but is correctly displayed when the edit dropdown is used.

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :
Changed in maas:
status: Incomplete → New
summary: - [2.4][2.5] maas ignores ttl parameter for address records
+ [ui][2.4][2.5] maas ignores ttl parameter for address records
description: updated
Changed in maas:
status: New → Triaged
Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

Unsubscribed ~field-high.

Revision history for this message
Mike Pontillo (mpontillo) wrote :

I see the bug: when I create an A record in the UI and specify a TTL, it doesn't take effect.

There is a workaround though: you can modify the default TTL for the domain.

Changed in maas:
importance: Undecided → High
Changed in maas:
milestone: 2.5.0 → 2.5.x
Revision history for this message
Adam Collard (adam-collard) wrote :

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

Changed in maas:
status: Triaged → Invalid
Changed in maas:
status: Invalid → New
Alberto Donato (ack)
Changed in maas:
milestone: 2.5.x → none
importance: High → Medium
importance: Medium → Undecided
tags: added: ui
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Changed in maas-ui:
importance: Undecided → Unknown
Changed in maas-ui:
status: New → Fix Released
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: none → 3.3.0
Changed in maas:
milestone: 3.3.0 → 3.3.0-beta1
Changed in maas:
status: Fix Committed → Fix Released
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.