DNS Zones cannot be deleted/updated within Horizon

Bug #1827241 reported by Miguel Meneses
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Designate Dashboard
New
Undecided
Unassigned
OpenStack Designate Charm
Invalid
Low
Unassigned

Bug Description

Within Horizon

If you go to....

Project -> DNS --> ZONES --> (choose a zone to delete/update) --> select 'create record set' drop down menu -> Update/Delete

When attempting to delete the zone nothing happens, zone does not delete. (no error message displayed)

The zone can be deleted via the CLI

Openstack client-CLI version: 3.18.0
Horizon version: 13.0.1 (3:13.0.1-0ubuntu4~cloud0)
designate version: designate 2.11.0

tags: added: canonical-bootstack
removed: canonical
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Please could you provide the bundle for this system and any logs from horizon instance that might show the error.

Also, the ubuntu/OpenStack versions, and the juju status output to provide the charm versions.

Thanks.

Changed in charm-designate:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Designate Charm because there has been no activity for 60 days.]

Changed in charm-designate:
status: Incomplete → Expired
Dorina Timbur (dorina-t)
Changed in charm-designate:
status: Expired → New
Revision history for this message
Giuseppe Petralia (peppepetra) wrote :
Revision history for this message
Giuseppe Petralia (peppepetra) wrote :
Revision history for this message
Giuseppe Petralia (peppepetra) wrote :
Revision history for this message
Giuseppe Petralia (peppepetra) wrote :

Hi,

the ubuntu version is Ubuntu 16.04.6 LTS, kernel 4.15.0-54-generic #58~16.04.1-Ubuntu

Openstack release is queens.

python-django-horizon 3:13.0.1-0ubuntu6~cloud0

We can't provide horizon logs because the request never hits the backend and an error is logged in the chrome console when clicking on the Delete button.

Thanks and regards,
Giuseppe

Changed in charm-designate:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Joe Guo (guoqiao) wrote :

Hi Team,

Is there any update about this bug? Customer is asking for a case created over 1 year ago.

Revision history for this message
Billy Olsen (billy-olsen) wrote :

On first glance, this doesn't feel like a charm issue. It feels like its a problem with the designate horizon. If its never actually hitting the server, it feels like its browser side. And indeed the console log provided by peppepetra86 in comment #5 points to a javascript issue which matches LP#1750384.

Changed in charm-designate:
status: Triaged → Confirmed
status: Confirmed → Invalid
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.