Bug 1566429

Summary: [RFE] Gluster jobs are scheduled even if there is no cluster configured to use it
Product: [oVirt] ovirt-engine Reporter: Roy Golan <rgolan>
Component: BLL.GlusterAssignee: Sahina Bose <sabose>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs
Target Milestone: ---Keywords: FutureFeature, Performance
Target Release: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-12 12:05:23 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:

Description Roy Golan 2018-04-12 09:58:34 UTC
Description of problem:

The engine has at least 6 scheduled jobs for the various gluster management taks.
Some of them are fired at rate of 5 seconds, 60, 300, 600. Every job like that would have to take cpu time, db connection, etc,  that we can really spare when the system doesn't need those jobs at all. Our default installation, with hosted engine, will configure a cluster support for both Virt and Gluster, but the default cluster itself is set to use virt only

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

How reproducible:
100%

Steps to Reproduce:
1. Setup which also has Gluster service enabled (set by engine-config or setup question)
2. All cluster must not have the "Gluster service" checked
3. Set the log level to DEBUG and see every 5 seconds gluster job, and wait more you'll see the rest

Actual results:
Gluster job are rescheduled while no one is using it.

Expected results:
Gluster jobs are paused and will be resumed only when a cluster with Gluser service will be checked.

Additional info: