Bug 1637815 - engine-vacuum fails with 'vacuumdb: command not found'
Summary: engine-vacuum fails with 'vacuumdb: command not found'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.2.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Martin Perina
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks: 1637818
TreeView+ depends on / blocked
 
Reported: 2018-10-10 07:13 UTC by Miguel Martin
Modified: 2019-02-13 07:46 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Clone Of:
: 1637818 (view as bug list)
Environment:
Last Closed: 2019-02-13 07:46:47 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.3+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 94821 0 master MERGED tools: engine-vacuum.sh must enable SCL if used by the engine. 2020-04-28 15:24:26 UTC

Description Miguel Martin 2018-10-10 07:13:55 UTC 
Description of problem:

engine-vacuum fails with 'vacuumdb: command not found'

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

How reproducible:
Always

Steps to Reproduce:
1. Open an SSH console to the oVirt manager
2. Run 'engine-vacuum' command

Actual results:
It fails with the error: 
~~~
[root@ovirt ~]# engine-vacuum
"/usr/bin/engine-vacuum: line 47: vacuumdb: command not found"
~~~

Expected results:
It should finish successfully:
~~~
[root@ovirt ~]# engine-vacuum
vacuumdb: vacuuming database "engine"
~~~

Additional info:
engine-vacuum does not load SCL environment.
Comment 1 Lucie Leistnerova 2018-12-11 07:35:17 UTC 
engine-vacuum works without manually enabling scl

verified in ovirt-engine-tools-4.3.0-0.6.alpha2.el7.noarch
Comment 2 Sandro Bonazzola 2019-02-13 07:46:47 UTC 
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

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