Bug 1290141

Summary: With exhausted range, part of DNA shared configuration is deleted after server restart
Product: Red Hat Enterprise Linux 7 Reporter: Noriko Hosoi <nhosoi>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: 389-ds-base- Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 20:38:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Noriko Hosoi 2015-12-09 17:57:50 UTC
This bug is created as a clone of upstream ticket:

When a DNA config entry is created with exhausted range (e.g. MaxValue < NextValue), some attributes set in the shared config entry of the host (e.g dnaHostname=<host_fqdn>+dnaPortNum=389,cn=posix-ids,cn=dna,cn=ipa,cn=etc,SUFFIX) are lost after a DS server restart.

This ticket is a corner case of https://fedorahosted.org/389/ticket/47779.

Having initial exhausted range is used when creating an IPA replica, so that it requests a new range to the master. This way all servers use the initially defined range by default.

The problem can be reproduced systematically with the attached test case

Comment 1 Noriko Hosoi 2015-12-09 17:58:34 UTC
Verifier: dirsrvtests/tickets/ticket48362_test.py

Comment 2 Mike McCune 2016-03-28 23:13:32 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 Viktor Ashirov 2016-06-15 12:17:54 UTC
Build tested: 

Automated test passes
tickets/ticket48362_test.py::test_ticket48362 PASSED

Marking as VERIFIED.

Comment 6 errata-xmlrpc 2016-11-03 20:38:17 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.