Created attachment 1509363 [details] SS of the error Description of problem: 389 web UI gives error when try to do backup management . Version-Release number of selected component (if applicable): 389-ds-base-1.4.0.19-2.module+el8+1+36e60e1d.x86_64 How reproducible: Always Steps to Reproduce: 1. Open https://servername:9090/389-console in browser 2. Go to Left Tab 389 Directory Server 3. Go to upper right Tab: Actions> Manage Backups 4. Gives error: Failed to get list of backups Actual results: Failed to get list of backups usage: dsctl [-h] [-v] [-j] [-l] [--remove-all [REMOVE_ALL]] [instance] {restart,start,stop,status,remove,db2index,db2bak,db2ldif,bak2db,ldif2db,backups} ... dsctl: error: invalid choice: 'slapd-anuj' (choose from 'restart', 'start', 'stop', 'status', 'remove', 'db2index', 'db2bak', 'db2ldif', 'bak2db', 'ldif2db', 'backups') Expected results: It should work properly. Additional info:
Description of problem: After creating backup , when we do backup management No backups available for restore. How reproducible: Always Steps to Reproduce: 1. Open https://servername:9090/389-console in browser 2. Go to Left Tab 389 Directory Server 3. Go to Perform Backup , create backup. 3. Go to upper right Tab: Actions> Manage Backups 4. Gives error: No backups available for restore Actual results: No backups available for restore Expected results: Backups should be there , as i have created one backup and it is present there in /var/lib/dirsrv/slapd-anuj/bak
In backend it should run below command. # dsctl rhds backups Backup: /var/lib/dirsrv/slapd-rhds/bak/backup - 2018-11-28 05:35:36 (11M) Backup: /var/lib/dirsrv/slapd-rhds/bak/newbackup - 2018-11-28 05:37:18 (11M) i.e. # dsctl <instancename> backups
*** Bug 1654510 has been marked as a duplicate of this bug. ***
*** Bug 1654519 has been marked as a duplicate of this bug. ***
Build Tested: cockpit-389-ds-1.4.0.20-5.module+el8+2685+6de0feb1.noarch 389-ds-base-1.4.0.20-5.module+el8+2685+6de0feb1.x86_64 Steps: 1) Create a DS instance. 2) Once the instance is created click on the action button. 3) Click Perform Backup, give an appropriate name for the backup folder. 4) Click on Manage Backup, it should list the backup files with options to delete/restore and to search.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:3731