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 1508263 [details]
replication-tab

Description of problem:
Replication's tab in the UI doesn't have any option to do anything with the server. It was available in the older version. More details can be found in the screenshot. (Attachment: replication-tab)

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

cockpit-389-ds-1.4.0.19-1.module+el8+1+a8d5e036.noarch
389-ds-base-1.4.0.19-1.module+el8+1+a8d5e036.x86_64

How reproducible:

Every time

Steps to Reproduce:
1. Log in to the console with the proper credential. 
2. Create a DS instance.
3. Once the instance is created, click on the replication tab.

Actual results:


Expected results:


Additional info:

Additional step after step: 3
4. Click on Configuration.

Looks like you didn't create a suffix when you created the instance.  Without a suffix there is nothing to configure for replication

All this is observed when I create an instance from the console itself and by checking: create sample entries also.

checking create sample entries or not doesn't matter to reproduce this.