Bug 1286660
Summary: | engine-setup should not depend on yum groups | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Sandro Bonazzola <sbonazzo> |
Component: | rhevm-setup-plugins | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Gonza <grafuls> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.0.0 | CC: | bazulay, bugs, didi, gklein, grafuls, lsurette, lsvaty, lveyde, melewis, pstehlik, rbalakri, Rhev-m-bugs, rmartins, sbonazzo, sherold, stirabos, yeylon, ykaul, ylavi |
Target Milestone: | ovirt-3.6.2 | ||
Target Release: | 3.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, engine-setup relied on a specific yum group to define a set of additional packages to be updated and if the group was not available for any reason these additional packages were not updated. Now, engine-setup has been changed and no longer relies on the specific yum group. Instead engine-setup now has this list hard-coded into it. The list of packages to upgrade is now independent of the yum repository management so that they remain updated.
|
Story Points: | --- |
Clone Of: | 1286558 | Environment: | |
Last Closed: | 2016-03-09 19:57:20 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: | 1286558 | ||
Bug Blocks: |
Description
Sandro Bonazzola
2015-11-30 12:36:14 UTC
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag. Changing the component because the fix is in a different package as sanity tests with yum passed on this codechange moving to verify tested with rhevm-3.6.2.6-0.1.el6.noarch Verified with upgrade from: rhevm-3.6.1-0.2.el6.noarch to: rhevm-3.6.2.6-0.1.el6.noarch Downgraded Otopi in the between upgrades: yum downgrade http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.0-14/el6/noarch/otopi-1.4.0-0.0.6.master.el6ev.noarch.rpm http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.0-14/el6/noarch/otopi-java-1.4.0-0.0.6.master.el6ev.noarch.rpm Upgrade completed successfully with the following: ... Setup has found updates for some packages: PACKAGE: [updated] ovirt-engine-extension-aaa-jdbc-1.0.3-1.el6ev.noarch PACKAGE: [update] ovirt-engine-extension-aaa-jdbc-1.0.5-1.el6ev.noarch PACKAGE: [updated] rhevm-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-backend-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-backend-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-branding-rhev-3.6.0-2.el6ev.noarch PACKAGE: [update] rhevm-branding-rhev-3.6.0-3.el6ev.noarch PACKAGE: [updated] rhevm-dbscripts-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-dbscripts-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-extensions-api-impl-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-extensions-api-impl-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-restapi-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-restapi-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-tools-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-tools-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-userportal-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-userportal-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-vmconsole-proxy-helper-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-vmconsole-proxy-helper-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-webadmin-portal-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-webadmin-portal-3.6.2.6-0.1.el6.noarch PACKAGE: [updated] rhevm-websocket-proxy-3.6.1-0.2.el6.noarch PACKAGE: [update] rhevm-websocket-proxy-3.6.2.6-0.1.el6.noarch ... Decided to drop the part about the answer file from the doc text, as it's not intended for direct end user manipulation, and not documented elsewhere. 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://rhn.redhat.com/errata/RHEA-2016-0395.html |