Bug 1591751 - Recreate engine_cache dir during start and host deployment flows
Summary: Recreate engine_cache dir during start and host deployment flows
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.1.10
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Moti Asayag
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks: 1597574
TreeView+ depends on / blocked
 
Reported: 2018-06-15 12:54 UTC by Javier Coscia
Modified: 2021-12-10 16:41 UTC (History)
12 users (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
: 1597574 (view as bug list)
Environment:
Last Closed: 2019-05-08 12:37:41 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44225 0 None None None 2021-12-10 16:41:08 UTC
Red Hat Knowledge Base (Solution) 3487071 0 None None None 2018-06-15 14:50:56 UTC
Red Hat Product Errata RHEA-2019:1085 0 None None None 2019-05-08 12:38:00 UTC
oVirt gerrit 92436 0 master ABANDONED engine: Recreate engine_cache dir during start and host deployment flows 2018-07-05 18:28:41 UTC
oVirt gerrit 92542 0 master MERGED engine: Fail with a clear message if cache dir is missing 2018-06-26 16:19:26 UTC
oVirt gerrit 92558 0 ovirt-engine-4.2 MERGED engine: Fail with a clear message if cache dir is missing 2018-06-27 07:50:58 UTC

Description Javier Coscia 2018-06-15 12:54:03 UTC
Description of problem:

Engine won't start if entire /var/cache/ovirt-engine dir is missing/deleted. 

It will also would fail to upgrade / add a host into it with a misleading message "Failed to enroll certificate for host" instead of "cannot create tarball"


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

rhevm-4.1.10.3-0.1.el7.noarch
ovirt-engine-4.1.10.3-0.1.el7.noarch


How reproducible:

100%

Steps to Reproduce:
1. Move or remove /var/cache/ovirt-engine dir on engine system
2. Start ovirt-engine service

Another repro:

1. Start ovirt-engine service
2. Move or remove /var/cache/ovirt-engine dir on engine system
3. Try to upgrade or add a new host into the cluster

Actual results:

Engine cannot start or cannot add/upgrade host in cluster



Expected results:

Engine should be able to re-create this /var/cache/ovirt-engine dir while starting and while adding/upgrading host in clusters and print a clear message to the user

Comment 4 Moti Asayag 2018-06-26 16:24:09 UTC
In case of a missing /var/cache/ovirt-engine folder, the host-deploy will fail with the following error in engine.log:


2018-06-26 15:39:15,287+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-3) [664fcf70-7c86-410e-82be-7f58f29439c6] EVENT_ID: VDS_INSTALL_FAILED(505), Host zeus05.eng.lab.tlv.redhat.com installation failed. Cannot create file under directory '/var/cache/ovirt-engine', make sure directory exists and has suitable permissions (error: 'No such file or directory').

or

2018-06-26 15:39:15,271+03 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-3) [664fcf70-7c86-410e-82be-7f58f29439c6] Host installation failed for host 'cde4ebca-bf30-4048-a498-a0ef5fbfcfd5', 'zeus05.eng.lab.tlv.redhat.com': Cannot create file under directory '/var/cache/ovirt-engine', make sure directory exists and has suitable permissions (error: 'Permission denied')

Comment 5 RHV bug bot 2018-07-02 15:34:01 UTC
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops

Comment 7 Petr Matyáš 2018-12-11 15:20:32 UTC
Verified on ovirt-engine-4.3.0-0.6.alpha2.el7.noarch

Comment 9 errata-xmlrpc 2019-05-08 12:37:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2019:1085


Note You need to log in before you can comment on or make changes to this bug.