#49927 dsctl db2index fails
Closed: wontfix 3 years ago Opened 3 years ago by mmuehlfeldrh.

Issue Description

The "dsctl db2index" command fails.

Package Version and Platform

389-Directory/1.4.0.16.20180829gitd6616221a B2018.241.810

Steps to reproduce

  1. systemctl stop dirsrv@instance_name
  2. dsctl instance_name db2index userRoot
  3. systemctl start dirsrv@instance_name

Actual results

# dsctl instance_name db2index userRoot
/usr/sbin/ns-slapd: invalid option -- 'n'
usage: ns-slapd upgradedb -D configdir [-d debuglevel] [-f] [-r] -a archivedir
db2index failed

Expected results

Command should succeed.


@spichugi Isn't there a test case for this? I am surprised this is failing. Would you mind having a look?

Metadata Update from @firstyear:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

3 years ago

@spichugi Isn't there a test case for this? I am surprised this is failing. Would you mind having a look?

Looks like there is an issue in the logic which decides how to construct the command (db2index or upgradedb)
https://pagure.io/389-ds-base/blob/master/f/ldap/admin/src/scripts/db2index.in#_76

Backend is added anyway and it fails for upgradedb
https://pagure.io/389-ds-base/blob/master/f/src/lib389/lib389/__init__.py#_2963

I will fix it a bit later, after the work on schema.

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0

3 years ago

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

3 years ago

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

3 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/2986

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)

2 years ago

Login to comment on this ticket.

Metadata