Bug 1861368

Summary:	grafana startup may take some time
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	Setup	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4.1.2	CC:	bugs, fk
Target Milestone:	ovirt-4.4.3	Keywords:	ZStream
Target Release:	4.4.3	Flags:	pm-rhel: ovirt-4.4+ pm-rhel: planning_ack+ pm-rhel: devel_ack+ lleistne: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-dwh-4.4.3	Doc Type:	Bug Fix
Doc Text:	Cause: systemd allows services up to 90 seconds to start, by default. grafana, on its first start, also does provisioning, which on a slow system might take a long time. Consequence: If grafana server took more than 90 seconds to start, this failed engine-setup. Fix: engine-setup was changed to temporarily configure systemd to allow up to 5 minutes for grafana to start. Result: grafana start and engine-setup now succeed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-02 11:33:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1879377

Description Michal Skrivanek 2020-07-28 12:32:22 UTC

seems hat on a slow server grafana may take significant time too start
I do have an extremely old and slow server, but it would be good to make the default timeout longer so that we don't see such issues in scale/loaded environment

Comment 2 Yedidyah Bar David 2020-07-28 12:39:26 UTC

We can try changing it once, if provisioning, using 'systemctl set-property'. I didn't actually try that yet.

Comment 3 Yedidyah Bar David 2020-08-26 10:30:58 UTC

(In reply to Yedidyah Bar David from comment #2)
> We can try changing it once, if provisioning, using 'systemctl
> set-property'. I didn't actually try that yet.

This does not work. I am going to create a (temporary?) file in /etc/systemd/system/grafana-server.service.d for this.

Comment 4 Yedidyah Bar David 2020-08-27 14:17:48 UTC

QE: Reproduction/verification steps:

Install engine+dwh rpms
mkdir -p /etc/systemd/system.conf.d
echo -e "[Manager]\nDefaultTimeoutStartSec=1" | tee /etc/systemd/system.conf.d/test1.conf
systemctl daemon-reload
engine-setup
rm /etc/systemd/system.conf.d/test1.conf
systemctl daemon-reload

With a broken build, engine-setup fails, while starting grafana.

With a fixed build, starting grafana succeeds, but engine-setup fails later :-), while starting websocket-proxy.

Comment 5 Yedidyah Bar David 2020-09-03 07:39:59 UTC

*** Bug 1872249 has been marked as a duplicate of this bug. ***

Comment 8 Sandro Bonazzola 2020-11-11 06:45:42 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.