Bug 487734

Summary:	The index task entry is not available for searching immediately after creation.
Product:	Red Hat Directory Server	Reporter:	Asha Akkiangady <aakkiang>
Component:	Directory Server	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED NOTABUG	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	medium	Docs Contact:
Priority:	low
Version:	9.0	CC:	alee, benl
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-04-09 18:48:36 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 Asha Akkiangady 2009-02-27 17:45:45 UTC

Description of problem:
The index task entry is not available for searching immediately after
creation, problem happens when CS 8.0 cloning setup is executed. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. This problem is discovered during the fix for the bug https://bugzilla.redhat.com/show_bug.cgi?id=486191

2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ade Lee 2009-03-03 19:06:52 UTC

Its not clear that this bug actually exists in DS.  Closer inspection of the logs and CS code indicates that the CS does the following:

1 creates indexA
2. searches for index B (to confirm that it is done)
3. uses index A

Index A and Index B are not the same, so CS is doing the wrong check.  

That said, its probably a good idea for DS to fail more gracefully on step 3.

Ade

Comment 2 Rich Megginson 2009-03-03 19:10:15 UTC

How should DS fail more gracefully on step 3?  What should DS do?

Comment 3 Rich Megginson 2009-04-09 18:48:36 UTC

I'm pretty sure this is not a DS bug - please reopen if necessary