Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1424787

Summary:	'Available swap memory' warning should appear once a day, not every 30 minutes
Product:	[oVirt] ovirt-engine	Reporter:	Yaniv Kaul <ykaul>
Component:	Backend.Core	Assignee:	Oved Ourfali <oourfali>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.1.0	CC:	bugs, mperina, oourfali
Target Milestone:	ovirt-4.1.1	Keywords:	Improvement
Target Release:	4.1.1.3	Flags:	rule-engine: ovirt-4.1+ rule-engine: ovirt-4.2+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-21 09:42:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2017-02-19 13:12:49 UTC

Description of problem:
I'm getting the warning:
"Available swap memory of host lago-basic-suite-master-host0 [615 MB] is under defined threshold [1024 MB]."

every 30 minutes. There's no point in that, and with more hypervisors I would have received a lot more. Once a day should suffice.

Version-Release number of selected component (if applicable):
Master

How reproducible:
Always.

Steps to Reproduce:
1. Run ovirt-system-tests, which currently does not set enough swap for its VMs.
2. See that every 30 minutes you'll get such a warning.

Comment 1 Oved Ourfali 2017-02-20 07:35:52 UTC

I tend to agree.
The question is whether this should also apply to other values such as:
    VDS_HIGH_NETWORK_USE
    VDS_HIGH_CPU_USE
    VDS_HIGH_SWAP_USE
    VDS_LOW_SWAP

I guess maybe only the last two should change.

Comment 2 Yaniv Kaul 2017-02-20 07:55:17 UTC

(In reply to Oved Ourfali from comment #1)
> I tend to agree.
> The question is whether this should also apply to other values such as:
>     VDS_HIGH_NETWORK_USE
>     VDS_HIGH_CPU_USE
>     VDS_HIGH_SWAP_USE
>     VDS_LOW_SWAP
> 
> I guess maybe only the last two should change.

I don't think so - they are dynamic in nature - depending on the memory pressure, they'll come and go.

Comment 3 Israel Pinto 2017-04-05 12:42:09 UTC

Verify with: 4.1.1.7-0.1.el7
set swap to 1 GB and load host memory,
check the log for 2 hours.
message appear only one time.
Message:
2017-04-05 11:12:27,254+03 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler4) [433ab3c2] EVENT_ID: VDS_LOW_SWAP(536), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Available swap memory of host host_mixed_1 [262 MB] is under defined threshold [1024 MB].