Bug 1289967
| Summary: | Fade "Numa Pinning" button, in case if VM pinned to host that does not have "NUMA Support" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||||
| Component: | Frontend.WebAdmin | Assignee: | Roman Mohr <rmohr> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.6.3 | CC: | bugs, dfediuck, gklein, mavital, mgoldboi, rmohr, sbonazzo | ||||||
| Target Milestone: | ovirt-3.6.3 | Keywords: | Reopened, Triaged | ||||||
| Target Release: | 3.6.3.3 | Flags: | rule-engine:
ovirt-3.6.z+
ykaul: exception+ mgoldboi: planning_ack+ rmohr: devel_ack+ mavital: testing_ack+ |
||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause:
As long as the alphabetically first host had numa support, the "Numa Pinning" pinning button was not greyed out.
Consequence:
It was possible to do numa pinning on hosts with just one numa node (which is the equivalent of no numa architecture) but saving the pinning failed because of correct backend validations. Backend validation was fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1279178
Fix:
Correctly detect in the UI if the currently selected host supports NUMA.
Result:
Greys out all numa related boxes and buttons in the UI when a host without numa support is selected.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-03-11 07:24:45 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: | 1265953 | ||||||||
| Bug Blocks: | 1279178 | ||||||||
| Attachments: |
|
||||||||
Fixed bug tickets must have target milestone set prior to fixing them. Please set the correct milestone and move the bugs back to the previous status after this is corrected. This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA Created attachment 1129005 [details]
screenshots
Checked on rhevm-backend-3.6.3.2-0.1.el6.noarch
Looks like now it works randomly, sometime it fade NUMA parameters for host with NUMA architecture, sometimes leave open NUMA parameters for host without NUMA architecture.
Also it fade all NUMA parameters and not only "NUMA pinning" button.
host with NUMA architecture
============================
alma05.qa.lab.tlv.redhat.com
alma06.qa.lab.tlv.redhat.com
host without NUMA architecture
============================
cyan-vdsg.qa.lab.tlv.redhat.com
See screenshots for more information
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 Artyom from comment #3) > Created attachment 1129005 [details] > screenshots > > Checked on rhevm-backend-3.6.3.2-0.1.el6.noarch > Looks like now it works randomly, sometime it fade NUMA parameters for host > with NUMA architecture, sometimes leave open NUMA parameters for host > without NUMA architecture. > Also it fade all NUMA parameters and not only "NUMA pinning" button. > > host with NUMA architecture > ============================ > alma05.qa.lab.tlv.redhat.com > alma06.qa.lab.tlv.redhat.com > > host without NUMA architecture > ============================ > cyan-vdsg.qa.lab.tlv.redhat.com > > See screenshots for more information The patch in Bug 1265953 solves this problem. You can work around it by selecting the preferred host, click on 'Any Host' and then select 'Specific' again. This is a very annoying error with a very isolated and simple fix (https://gerrit.ovirt.org/#/c/53364/2). The select box modified there is only used at this one place in the UI. Verified on rhevm-webadmin-portal-3.6.3.3-0.1.el6.noarch 1) add three hosts two with NUMA support and one without 2) change vm migration policy to "Not allow migration" 3) check numa parameters when check different specific host NUMA parameters close for non-NUMA host and opened for NUMA host |
Created attachment 1103871 [details] screenshot Description of problem: I have possibility to pin VNUMA node to PNUMA node also in case when host have one NUMA node(in our terms not support NUMA). Version-Release number of selected component (if applicable): rhevm-3.6.1.1-0.1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Create vm with one or more NUMA nodes and pin it to host without NUMA Support 2. 3. Actual results: Possible to pin VNUMA node to PNUMA node(via "Numa Pinning" button) Expected results: "Numa Pinning" button must be faded in case if vm pinned to host without "NUMA Support" Additional info: I believe we also need to add validation for REST api