Bug 1271579

Summary: Automember rule expressions disappear from tables on single expression delete
Product: Red Hat Enterprise Linux 7 Reporter: Martin Bašti <mbasti>
Component: ipaAssignee: Standa Laznicka <slaznick>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: ksiddiqu, mvarun, rcritten
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.4.0-0.el7.1.alpha1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 05:38:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 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