Created attachment 1781999 [details]
Description of problem:
The 389-console only shows a white page and a red "Oops!" indicator
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. dnf install cockpit-389-ds
2. Create instance.inf
full_machine_name = ldap.example.com
start = True
strict_host_checking = False
instance_name = localhost
root_password = mysecret
port = 389
secure_port = 636
self_sign_cert = False
sample_entries = yes
suffix = dc=example,dc=com
3. dscreate from-file instance.inf
4. systemctl enable --now cockpit.socket
5. Open https://<host>:9090/389-console in browser
Console does not load, red "Ooops!" indicator (see Screenshot)
Works as expected on Fedora 33 with cockpit-389-ds-184.108.40.206-1.fc33.noarch
Please note that this would be fixed by: https://koji.fedoraproject.org/koji/buildinfo?buildID=1744853
Unfortunately the update was unpushed: https://bodhi.fedoraproject.org/updates/FEDORA-2021-9f1db7e096
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 34 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
The console is definitely stable in https://koji.fedoraproject.org/koji/buildinfo?buildID=1937986 (2.0.15)
Closing bug, but if problem persists for some reason, please reopen this bug and provide the browser's console log (press F12) so we can see what is crashing the browser.