#50753 Dumping the changelog to a file doesn't work.
Closed: wontfix 4 years ago by spichugi. Opened 4 years ago by mmuehlfeldrh.

Issue Description

The "-o file" option doesn't work with "dsconf replication dump-changelog". It creates a 0 byte file and writes the output to standard out, instead of the specified file.

Package Version and Platform

389-ds-base-1.4.1.10-1.module+el8dsrv+4575+0d8b81fc.x86_64

Steps to reproduce

  1. Set up replication.
  2. Run:
    dsconf -D "cn=Directory Manager" ldap://server.example.com replication dump-changelog -o /tmp/changelog-export.ldif -r "dc=example,dc=com"

Actual results

/tmp/changelog-export.ldif is created but the size is 0 bytes. Instead of writing the changelog to that file, dsconf displays it on standard out.

Expected results

If "-o file" is specified, the changelog should be written to that file.


Metadata Update from @spichugi:
- Issue assigned to spichugi

4 years ago

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

4 years ago

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

4 years ago

ae87936..876ce73 389-ds-base-1.4.1 -> 389-ds-base-1.4.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/3808

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)

3 years ago

Login to comment on this ticket.

Metadata