#49800 Debug messages "OK user/group dirsrv exists" are emitted when lib389 cli tools are used
Closed: wontfix 3 years ago Opened 3 years ago by vashirov.

Issue Description

Every time instance is created or dsctl is used for ldif2db, db2ldif, bak2db, db2bak, dbscan, debug messages such as

OK user dirsrv exists
OK group dirsrv exists

are emitted.

They should be printed only in verbose/debug mode. And I think that adding user/group during above operations (except instance creation) is already too late. Also, call to add user/group during instance creation might be useful in prefixed install, but in RPM installation we already ensure that we have dirsrv user and group created.

Package Version and Platform

1.4.x

Steps to reproduce

  1. run dsctl {db2bak,db2ldif,bak2db,ldif2db,dbscan}

Actual results

Debug messages are printed.

Expected results

Debug messages should be printed only in debug/verbose mode.


Metadata Update from @mreynolds:
- 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
- Issue set to the milestone: 1.4.0
- Issue tagged with: lib389

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

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