Bug 1083104
Summary: | engine-setup --offline does not update versionlock | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Yedidyah Bar David <didi> |
Component: | Setup.Engine | Assignee: | Simone Tiraboschi <stirabos> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.6.0 | CC: | bugs, didi, gklein, lsvaty, mgoldboi, rbalakri, sbonazzo, stirabos, yeylon, ylavi |
Target Milestone: | ovirt-3.6.2 | Keywords: | TestCaseNeeded |
Target Release: | 3.6.2 | Flags: | rule-engine:
ovirt-3.6.z+
rule-engine: blocker+ mgoldboi: planning_ack+ sbonazzo: devel_ack+ pstehlik: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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: | |
Embargoed: |
Description
Yedidyah Bar David
2014-04-01 13:35:04 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. Still relevant, AFAIK. 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. Re-targeting to 3.6.2 since it affects appliance setup in Hosted Engine setup workflow 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: /etc/yum/pluginconf.d/versionlock.list should contain ovirt-engine-webadmin-portal-3.6.{version}.el7.centos.noarch ovirt-engine-wildfly-8.2.1-1.el7.x86_64 ovirt-engine-restapi-3.6.{version}.el7.centos.noarch ovirt-engine-dbscripts-3.6.{version}.el7.centos.noarch ovirt-engine-userportal-3.6.{version}.el7.centos.noarch ovirt-engine-3.6.{version}.el7.centos.noarch ovirt-engine-backend-3.6.{version}.el7.centos.noarch ovirt-engine-wildfly-overlay-8.0.4-1.el7.noarch ovirt-engine-tools-3.6.{version}.el7.centos.noarch Please substitute {version} with the rpm version on disk. oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA verified in rhevm-setup-3.6.2.6-0.1.el6.noarch |