Bug 1751145

Summary: Failed to promote replica to a Master
Product: Red Hat Directory Server Reporter: bsmejkal
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 11.0CC: afarley, lkrispen, mhonek, pasik, spichugi, tbordaz, vashirov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-06 12:42:36 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:
Attachments:
Description Flags
Fail message none

Description bsmejkal 2019-09-11 09:30:01 UTC
Created attachment 1614008 [details]
Fail message

Description of problem:
Promoting replica from Consumer/Hub to Master fails.

Version-Release number of selected component (if applicable):
cockpit-196.2-1.el8.x86_64
cockpit-389-ds-1.4.1.8-1.module+el8dsrv+4209+f45880df.noarch

How reproducible:
Always

Steps to Reproduce:
1. In tab Replication -> Configuration enable replication and fill Replication role as Consumer or Hub. 
2. Save the configuration
3. Now change Replication role to Master with proper Replica Id

Actual results:
WebUI shows error 
Failed to promote replica to a Master
{"desc": "'tuple' object has no attribute 'encode'"}

Expected results:
Promoting replica to master should be successful.

Additional info:

Comment 2 Viktor Ashirov 2019-10-29 21:37:48 UTC
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 can successfully promote Consumer or Hub to Master.

Marking as VERIFIED.

Comment 4 errata-xmlrpc 2019-11-06 12:42:36 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