Bug 1212635 - 389ds: the command dsctl db2ldif fails
Summary: 389ds: the command dsctl db2ldif fails
Status: NEW
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Other (show other bugs)
Version: Leap 15.5
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: William Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-23 04:16 UTC by Giacomo Comes
Modified: 2023-08-02 11:16 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Giacomo Comes 2023-06-23 04:16:18 UTC 
In order to make a backup of a ds instance I run:
  dsctl <DSINST> stop
  dsctl <DSINST> db2ldif --replication userRoot
and a backup file is created in /var/lib/dirsrv/slapd-<DSINST>/ldif
The second command works on Leap 15.4 but it fails on Leap 15.5 with the error message:
  Error: expected str, bytes or os.PathLike object, not NoneType
If I specify the path to the ldif output location:
  dsctl <DSINST> db2ldif --replication userRoot /path/to/file.ldif
then the command succeeds.
dsctl <DSINST> db2ldif --help
shows:
  usage: dsctl [instance] db2ldif [-h] [--replication] [--encrypted]
                                backend [ldif]
which indicates that the ldif path is an optional parameter.

Either there is a bug in the leap 15.5 version of dsctl, or the behaviour has changed and the help output had not been updated.