Bug 1006360 - Broken redirection when deleting last entry of DNS resource record
Summary: Broken redirection when deleting last entry of DNS resource record
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-10 13:52 UTC by Dmitri Pal
Modified: 2014-06-18 00:11 UTC (History)
3 users (show)

Fixed In Version: ipa-3.3.1-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:48:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dmitri Pal 2013-09-10 13:52:13 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3907

Reproduction:
1. add new dns record
2. open details page of the record
3. delete the entry (there should be only one in the record)
4. redirection dialog with text "DNS record was deleted because it contained no data. You will be redirected to DNS Zone." should appear
5. confirm the dialog
6. User is not redirected

Expected:
6. User should be redirected resource records page of parent zone

Cause:
* Invalid call - `navigation.show_entity_page`. Should be `navigation.show_entity`.

Comment 3 Varun Mylaraiah 2014-02-03 10:23:40 UTC
Verified in ipa-server-3.3.3-15.el7.x86_64

Step
1. add new dns record
2. open details page of the record
3. delete the entry (there should be only one in the record)
4. redirection dialog with text "DNS record was deleted because it contained no data. You will be redirected to DNS Zone."
5. confirm the dialog
6. User is redirected to resource records page of parent zone.

Comment 4 Ludek Smid 2014-06-13 11:48:27 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.