Bug 1460609
| Summary: | Introduce ovirt-host package | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-distribution | Reporter: | Shirly Radco <sradco> | |
| Component: | ovirt-host | Assignee: | Sandro Bonazzola <sbonazzo> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavol Brilla <pbrilla> | |
| Severity: | high | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 4.1.2 | CC: | bugs, didi, dondavis, jcall, lsvaty, mperina, pbrilla, pstehlik, rbarry, sbonazzo, sradco, trichard | |
| Target Milestone: | ovirt-4.2.0 | Keywords: | FutureFeature | |
| Target Release: | 4.2.0 | Flags: | rule-engine:
ovirt-4.2+
pstehlik: testing_plan_complete- ylavi: planning_ack+ sbonazzo: devel_ack+ pstehlik: testing_ack+ |
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
A new package, ovirt-host, has been introduced, consolidating host package requirements into a single meta package.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1491203 (view as bug list) | Environment: | ||
| Last Closed: | 2017-12-20 11:29:43 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: | 1495854 | |||
| Bug Blocks: | 1380498, 1408942, 1429855, 1460708, 1461081, 1461083, 1491203, 1503442 | |||
|
Description
Shirly Radco
2017-06-12 08:05:20 UTC
Since 3.6 it's no longer true that all package dependencies on the host are handled by RPM dependency of VDSM. At the moment some we have several place where packages for the host required by oVirt are defined: 1. vdsm package dependencies (defined per VDSM version) 2. ovirt-host-deploy package list (defined per ovirt-host-deploy version) 3. Host upgrade manager package list (defined per cluster version) This status makes nearly impossible to achieve the same package status for different upgrade methods: 1. Manual 'yum update' on the host 2. Executing host 'Upgrade' from webadmin 3. Executing host 'Reinstall' from webadmin So we need to move host package dependencies on the host by create ovirt-host-X.Y.Z package which will define dependencies of the host for specific oVirt X.Y.Z What's the question? The goal should be: - In host deploy only this package is required to get all deps installed per arch, per version. - Engine only updates this package to get the oVirt deps updated - The node only requires this package to build. The host side holds the list of packages to update so that (to remove the need of engine being aware of the host version\arch): - Node host lists only the image rpm name to update. - RHEL-H only lists this meta-data package to update. (In reply to Yaniv Lavi from comment #3) > The goal should be: > - In host deploy only this package is required to get all deps installed per > arch, per version. ack > - Engine only updates this package to get the oVirt deps updated ack > - The node only requires this package to build. No, node and non-node hosts differ at least in imgbased and nodectl presence. We need to decide if we want to enforce all the other packages installed on node to be also installed on plain hosts. > The host side holds the list of packages to update so that (to remove the > need of engine being aware of the host version\arch): > - Node host lists only the image rpm name to update. > - RHEL-H only lists this meta-data package to update. Package is installable, 4.2 host to 4.2 engine SUCCESS This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |