Bug 555783 - BOGUS_NODE is displayed in console when VLVindex is created
Summary: BOGUS_NODE is displayed in console when VLVindex is created
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: 389
Classification: Retired
Component: Directory Console
Version: 1.2.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks: 512820 690311
TreeView+ depends on / blocked
 
Reported: 2010-01-15 14:26 UTC by Bob Kong
Modified: 2014-08-22 16:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-22 16:21:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Bob Kong 2010-01-15 14:26:32 UTC
Description of problem:
If replication is configured on the directory server and a vlvindex is created a BOGUS_NODE is displayed under the Directory Console when listing the suffix contents. 

Dumping the database does not show any additional entries and appears to only be console related.

Version-Release number of selected component (if applicable):
389-adminutil-1.1.8-4.el5
389-dsgw-1.1.4-1.el5
389-ds-console-1.2.0-5.el5
389-ds-1.1.3-6.el5
389-admin-1.1.10-0.2.a2.el5
389-admin-console-1.1.4-3.el5
389-ds-console-doc-1.2.0-5.el5
389-console-1.1.3-6.el5
389-ds-base-1.2.5-0.5.rc4.el5
389-admin-console-doc-1.1.4-3.el5

How reproducible:
Consistently reproducible

Steps to Reproduce:
1. Fresh install and setup of the software listed above
2. Enable replication on database
3. Create vlvindex via the directory console window (Browsing index)
4. List suffix under directory console
  
Actual results:
BOGUS_NODE is displayed as part of the listing

Expected results:
Only the valid listed entries


Additional info:

Comment 2 Martin Kosek 2012-01-04 13:41:02 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/94

Comment 3 mreynolds 2014-08-22 16:21:38 UTC
I can not reproduce this on the current version of the server/console, closing as works for me...


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