Description of problem: Once can create a backup with specifying a name. Version-Release number of selected component (if applicable): # rpm -qa | grep ^389 389-ds-base-1.4.1.1-20190312git813030cc7.el8.x86_64 389-ds-base-libs-1.4.1.1-20190312git813030cc7.el8.x86_64 # How reproducible: Always. Steps to Reproduce: 1. Create a suffix 2. Take a backup of the suffix using the UI. 3. Fill in the field "Backup Name" with the name of the backup. 4. Click again on the button "Create Backup" and this time leave the name field empty. 5. A new backup will be created with the name <PREVIOUS_NAME>.bak 6. Run again the step 4). No new backup will be created. Actual results: The backup behavior is not not consistent. Expected results: Either: * disable the "Do Backup" button or * use default name for the backup when the name field is empy ( use timestamp? ) Additional info:
https://pagure.io/389-ds-base/issue/50289
Builds tested: 389-ds-base-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.x86_64 cockpit-389-ds-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.noarch If backup name is not specified, it gets populated automatically, i.e. backup-2019_09_27_09_50_13 Marking as VERIFIED.
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