389-ds-base

#50744 -n option of ns-slapd dbverify does not work
Closed: wontfix by mreynolds. Opened by sgmt.

Closed: wontfix
Reopen Issue

Issue Description

ns-slapd dbverify seems to verify all instances even when -n is specified.

Package Version and Platform

51e2c4581e8640f22f563ae3c7c99b4e670992e0
Fedora 31

Steps to reproduce

  1. ns-slapd dbverify -D "configdir" -n "backend-instance-name"

Actual results

All instances are verified

Expected results

Only the instances specified by -n option are verified

0001-n-option-of-dbverify-does-not-work.patch

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2

Metadata Update from @mreynolds:
- Issue priority set to: major

commit 534c2cfa22e7026da43615cb8e42f8df7b4d930a

483f0d25b..6e7845d48 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

9c5cfbd26..3d180a54f 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

@sgmt Thank you very much contributing this patch !!

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

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: fixed)
Metadata
None
None
None
None
Normal
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.