Bug 922507 - Don't let Quartz call home for updates
Summary: Don't let Quartz call home for updates
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.2.0
Assignee: Juan Hernández
QA Contact: Martin Pavlik
URL:
Whiteboard: infra
Depends On:
Blocks: 948448
TreeView+ depends on / blocked
 
Reported: 2013-03-17 14:48 UTC by Juan Hernández
Modified: 2016-02-10 19:20 UTC (History)
10 users (show)

Fixed In Version: sf11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Juan Hernández 2013-03-17 14:48:30 UTC 
The Quartz library that we use to schedule tasks connects to its web site to check for updates. This should be disabled.
Comment 1 Juan Hernández 2013-03-17 15:01:06 UTC 
The proposed change has already been merged upstream:

http://gerrit.ovirt.org/12411

It consists on adding the following to the standalone.xml file:

<system-properties>
  <property name="org.quartz.scheduler.skipUpdateCheck" value="true"/>
</system-properties>
Comment 3 Martin Pavlik 2013-05-15 10:16:39 UTC 
In SF17 change is present

[root@mp-rhevm32 ~]# grep system-properties -a2 /usr/share/ovirt-engine/service/engine-service.xml.in
  </extensions>

  <system-properties>
    <!-- Don't let quartz call home to check for updates: -->
    <property name="org.quartz.scheduler.skipUpdateCheck" value="true"/>
--
    <property name="org.apache.coyote.http11.Http11Protocol.COMPRESSION_MIME_TYPES" value="text/javascript,text/css,text/html,text/xml,text/json,application/x-yaml,application/xml,application/json"/>

  </system-properties>

  <profile>
Comment 4 Itamar Heim 2013-06-11 09:42:46 UTC 
3.2 has been released
Comment 5 Itamar Heim 2013-06-11 09:43:05 UTC 
3.2 has been released
Comment 6 Itamar Heim 2013-06-11 09:54:38 UTC 
3.2 has been released
Note You need to log in before you can comment on or make changes to this bug.