Bug 1363900
| Summary: | Specific Host(s) radio button doesn't work | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | bill.james <bill.james> | ||||||||
| Component: | Frontend.Core | Assignee: | Phillip Bailey <phbailey> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 4.0.1 | CC: | acanan, bill.james, bugs, dfediuck, mgoldboi, michal.skrivanek | ||||||||
| Target Milestone: | ovirt-4.0.7 | Keywords: | TestOnly | ||||||||
| Target Release: | --- | Flags: | dfediuck:
ovirt-4.0.z?
dfediuck: ovirt-4.1? mgoldboi: planning_ack+ rule-engine: devel_ack? rule-engine: testing_ack? |
||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-01-09 12:35:33 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | 1365687 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1195955 [details]
Video of element being disabled when clicking above it
Bill, I just want to clarify things a bit. When you go to the "Host" side-tab of the "New VM" popup, and click on the "Specific Host(s)" radio button, it never becomes active, correct? I'm asking because I haven't been able to reproduce that specific behavior. However, I have discovered that clicking just above the hosts list will cause the element to become disabled. I have captured this in the attachment I have uploaded. Created attachment 1195980 [details]
example of issue
Video show how "Specific Host" option is not available in "new VM" option, but is available in "Run Once" option.
provided video showing the problem I am having. Yes I realize this may be an issue with just my installation but I don't have any idea how to fix the issue and the ovirt-users list has not had any suggestions, except open a bug. Please suggest some way to troubleshoot the issue. This is a dev cluster so I could just delete it and start over again. But part of the purpose is to verify 4.0 before we upgrade our production cluster. How can I be sure this same issue won't happen on prod upgrade, where deleting install is not an option? Thanks! Thanks for adding the video. I completely understand your concerns and will do everything I can to help identify the cause of the issue and correct it before resorting to the delete and start over stage. What browser are you using and what version? Have you tried using any other browser(s)? I believe I've identified the problem. I created an Ubuntu VM and used Firefox to access my engine. When the display resolution was at a low setting, the dialog appeared as yours does in the video and I was unable to select the "Specific Host(s)" radio button. Once I increased the resolution setting, the dialog was able to spread out, appearing as it does in my video, and I was able to select it without problem. Would it be possible for you to increase the display resolution on the machine you're using to see if this corrects the problem for you, as well? In the meantime, I'll be looking for a way to remove the screen resolution as a variable in the UI's behavior here. I asked one of my co-workers to try it, who has better monitors then me. His resolution is 1920x1080 and the radio button works fine for him. The highest I can go is 1280x1024. He is also using Firefox 44, while I'm using FF 48, on ubuntu 16.0.4.1. I also tried Chromium 51.0.2704.79, same problem. I guess I need to ask for better monitors! :-) haha... Well, better monitors are a great thing to have, but shouldn't be required to use the application properly. I'm looking into ways to avoid this from happening, so hopefully there'll be a fix in an upcoming version. Thanks for bringing this to our attention! Well, good news and bad news. 3 other people work just fine, only me has a problem. Even after swapping out my monitors. One of the other people is even running ubuntu 16.04 and FF 48 just like me. So maybe instead of rebuilding the ovirt cluster I need to rebuild my PC. *sigh* Interesting. I'm assuming the dialog didn't spread out once you switched out the monitors? At what resolution were the monitors set? 1920x1080 on both monitors. Just to make sure I understand you correctly, you're saying that the dialog doesn't spread out on your system, even at the 1920x1080 setting, correct? Oh, When I spread out the webbrowser window wider so the dialog box speard out wider the radio button now works! Yeah! So yes, having the browser window too small makes the radio button not work. Well, I'm glad we narrowed down the problem and that there's an easy interim solution. I talked to the UI/UX team and there is an on-going effort to update existing UI code to avoid issues like this in the future. I noted this bug as being blocked by the epic bug that's being used to track that effort (1365687). Please let me know if you have any other questions/concerns regarding this issue. This is working as expected once you have the browser window at the minimal size. |
Created attachment 1187214 [details] on-node1 is original node, qaprivate01 is the new one. Description of problem: (sorry if I assigned this to wrong group. Please reassign as appropriate.) When trying to create a new VM, on the Host tab, the "Specific Host(s)" button does not allow me to select it, even though I have 2 hosts listed, both are in UP status. No reason is given for why the button is not active. Version-Release number of selected component (if applicable): ovirt-engine-4.0.1.1-1.el7.centos.noarch vdsm-4.18.10-1.el7.x86_64 How reproducible: Not sure, only have 1 cluster running 4.0.1. Steps to Reproduce: 1. Upgrade ovirt-engine to 4.0.1. 2. Add new hardware node. 3. Try and add VMs to it. Actual results: Radio button not active so can't assign VM to node. I can start the VM on the other node and then migrate it to the new node fine. Expected results: Should be able to assign VMs to new node. Additional info: