Bug 1609175
Summary: | [downstream clone - 4.2.6] ovirt-web-ui is not getting updating during engine-setup which is creating unexpected results | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
Component: | ovirt-engine | Assignee: | Michal Skrivanek <michal.skrivanek> |
Status: | CLOSED ERRATA | QA Contact: | Lucie Leistnerova <lleistne> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.4 | CC: | audgiri, didi, lsurette, lsvaty, michal.skrivanek, Rhev-m-bugs, srevivo, tburke |
Target Milestone: | ovirt-4.2.6 | Keywords: | Rebase, ZStream |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.2.6 | Doc Type: | Rebase: Bug Fixes and Enhancements |
Doc Text: | Story Points: | --- | |
Clone Of: | 1599525 | Environment: | |
Last Closed: | 2018-09-04 13:41:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1599525 | ||
Bug Blocks: |
Description
RHV bug bot
2018-07-27 08:17:23 UTC
we would add it to the list of packages updated by engine-setup. No need to lock/hide it really, but updating it as part of regular engine upgrade as makes sense. Didi, where exactly it should be added? (Originally by michal.skrivanek) (In reply to Michal Skrivanek from comment #1) > we would add it to the list of packages updated by engine-setup. No need to > lock/hide it really, but updating it as part of regular engine upgrade as > makes sense. > Didi, where exactly it should be added? In packaging/setup/ovirt_engine_setup/engine/constants.py : DEFAULT_ADDITIONAL_PACKAGES . (Originally by didi) Please note that you now just require it, by the engine, without any version. Is a new version compatible with an old engine? If not, this will fail: 1. Install and setup old engine (say, 4.1) 2. Add newer repo/channel (say, 4.2) 3. yum update (but do not run engine-setup) 4. restart engine? If you want to prevent that, either require/conflict with specific versions, or add also to versionlock. Or both. (Originally by didi) It is compatible, it’s just outdated when people only use engine-setup and not do full yum update (Originally by michal.skrivanek) engine-setup updated package ovirt-web-ui 1.2.1 to 1.3.9 successfully verified in ovirt-engine-4.2.6-0.1.el7ev.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/RHBA-2018:2623 |