search

389ds / 389-ds-base

The enterprise-class Open Source LDAP server for Linux
https://www.port389.org/
Other
211 stars 91 forks source link

After upgrading from 389-Directory/2.2.9 B2024.044.1200 to 389-Directory/2.2.10 B2024.225.1200 on OpenSuSE 15.6, .dsrc file not working #6380

Open gike77 opened 5 days ago

gike77 commented 5 days ago

Issue Description

After upgrading from 389-Directory/2.2.9 B2024.044.1200 to 389-Directory/2.2.10 B2024.225.1200 on OpenSuSE 15.6, .dsrc file not working correctly.

Yesterday I applied OpenSuSE security patches which included an upgrade of 389-ds, lib389 and libsvcore0. After finishing installing the patches, the systems always asks me the basedn if I do not use the -b dc=caha,dc=es on the command line with dsidm. However, there is a file called ~/.dsrc file with the content:

[ldapint] uri = ldapi://%%2fvar%%2frun%%2fslapd-ldapint.socket basedn = dc=caha,dc=es binddn = cn=Directory Manager

After intalling the patches, without rebooting the computer, the version shown is the same as before installing patches (2.2.9). If I reboot the computer, then the version changes to 2.2.10. However, even before rebooting the computer, just after installing the patches (with the same version 2.2.9) the system starts asking me the basedn if I do not specify -b dc=caha,dc=es

Package Version and Platform:

The applied security patches related with 389-ds are:

Steps to Reproduce

Apply security patches that include above security packages No need to reboot the computer. The computer before rebooting remains on 2.2.9, but the effect is reproducible once the upgrade is finished.

Expected results

The command dsidm ldapint user list should show the list of users. Instead, it asks for the basedn, although this is defined on the ~/.dsrc file This is the expected result.

For the command to work without any question, I must explicitly define the basedn on the command line: dsidm ldapint -b dc=caha,dc=es user list This is not the expected result.

Screenshots

No screenshots, but three files with the output of dsidm -v command with the three possible situations:

  1. Without any patch installation (version 2.2.9)
  2. With patches installed (still version 2.2.9), but without rebooting the computer
  3. With patches installed and after rebooting the computer (version changed to 2.2.10)

01 - Version 2.2.9 B2024.044.1200 - WITHOUT PATCHES (initial situation - all working well).txt 02 - Version 2.2.9 B2024.044.1200 - WITH PATCHES BUT BEFORE REBOOT THE SYSTEM.txt 03 - Version 2.2.10 B2024.225.1200 - WITH THE PATCHES AND AFTER REBOOTING.txt

Thanks

vashirov commented 5 days ago

This was fixed recently in https://github.com/389ds/389-ds-base/pull/6362 and backported to 2.2, but not sure when it will land in OpenSUSE.

gike77 commented 5 days ago

Thanks, Vashirov.

Then we have to wait the OpenSuSE patch.

Ok, thanks

Firstyear commented 5 days ago

It's been submitted internally and is waiting on QA process. Estimate is mid nov.

gike77 commented 3 days ago

Thanks for the info, Firstyear