Description of problem: Bad UI while adding an entry to Trusted Forest Settings. The form to input entry doesn't load in one click. Version-Release number of selected component (if applicable): 5.10.4 How reproducible: Always Steps to Reproduce: 1. Go to Configurations > Authentications 2. Select LDAP mode 3. Check `Get User Groups from LDAP` 4. Click on the plus icon that appears under `Trusted Forest Settings` and check if you are able to input any data. Actual results: Need to click the plus icon multiple times before finally getting a stable form to input data. Expected results: Clicking the plus icon once should load a stable form. Additional info: This used to work fine on 5.9 but it persists on 5.11.
https://github.com/ManageIQ/manageiq-ui-classic/pull/5548
https://github.com/ManageIQ/manageiq-ui-classic/pull/5554
New commits detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/bcfd5106765cf2239e80087fb172cd0490d9f23a commit bcfd5106765cf2239e80087fb172cd0490d9f23a Author: Dávid Halász <dhalasz> AuthorDate: Wed May 8 02:59:33 2019 -0400 Commit: Dávid Halász <dhalasz> CommitDate: Wed May 8 02:59:33 2019 -0400 Convert ldaphost in trusted forests to string to avoid exceptions https://bugzilla.redhat.com/show_bug.cgi?id=1706764 app/views/ops/_ldap_forest_entries.html.haml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) https://github.com/ManageIQ/manageiq-ui-classic/commit/e90f0d6910524c728853f9a1b1f200777705e68d commit e90f0d6910524c728853f9a1b1f200777705e68d Author: Dávid Halász <dhalasz> AuthorDate: Thu May 9 10:41:48 2019 -0400 Commit: Dávid Halász <dhalasz> CommitDate: Thu May 9 10:41:48 2019 -0400 Do not submit the form when adding a new LDAP trusted forest item Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1706764 app/views/ops/_ldap_forest_entries.html.haml | 4 +- 1 file changed, 2 insertions(+), 2 deletions(-)
FIXED. Verified on 5.11.0.4.20190514210444_0c91ee1.
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/RHBA-2019:4199