Bug 1676461
| Summary: | engine-setup should mention WA for upgrade issues (ovirt-vmconsole) | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lukas Svaty <lsvaty> | |
| Component: | ovirt-engine | Assignee: | Yedidyah Bar David <didi> | |
| Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> | |
| Severity: | high | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 4.2.8-1 | CC: | fromani, lsurette, michal.skrivanek, mtessun, nsednev, Rhev-m-bugs, sbonazzo, sborella | |
| Target Milestone: | ovirt-4.3.1 | Keywords: | ZStream | |
| Target Release: | 4.3.0 | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-engine-4.3.1.1 | Doc Type: | Bug Fix | |
| Doc Text: |
updated by engine-setup. If an error occurs, engine-setup treats this is a failure and tries to rollback, which is a risky process. To work around this scenario, the package ovirt-engine-setup-plugin-ovirt-engine now requires ovirt-vmconsole 1.0.7-1. Updating the setup packages with yum should also update ovirt-vmconsole. If an error occurs, yum evaluates it as a non-fatal error. See also bug 1665197 for the actual error from ovirt-vmconsole.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1678580 (view as bug list) | Environment: | ||
| Last Closed: | 2019-05-08 12:39:10 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: | ||||
| Bug Blocks: | 1678580 | |||
|
Description
Lukas Svaty
2019-02-12 11:15:13 UTC
Let's check if problematic rpm is installed at the beginning of the setup, issue an error pointing to KB and exit. (In reply to Sandro Bonazzola from comment #1) > Let's check if problematic rpm is installed at the beginning of the setup, > issue an error pointing to KB and exit. I looked at the referenced bug 1665197 and do not see there any specific problematic rpm we can check about. AFAIU all current versions of ovirt-vmconsole are problematic to _upgrade_ (perhaps also remove?), and they are required by the engine, so we can't exit. A possible workaround for now can be to patch ovirt-engine-setup to require the currently-latest ovirt-vmconsole. This way, it will be upgraded while upgrading engine-setup, and if this fails, it's hopefully less dramatic than if engine-setup fails. (There isn't anymore rhevm-setup) Let's try with the solution proposed by didi. (In reply to Yedidyah Bar David from comment #3) > A possible workaround for now can be to patch ovirt-engine-setup to require > the currently-latest ovirt-vmconsole. Francesco, does this make sense? If so, which version should we require? I do not see a bump in the git repo after merging [1]. Can you please bump, and build for 4.2? Thanks. [1] https://gerrit.ovirt.org/97062 > This way, it will be upgraded while > upgrading engine-setup, and if this fails, it's hopefully less dramatic than > if engine-setup fails. Didi, I think it's a great workaround. You can require any version of ovirt-vmconsole. As far as I've seen the error is ignored when invoked on commandline. Francesco, it makes sense to proceed with that regardless when/how you fix ovirt-vmconsole for future (In reply to Michal Skrivanek from comment #9) > Didi, I think it's a great workaround. You can require any version of > ovirt-vmconsole. Not really - if I require e.g. 1.0.4 and the user already has that, engine-setup will still try to upgrade (to 1.0.6.) and might fail. > As far as I've seen the error is ignored when invoked on > commandline. Indeed. We decided to not ignore it in otopi, to be on the safe side - see bug 1493160. > Francesco, it makes sense to proceed with that regardless when/how you fix > ovirt-vmconsole for future *** Bug 1678765 has been marked as a duplicate of this bug. *** Verified on ovirt-engine-4.3.1.1-0.1.el7.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1085 |