Sometimes when we reload the Cockpit UI we have an unexpected internal error while trying to open 389 Directory Server tab.
389-ds-base-1.4.0.13 built from master (b14c836b5ab734) on Fedora 28
The next error happens:
Uncaught TypeError: Cannot read property 'clear' of undefined at get_and_set_sasl (servers.js:223) at load_config (ds.js:272) at Function.<anonymous> (ds.js:196) at T (cockpit.js:879) at cockpit.js:891 at j (cockpit.js:808)
Sometimes it also fails with:
Uncaught TypeError: Cannot read property 'options' of null at Function.<anonymous> (ds.js:167) at T (cockpit.js:879) at cockpit.js:891 at j (cockpit.js:808)
It should proceed without any error
Metadata Update from @spichugi: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue tagged with: Cockpit
I can not reproduce this problem on master branch
Okay, I've checked it with Firefox and I wasn't able to reproduce it there. I can reproduce it easily with Chrome though.
I will investigate in details later.
Uncaught TypeError: Cannot read property 'clear' of undefined at get_and_set_sasl (servers.js:223)
I might have accidentally of fixed this in the password policy PR, but even without that change Chrome still works for me.
The issue is fixed with https://pagure.io/389-ds-base/c/7449810386821229b10c3dc0bf71bff3e143efef?branch=master
Metadata Update from @spichugi: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2937
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)