Bug 1377196
| Summary: | RHVH 4.0_7.3 should be built against the latest RHEL 7.3 compose tree to keep all packages as newest. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | cshao <cshao> | ||||
| Component: | releng | Assignee: | Ryan Barry <rbarry> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Qin Yuan <qiyuan> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.0.0 | CC: | bugs, dguo, fdeutsch, gklein, huzhao, jboggs, jiawu, leiwang, lsurette, pbabinca, rbarry, srevivo, tmlcoch, weiwang, yaniwang, ycui, ykaul, yzhao | ||||
| Target Milestone: | ovirt-4.0.5 | Keywords: | Rebase, ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-11-22 17:02:46 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
We currently inheirt beta. This should probably be updated to something more recent. $ brew list-tag-inheritance rhevm-4.0-rhel-7.3-rhevh-next-build rhevm-4.0-rhel-7.3-rhevh-next-build (9717) … ├─rhel-7.3-beta-1.1-set (9710) Pavol, to me the question is: How should we proceed before a release? Should we - RHVH - update the tree for each new tag which is produced by RHEL beta/rc or is there another way - i.e. a RHEL tag always referencing the latest beta/rc builds? In one solution we'll need to always update our tree, in the other solution, RHEL would provide a stable tag. (In reply to Fabian Deutsch from comment #1) > In one solution we'll need to always update our tree, in the other solution, > RHEL would provide a stable tag. The normal way is to update our tree, but +1 for a stable tag from the most recent successful compose. Test version: redhat-virtualization-host-4.0-20161107.0 imgbased-0.8.7-0.1.el7ev.noarch Test steps: 1. Install RHVH. 2. Login RHVH. 3. Check main packages. Test results： redhat-virtualization-host-4.0-20161107.0 imgbased-0.8.7-0.1.el7ev.noarch kernel-3.10.0-514.el7.x86_64 vdsm-4.18.15.2-1.el7ev.x86_64 qemu-kvm-rhev-2.6.0-27.el7.x86_64 ovirt-hosted-engine-ha-2.0.4-1.el7ev.noarch ovirt-hosted-engine-setup-2.0.3-2.el7ev.noarch All pkgs are in consistent with the latest RHEL 7.3 compose tree. So the bug is fixed, change bug status to VERIFIED. 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/RHBA-2016-2813.html |
Created attachment 1202327 [details] /var/log/*.*; /tmp/log; sosreport; ks Description of problem: Build RHVH 40_7.3 build should be with the latest RHEL 7.3 compose tree to keep all pkgs in post. e.g. 1. RHVH 40_73 include wrong kernel package.(The latest one: kernel-3.10.0-507.el7) 2. RHVH 40_73 include wrong libvirt package.(The latest one: libvirt-2.0.0-9.el7) Version-Release number of selected component (if applicable): redhat-virtualization-host-4.0-20160912.1 kernel-3.10.0-493.el7.x86_64 libvirt-client-2.0.0-4.el7.x86_64 libvirt-daemon-2.0.0-4.el7.x86_64 imgbased-0.8.4-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHVH via ks file in attachment. 2. Login RHVH. 3. Check main packages. Actual results: Build RHVH 40_7.3 build didn't used the latest RHEL 7.3 compose tree. Expected results: Build RHVH 40_7.3 build should be with the latest RHEL 7.3 compose tree to keep all pkgs in post. Additional info: