#50290 Ticket 50289 - Fix various database UI issues
Closed by spichugi. Opened by mreynolds.
mreynolds/389-ds-base ui-fixes  into  master

Download 50290.patch

Description:

Fixed these issues:

  • https://bugzilla.redhat.com/show_bug.cgi?id=1664621 - backup freezes when no suffix present

  • https://bugzilla.redhat.com/show_bug.cgi?id=1685395 - Perform Backup fails when Backend Name is not configured

  • https://bugzilla.redhat.com/show_bug.cgi?id=1688587 - typo when restarting instance

  • https://bugzilla.redhat.com/show_bug.cgi?id=1688775 - db tree breaks when suffix contains spaces.

  • https://bugzilla.redhat.com/show_bug.cgi?id=1688919 - backups fail with empty name

Also fixed issue where if you start an instance in UI the configuration is correctly loaded.

https://pagure.io/389-ds-base/issue/50289

I have a weird (empty line) error while trying to perform instance backup task from UI while the instance doesn't have any suffixes.
The screenshot:
https://drive.google.com/file/d/1IuPag3CiEf8yfzEUtQyIsWr4QzCI_VCa/view?usp=sharing

Also, dsconf backup gives me unwilling to perform exception:

# dsconf localhost backup create test_backup

Error: {'desc': 'Server is unwilling to perform'}

Though the task is created:

dn: cn=backup_2019-03-19T18:18:59.554265,cn=backup,cn=tasks,cn=config
cn: backup_2019-03-19T18:18:59.554265
nsArchiveDir: /var/lib/dirsrv/slapd-localhost/bak/test_backup
nsDatabaseType: ldbm database
objectclass: top
objectclass: extensibleObject

rebased onto a60bda60ea0e2dc48debdbabbd21a73d2fba1d3e

@spichugi, fixed, please review...

LGTM!

P.S. sorry for late review. The notification email got lost somehow.

rebased onto 395a4a26bd2043effe00b93930961ba210da5c5c

Thanks @spichugi !

Pull-Request has been merged by mreynolds

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3349

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

Metadata