Bug 1271579 - Automember rule expressions disappear from tables on single expression delete
Summary: Automember rule expressions disappear from tables on single expression delete
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Standa Laznicka
QA Contact: Namita Soman
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-14 10:34 UTC by Martin Bašti
Modified: 2016-11-04 05:38 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2016-11-04 05:38:56 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Martin Bašti 2015-10-14 10:34:45 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/5353

Upon deleting an expression at the automember rule page, all the expressions from both Inclusive/Exclusive tables disappear. They appear back on refresh (without the deleted expressions).

Steps to reproduce:
1. Go to an automember rule detail page
2. Create some expressions in both Inclusive/Exclusive tables
3. Delete one or more expressions from either table by selecting them and clicking "Delete".

Expected result:
The table that contained the deleted expression(s) gets updated according to the changes.

Actual result:
All expressions from both tables disappear.

Comment 2 Mike McCune 2016-03-28 23:35:19 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Comment 4 Varun Mylaraiah 2016-09-13 13:50:44 UTC
Verified
Version : ipa-server-4.4.0-10.el7.x86_64

After deleting expressions gets updated as expected.

Comment 6 errata-xmlrpc 2016-11-04 05:38:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2404.html


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