Bug 1861368 - grafana startup may take some time
Summary: grafana startup may take some time
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-dwh
Classification: oVirt
Component: Setup
Version: 4.4.1.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.3
: 4.4.3
Assignee: Yedidyah Bar David
QA Contact: Pavel Novotny
URL:
Whiteboard:
: 1872249 (view as bug list)
Depends On:
Blocks: 1879377
TreeView+ depends on / blocked
 
Reported: 2020-07-28 12:32 UTC by Michal Skrivanek
Modified: 2020-11-11 06:45 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-dwh-4.4.3
Clone Of:
Environment:
Last Closed: 2020-11-02 11:33:42 UTC
oVirt Team: Integration
Embargoed:
pm-rhel: ovirt-4.4+
pm-rhel: planning_ack+
pm-rhel: devel_ack+
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 110984 0 master MERGED packaging: setup: Give grafana more time to start 2020-10-30 11:22:06 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.