Bug 1083104

Summary: engine-setup --offline does not update versionlock
Product: [oVirt] ovirt-engine Reporter: Yedidyah Bar David <didi>
Component: Setup.EngineAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: urgent    
Version: 3.6.0CC: bugs, didi, gklein, lsvaty, mgoldboi, rbalakri, sbonazzo, stirabos, yeylon, ylavi
Target Milestone: ovirt-3.6.2Keywords: TestCaseNeeded
Target Release: 3.6.2Flags: rule-engine: ovirt-3.6.z+
rule-engine: blocker+
mgoldboi: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: a bug in engine-setup running in offline mode Consequence: cause version lock wasn't written inside the appliance on versions < 3.6.2: yum update cause ovirt-engine packages to be updated without a database update by engine-setup. Workaround (if any): avoid to use --offline on verson < 3.6.2; in hosted-engine deployment with the appliance avoid to use the automatic setup. When upgrading appliance from a previous version to 3.6.2 be sure to upgrade setup packages only: yum update "ovirt-engine-setup*" and then run engine-setup. Result:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 11:00:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Yedidyah Bar David 2014-04-01 13:35:04 UTC
Description of problem:

See Summary.

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


How reproducible:

Steps to Reproduce:
1. engine-setup --offline on a clean machine

Actual results:

yum versionlock is not updated

Expected results:

yum versionlock is updated

Additional info:

Comment 1 Sandro Bonazzola 2015-09-04 08:58:27 UTC
This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 2 Yedidyah Bar David 2015-09-16 07:07:33 UTC
Still relevant, AFAIK.

Comment 3 Red Hat Bugzilla Rules Engine 2015-10-19 10:53:51 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 4 Sandro Bonazzola 2015-12-11 15:56:07 UTC
Re-targeting to 3.6.2 since it affects appliance setup in Hosted Engine setup workflow

Comment 5 Simone Tiraboschi 2015-12-11 16:36:13 UTC
The patch http://gerrit.ovirt.org/50333 will fix for future executions of engine-setup.

Who run 'engine-setup --offline' in the past or used the engine appliance from hosted-engine-setup with unattended execution of engine-setup should manually fix their version-lock file before running yum update:

should contain 


Please substitute {version} with the rpm version on disk.

Comment 6 Sandro Bonazzola 2015-12-23 13:40:30 UTC
oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA

Comment 7 Lukas Svaty 2016-01-21 13:47:09 UTC
verified in rhevm-setup-