Description of problem: Input fields are inaccessible during self hosted engine setup. See attached screenshot. Version-Release number of selected component (if applicable): - ovirt-node-ng-installer-master-2017112909 - appliance 4.2-20171130.1.el7.centos How reproducible: Start installation of self hosted engine on a large screen, in terms of height (1200px). Steps to Reproduce: 1. Start self hosted engine setup 2. 3. Actual results: fields invisible Expected results: visible fields Additional info: Tested in Firefox at a screen resolution of 1920x1200 Workaround: resize browser window to a lower height.
Can you attach a screenshot?
Created attachment 1362508 [details] Screenshot
Created attachment 1371261 [details] screenshot 2017-12-22 Still a problem in version ovirt-node-ng-installer-master-2017122109
Didn't meet this issue. Test version: cockpit-ovirt-dashboard-0.11.3-0.1.el7ev.noarch rhvh-4.2.0.6-0.20171218.0+1 google-chrome-stable-61.0.3163.91-1.x86_64 firefox-55.0.3-1.fc26.x86_64 Test steps: 1. Install RHVH4.2 2. Deploy SHE Test results: 1. Deploy successfully with Firefox or Chrome.
(In reply to Bernhard Seidl from comment #6) > Created attachment 1371261 [details] > screenshot 2017-12-22 > > Still a problem in version ovirt-node-ng-installer-master-2017122109 Bernhard, I see the screenshot attachment:1371261, the labels on that screenshot didn't have a gray background， so why is still a problem and I didn't meet this issue.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
(In reply to Yihui Zhao from comment #8) > (In reply to Bernhard Seidl from comment #6) > > Created attachment 1371261 [details] > > screenshot 2017-12-22 > > > > Still a problem in version ovirt-node-ng-installer-master-2017122109 > > Bernhard, I see the screenshot attachment:1371261, the labels on that > screenshot didn't have a gray background， so why is still a problem and I > didn't meet this issue. The checkbox labeled "Engine Setup" is one of the controlls unaccessable. This bug apply only to controls at the end of dialog box.
Created attachment 1377497 [details] Screenshot of VM step in Chrome emulated at 1920x1200
Created attachment 1377498 [details] Screenshot of VM step in Firefox emulated at 1920x1200
Bernhard, I have been unable to emulate your issue. I've attached screenshots of what I see in FF and Chrome using the screen size emulators.
Bernhard, I finally have a system with the issue replicated on it and think I've figured out what's going on. It appears that Patternfly has made changes to their wizard CSS styles that are causing the problem you're seeing. Specifically, removing the following additions fixed the problem for me. wizard-pf-footer: -- position: absolute wizard-pf-row: -- bottom: 58px -- top: 172px -- position: absolute
Bernhard, Could you follow the solution from the comment 14 to try again? I didn't meet this issue with my ENV.
Yihui, the solution from comment #14 solved it.
(In reply to Bernhard Seidl from comment #16) > Yihui, > > the solution from comment #14 solved it. OK, Thanks, So Could I change the bug's status to verified?
(In reply to Yihui Zhao from comment #17) > (In reply to Bernhard Seidl from comment #16) > > Yihui, > > > > the solution from comment #14 solved it. > > OK, Thanks, So Could I change the bug's status to verified? From the comment 15, I didn't meet this issue with my ENV, So could you help to verify this bug?
Sure, I can help verifying this bug and from my perspective this bug can be considered to be verified.
Created attachment 1382383 [details] Screenshot - CentOS 7
I'm still showing this issue as recently as yesterday when running Cockpit on a CentOS machine. See the attachment in comment 20. Moving this back to ASSIGNED for now.
Phillip, I cannot verified this bug because I never met this issue. I saw the comment 16, Bernhard didn't meet this issue with the solution. But you met this issue again, now the bug' status is ON_QA, so could you meet this issue again? If didn't meet, I will change the bug's status to verified!
(In reply to Yihui Zhao from comment #22) > Phillip, > I cannot verified this bug because I never met this issue. I saw the > comment 16, Bernhard didn't meet this issue with the solution. > > But you met this issue again, now the bug' status is ON_QA, so could you > meet this issue again? If didn't meet, I will change the bug's status to > verified! I haven't seen this problem again since I made the associated changes.
According to the comment 23, I will change the bug's status to verified! If have the same issue again, please reopen the bug.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.