Description of problem: db2ldif -s <suffix1> -s <suffix2> or db2ldif -n <backend1> -n <backend2> is not considering all the parameters. The reason is rather obvious: ================ while getopts "hZ:vd:D:ENa:rs:x:CSut:n:UmMo1qc:" flag do case $flag in h) usage exit 0;; Z) servid=$OPTARG;; n) benameopt="-n $OPTARG" required_param="yes";; s) includeSuffix="-s \"$OPTARG\"" required_param="yes";; x) excludeSuffix="-x \"$OPTARG\"";; ================= should be: ================ while getopts "hZ:vd:D:ENa:rs:x:CSut:n:UmMo1qc:" flag do case $flag in h) usage exit 0;; Z) servid=$OPTARG;; n) benameopt=$benameopt" -n $OPTARG" required_param="yes";; s) includeSuffix=$includeSuffix" -s \"$OPTARG\"" required_param="yes";; x) excludeSuffix=$excludeSuffix" -x \"$OPTARG\"";; ================= Version-Release number of selected component (if applicable): 389-ds-base-1.3.4.0-29.el7.x86_64 (this is only RHEL7 issue. RHEL6 is doing the right way by passing the full command line to ns-slapd db2ldif). How reproducible: always Steps to Reproduce: use multiple suffix in export, for instance Workaround: change the script shown before.
attachment 0001-Ticket-48828-db2ldif-is-not-taking-int-account-multiple-suffixes-backends.patch
Reviewed by nhosoi.
Pushed to master on behalf of German Parent. cbb8bf4..4fc76f2 master -> master commit 4fc76f2bcbf339531aa96ef37406aa2efa524346
Metadata Update from @gparente: - Issue set to the milestone: 1.3.5.1
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/1888
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)