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

Bug 1563122

Summary:	Useless error message: 'Engine server is not responding' (NOT on hosted-engine, regular engine)
Product:	[oVirt] ovirt-engine	Reporter:	Yaniv Kaul <ykaul>
Component:	Backend.Core	Assignee:	Ravi Nori <rnori>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Eli Mesika <emesika>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bugs, lsvaty, mperina
Target Milestone:	ovirt-4.2.5	Flags:	rule-engine: ovirt-4.2+
Target Release:	4.2.5.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.5.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-31 15:28:26 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 2018-04-03 07:55:30 UTC

Description of problem:
Seen it first on o-s-t (never seen in the past, might be a 4.3 change?).

I suspect it's when we restart ovirt-engine after engine-config. The /var/log/ovirt-engine doesn't even yet contain relevant entries, so it prior to that log.

The error itself is useless for the user, as is.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.0-0.0.master.20180403052544.git5c455cf0.el7.centos.noarch

How reproducible:
Haven't tried.

Steps to Reproduce:
1. Run o-s-t. Currently, it fails on check for updates.

Comment 1 Martin Perina 2018-04-27 11:57:36 UTC

The error is produced by ovirt-engine-notifier, who inserts this event when it cannot contact engine, am I right Ravi? If so can we make this error a bit more understandable?

Comment 2 Sandro Bonazzola 2018-07-31 15:28:26 UTC

This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.5 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.