Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1613900[details]
Video1
Description of problem:
Database
1. Create two suffix
dc=example,dc=com
dc=example1,dc=com
2. Backups & LDIFS > Backup
3. create a backup
4. delete both the above suffix
5. Try to restore again with the backup just taken
Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.8-1.module+el8dsrv+4209+f45880df.x86_64
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
This is expected behavior though. How can you restore a database if you don't have a database configured. I will add better validation, and improve the error message, but it should not be expected to work.
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
I'm getting the same error as in the attached video:
Failure restoring up server - Server is unwilling to perform
I'd also add some explanations to backup tab about what can be backed up and what can be restored since the user might be under impression that the backup can restore instance completely with all suffixes.
Moving to ASSIGNED.
Created attachment 1613900 [details] Video1 Description of problem: Database 1. Create two suffix dc=example,dc=com dc=example1,dc=com 2. Backups & LDIFS > Backup 3. create a backup 4. delete both the above suffix 5. Try to restore again with the backup just taken Version-Release number of selected component (if applicable): 389-ds-base-1.4.1.8-1.module+el8dsrv+4209+f45880df.x86_64 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: