#50550 DS installer debug messages leaking to ipa-server-install
Closed: wontfix 2 years ago by spichugi. Opened 2 years ago by spichugi.

Description of problem:

DS installer debug messages are now leaked in the main ipa-server-install output. This looks as a (very minor) regression, I did not see this text in the past.

ipa-server-install

...
Configuring directory server (dirsrv). Estimated time: 30 seconds
[1/44]: creating directory server instance

Starting installation...
Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv@RHEL8-TEST.service → /usr/lib/systemd/system/dirsrv@.service.
Opening SELinux policy "//etc/selinux/targeted/policy/policy.31"
Successfully opened SELinux policy "//etc/selinux/targeted/policy/policy.31"
Allocate local instance <class 'lib389.DirSrv'> with ldapi://%2fvar%2frun%2fslapd-RHEL8-TEST.socket
[2/44]: configure autobind for root
...

Version-Release number of selected component (if applicable):
ipa-server-4.8.0-4.module+el8.1.0+3696+eb4a1e69.x86_64
389-ds-base-1.4.1.3-3.module+el8.1.0+3533+f8225121.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run ipa-server-install
2.
3.

Actual results:
Leaking DS installer in ipa-server-install

Expected results:
DS installer info is only present in the installer log file.

Additional info:

Cloned from BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1733201


Metadata Update from @spichugi:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

2 years ago

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

2 years ago

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

2 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/3606

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