Bug 1541947
Summary: | [TestOnly] engine-setup upgrade of postgres to pg95 using otopi answer-files | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Yedidyah Bar David <didi> |
Component: | Setup.Engine | Assignee: | Sandro Bonazzola <sbonazzo> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Novotny <pnovotny> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | --- | CC: | bugs, didi, irosenzw, lsvaty, ncredi, sbonazzo |
Target Milestone: | ovirt-4.2.2 | Keywords: | Regression, TestOnly |
Target Release: | 4.2.2.2 | Flags: | rule-engine:
ovirt-4.2+
rule-engine: blocker+ |
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1518697 | Environment: | |
Last Closed: | 2018-03-29 11:01:03 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: | |||
Bug Depends On: | 1396925 | ||
Bug Blocks: |
Description
Yedidyah Bar David
2018-02-05 09:46:59 UTC
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. QE: Please test the following: 1. Install and setup 4.1 engine 2. Add 4.2 repos and update setup packages 3. Take a snapshot of the machine 4. Run engine-setup, for upgrade, interactively, with only this in the answer file (or in the command line with '--otopi-environment='): DIALOG/answerFile=str:/tmp/ans1 5. Copy /tmp/ans1 somewhere 6. Revert the machine to the snapshot and copy back ans1 to /tmp 7. Run engine-setup --config-file=/tmp/ans1 See bug 1396925 for more information. (In reply to Yedidyah Bar David from comment #2) > QE: Please test the following: > > 1. Install and setup 4.1 engine > 2. Add 4.2 repos and update setup packages > 3. Take a snapshot of the machine > 4. Run engine-setup, for upgrade, interactively, with only this in the > answer file (or in the command line with '--otopi-environment='): > DIALOG/answerFile=str:/tmp/ans1 > 5. Copy /tmp/ans1 somewhere > 6. Revert the machine to the snapshot and copy back ans1 to /tmp > 7. Run engine-setup --config-file=/tmp/ans1 Sorry: engine-setup --config-append=/tmp/ans1 > > See bug 1396925 for more information. To clarify: I do not expect merely moving to VERIFIED once it works, but also that QE start to use it - at least in a reasonably-large subset of the tests you run, and including in cases like bug 1518697. Thanks! Verified in ovirt-engine-setup-4.2.2.4-0.1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.2.2.4-0.1.el7.noarch Verified by following the steps in comment 2. Upgrade from ovirt-engine-4.1.10.3-0.1.el7.noarch to ovirt-engine-4.2.2.4-0.1.el7.noarch # engine-setup --otopi-environment='DIALOG/answerFile=str:/tmp/answer.txt' then after restoring the machine to the same pre-upgrade state: # engine-setup --config-append=/tmp/answer.txt Result: No manual interaction was required. All needed answers were provided by the Otopi answer file. # cat /tmp/answer.txt # OTOPI answer file, generated by human dialog [environment:default] QUESTION/1/UPGRADE_DBMS=str:yes QUESTION/1/ENGINE_VACUUM_FULL=str:no QUESTION/1/UPGRADE_PG_CONF_ENGINE=str:yes QUESTION/1/OVESETUP_UPDATE_FIREWALL=str:yes QUESTION/1/OVESETUP_DIALOG_CONFIRM_SETTINGS=str:ok QUESTION/1/OVESETUP_DIALOG_CONTINUE_UPGRADE=str:yes QUESTION/1/ovirt-provider-ovn=str:no QUESTION/1/UPGRADE_DBMS_CLEANUPOLD=str:no QUESTION/1/DWH_VACUUM_FULL=str:no QUESTION/1/OVESETUP_RPMDISTRO_PACKAGE_UPGRADE=str:yes This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 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. |