Red Hat Bugzilla – Bug 1295922
Content -> Lifecycle Environments are not visible on screen and no scroll bars appear to view the additional content
Last modified: 2016-12-23 06:02:24 EST
Description of problem: If there are multiple Lifecycle Environment present under "Content -> Lifecycle Environments" then it does not fit on the screen and no scroll bar are available to scroll and view the content. Version-Release number of selected component (if applicable): Satellite Server v.6.1.5 How reproducible: This can be reproduced by having 8 or more than 8 Lifecyle Environment present under "Content -> Lifecycle Environments". We can observe that if it does not fit on screen and it does not provide scroll bar to view. Actual results: No scroll bar to view the content on screen, which results in unable to access the content. Expected results: In case of multiple Environment and if it does not fit on screen then it should provide a scroll bar for complete access.
NB. The 8 Lifecycle environments is simply the number we have and means the screen has to be extended significantly. The issue here seems to be with the whole table.
Hi, Can you add a screenshot of the behavior? Thanks!
Created redmine issue http://projects.theforeman.org/issues/13901 from this bug
PR - https://github.com/Katello/katello/pull/5813
Moving to POST since upstream bug http://projects.theforeman.org/issues/13901 has been closed ------------- Walden Raines Applied in changeset commit:katello|64044e198fd671850e7f45ec0bceecf2d9559bce.
*** Bug 1313321 has been marked as a duplicate of this bug. ***
Was able to see all the columns if I had 8 or more environments. However, the column/env names became impossible to read. I've opened a separate bug though for that: https://bugzilla.redhat.com/show_bug.cgi?id=1323699 Verified against 6.2 Snap 6.
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-2016:1500