Bug 1685395

Summary: Perform Backup fails when Backend Name is not configured
Product: Red Hat Directory Server Reporter: Anuj Borah <aborah>
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: afarley, ebock, lkrispen, mhonek, nkinder, pasik, rmeggins, spichugi, tbordaz, vashirov
Target Milestone: DS11.0   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: sync-to-jira
Fixed In Version: 389-ds-base-1.4.1.6-2.module+el8dsrv+3912+aa2ce078.x86_64 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-06 12:42:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
video demo none

Description Anuj Borah 2019-03-05 06:02:58 UTC
Created attachment 1540853 [details]
video demo

Description of problem:

Perform Backup fails when Back end Name is not configured 

Actions > Perform Backup 

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

Version-Release number of selected component (if applicable):

389-ds-base-1.4.0.20-7.module+el8+2809+aaa18b6a.x86_64

How reproducible:

Always

Steps to Reproduce:

Mentioned Above 


Actual results:

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


Expected results:

Should Give Feedback like 'Nothing to backup' Or 'Success'


Additional info:

Comment 1 mreynolds 2019-03-18 14:37:16 UTC

I can not reproduce this.  This could be related to a faulty build.  Works for me using: 389-ds-base-1.4.0.20-9.module+el8+2890+f5597371

Comment 2 mreynolds 2019-03-25 15:30:02 UTC
https://pagure.io/389-ds-base/issue/50289

Comment 4 Viktor Ashirov 2019-09-03 09:16:09 UTC
Build tested: 389-ds-base-1.4.1.6-2.module+el8dsrv+3912+aa2ce078.x86_64

I get a following error:

{"desc": "Server is unwilling to perform", "info": "no db2archive function defined.  There is no backend/suffix present"}

Error message states why backup operation failed, marking as VERIFIED.

Comment 8 errata-xmlrpc 2019-11-06 12:42:01 UTC
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