Bug 1654250 - Rendering issue in creating local password policy under UI's Server Tab
Summary: Rendering issue in creating local password policy under UI's Server Tab
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: cockpit-389-ds
Version: 11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DS11.0
: dirsrv-11.1
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-28 10:26 UTC by Akshay Adhikari
Modified: 2020-07-28 06:55 UTC (History)
8 users (show)

Fixed In Version: redhat-ds-11-8020020200604214543.51c5a973
Doc Type: Bug Fix
Doc Text:
Cause: Opening a local password policy in the Cockpit UI. Consequence: The form is not aligned and it hard to read Fix: Redesigned the layout of how local password policies are managed in the UI. Result: The UI can a clean and easy to read page for the local password policies.
Clone Of:
Environment:
Last Closed: 2020-07-28 06:55:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
pop-up-window (176.68 KB, image/png)
2018-11-28 10:26 UTC, Akshay Adhikari
no flags Details
local pwpolicy (255.43 KB, image/png)
2019-09-03 08:48 UTC, Viktor Ashirov
no flags Details
pwpolicy in a small window (122.58 KB, image/png)
2019-09-30 07:41 UTC, Viktor Ashirov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3171 0 None None None 2020-07-28 06:55:20 UTC

Description Akshay Adhikari 2018-11-28 10:26:26 UTC
Created attachment 1509428 [details]
pop-up-window

Description of problem:

Rendering issue in the create-local-password policy of UI's server tab and in other tabs also. 

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

cockpit-389-ds-1.4.0.19-2.module+el8+1+36e60e1d.noarch

How reproducible:

Every time

Steps to Reproduce:

1. Create a DS instance.
2. Select Server Tab > Password Policy > Local Password Policy.
3. Click on create-local-password-policy.

Actual results:

Check the Attachment

Expected results:
The pop-up window should be expandable.

Additional info:

Comment 1 mreynolds 2019-03-18 14:39:22 UTC
Fixed in:  389-ds-base-1.4.0.20-9.module+el8+2890+f5597371

Comment 3 Viktor Ashirov 2019-09-03 08:48:31 UTC
Created attachment 1611056 [details]
local pwpolicy

Modal window is not centered, moving back to ASSIGNED

Comment 5 Viktor Ashirov 2019-09-30 07:41:24 UTC
Builds tested:
389-ds-base-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.x86_64
cockpit-389-ds-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.noarch

The modal dialog is still a bit off. If I start decreasing the browser's window width, it's even more visible, that the dialog gravitates towards the right border, see attached screenshot.

Comment 6 Viktor Ashirov 2019-09-30 07:41:55 UTC
Created attachment 1620982 [details]
pwpolicy in a small window

Comment 7 mreynolds 2019-10-07 15:00:38 UTC
This is an issue with patternfly's modal using set a width, and when we expanded it it became very difficult to perfectly center it.  I think we will address this once we move this tab to ReactJS, then I can redesign the entire modal

Comment 11 Akshay Adhikari 2020-07-10 14:17:58 UTC
Build tested:

389-ds-base-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.x86_64
cockpit-389-ds-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.noarch

Steps:

1) Create a DS instance
2) Select Database Tab 
3) Under "Password Policy" click on Local Password Policy > Create policy

I cannot see any Rendering issue as the whole tab is converted to ReactJS and the page is re-designed under the Database tab.

Marking as VERIFIED.

Comment 13 errata-xmlrpc 2020-07-28 06:55:14 UTC
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-2020:3171


Note You need to log in before you can comment on or make changes to this bug.