Bug 1135966 - [Event log] Wrong warning about available swap memory of host [1023MB], when actually host has [1024MB] memory size
Summary: [Event log] Wrong warning about available swap memory of host [1023MB], when ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.4.3
Assignee: Yaniv Bronhaim
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On: 1135909
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-01 10:37 UTC by Nir Yechiel
Modified: 2016-02-10 19:27 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1135909
Environment:
Last Closed: 2014-09-11 05:20:48 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nir Yechiel 2014-09-01 10:37:21 UTC 
+++ This bug was initially created as a clone of Bug #1135909 +++

Description of problem:
Wrong warning messages appears in the event log every 10-15 minutes, about available swap memory of host [1023MB]. When the actual swap memory size of host is [1024MB]

cat /proc/meminfo

SwapTotal:       1048568 kB (1023.99219 MB)
SwapFree:        1048568 kB (1023.99219 MB)

This warnings started to appear in the last build.

Version-Release number of selected component (if applicable):
 oVirt Engine Version: 3.5.0-0.0.master.20140821064931.gitb794d66.el6 

How reproducible:
always

Steps to Reproduce:
1. Working setup with host installed
2.
3.

Actual results:
Wrong warnings every 10-15 minutes in the event log about available swap memory of host.

Expected results:
Not see such warning messages in the event log.

Additional info:
Comment 1 Michael Burman 2014-09-01 10:43:59 UTC 
Also on build-  Red Hat Enterprise Virtualization Manager Version: 3.4.2-1.1.el6ev
Comment 2 Oved Ourfali 2014-09-07 08:38:33 UTC 
Seems like the truncation logic resides in VDSM.
It should round it up instead of truncating.
Moving it to VDSM.
Comment 3 Oved Ourfali 2014-09-11 05:20:48 UTC 
We will fix it for 3.5.0. Even if we do decide to fix it in 3.4.Z, it requires proper cloning through the jenkins job.
Note You need to log in before you can comment on or make changes to this bug.