Bug 1637815

Summary: engine-vacuum fails with 'vacuumdb: command not found'
Product: [oVirt] ovirt-engine Reporter: Miguel Martin <mmartinv>
Component: GeneralAssignee: Martin Perina <mperina>
Status: CLOSED CURRENTRELEASE QA Contact: Lucie Leistnerova <lleistne>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.6CC: bugs, mperina
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1637818 (view as bug list) Environment:
Last Closed: 2019-02-13 07:46:47 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:
Bug Depends On:    
Bug Blocks: 1637818    

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.