#94 BOGUS_NODE is displayed in console when VLVindex is created
Closed: wontfix None Opened 12 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=555783

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:

batch update to FUTURE milestone

set default ticket origin to Community

Added initial screened field value.

I can not reproduce this issue using the current version of console, closing ticket...

Metadata Update from @nkinder:
- Issue assigned to mreynolds
- Issue set to the milestone: 389-admin,console 1.1.36

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/94

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

3 years ago

Login to comment on this ticket.

Metadata