Bug 1959380

Summary: 389ds console does not load
Product: [Fedora] Fedora Reporter: Spike <SpikeFedora>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: abokovoy, dperpeet, mmarusak, mpitt, mreynolds, nhosoi, nkinder, patrick, pvolpe, rmeggins, spichugi, stefw, tbordaz, vashirov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-12 17:02:08 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
Screenshot showing error messages in javascript console none

Description Spike 2021-05-11 12:08:23 UTC
Created attachment 1781999 [details]
Screenshot showing error messages in javascript console

Description of problem:
The 389-console only shows a white page and a red "Oops!" indicator


Version-Release number of selected component (if applicable):
cockpit-389-ds-2.0.3-3.fc34.noarch
389-ds-base-2.0.3-3.fc34.x86_64


How reproducible:
Always


Steps to Reproduce:
1. dnf install cockpit-389-ds
2. Create instance.inf

[general]
full_machine_name = ldap.example.com
start = True
strict_host_checking = False

[slapd]
instance_name = localhost
root_password = mysecret
port = 389
secure_port = 636
self_sign_cert = False

[backend-userroot]
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


Actual results:
Console does not load, red "Ooops!" indicator (see Screenshot)


Expected results:
Working console

Additional info:
Works as expected on Fedora 33 with cockpit-389-ds-1.4.4.15-1.fc33.noarch

Comment 1 Spike 2021-05-14 05:30:00 UTC
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

Comment 2 Ben Cotton 2022-05-12 16:15:58 UTC
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.

Comment 3 mreynolds 2022-05-12 17:02:08 UTC
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.