Bug 1247058
Summary: | getVdsStas crashed if host have numa node with 0 memory | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Artyom <alukiano> |
Component: | vdsm | Assignee: | Roman Mohr <rmohr> |
Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.0 | CC: | bazulay, dfediuck, gklein, lpeer, lsurette, mavital, mgoldboi, rgolan, rmohr, ycui, yeylon, ykaul |
Target Milestone: | ovirt-3.6.0-rc | Keywords: | Triaged |
Target Release: | 3.6.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
NUMA nodes can exist without memory (for example, when hotswapping memory modules). This was not considered in VDSM, causing the statistics reporting mechanism (getVdsStats) to break. Now, this error has been fixed by explicitly checking for NUMA nodes with zero memory, and returning a memory usage of 100%.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 19:42:57 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: |
Description
Artyom
2015-07-27 09:00:56 UTC
I guess this issue could be serious if a memory card needs maintenance and is pooled out(or not placed beforhand) No on hit this yet but when they will we have no workaround. Engine should cope with 0 and will prevent pinning vms on this node. The fix is rather small so we should consider 3.5.z Moran, what's your view on adding this to 3.5.z? (In reply to Doron Fediuck from comment #2) > Moran, > what's your view on adding this to 3.5.z? small fix, which adds to stability is a valid zstream. but what would be the functional implications of using numa node without memory? (In reply to Moran Goldboim from comment #3) > (In reply to Doron Fediuck from comment #2) > > Moran, > > what's your view on adding this to 3.5.z? > > small fix, which adds to stability is a valid zstream. > but what would be the functional implications of using numa node without > memory? This is rare and probably a result of malfunction. This is why I'm not keen to add it to .z unless there's a specific request for it. Verified on vdsm-4.17.8-1.el7ev.noarch 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://rhn.redhat.com/errata/RHBA-2016-0362.html |