Bug 1599525
| Summary: | ovirt-web-ui is not getting updating during engine-setup which is creating unexpected results | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | nijin ashok <nashok> | |
| 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 | |
| Target Milestone: | ovirt-4.3.0 | Keywords: | Rebase, ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1609175 (view as bug list) | Environment: | ||
| Last Closed: | 2019-05-08 12:37:51 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1609175 | |||
|
Description
nijin ashok
2018-07-10 02:32:31 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? (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 . 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. It is compatible, it’s just outdated when people only use engine-setup and not do full yum update engine-setup updates ovirt-web-ui package verified in ovirt-engine-setup-4.3.0-0.0.master.20180903111244.git94dce75.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 sync2jira sync2jira |