Bug 1261426
Summary: | [rhevh 7.2] Beta should display in plymouth | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | cshao <cshao> |
Component: | ovirt-node | Assignee: | Ryan Barry <rbarry> |
Status: | CLOSED ERRATA | QA Contact: | cshao <cshao> |
Severity: | medium | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.6.0 | CC: | cwu, fdeutsch, gklein, huiwa, huzhao, leiwang, lsurette, rbarry, yaniwang, ycui, ykaul |
Target Milestone: | ovirt-3.6.0-rc3 | Flags: | pm-rhel:
testing_plan_complete+
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-node-3.6.1-5.0.el7ev | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 14:37:20 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: |
Comment 1
Ying Cui
2015-10-15 05:13:07 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high This is a very easy fix, _but_ it should be done by whomever is doing the next RHEV-H build Test version: rhev-hypervisor7-7.2-20151112.1 ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch # cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor (Beta) release 7.2 (20151112.1.el7ev) Seem the position of "Beta" is not suitable. It should be: Red Hat Enterprise Virtualization Hypervisor release 7.2 (Beta) (20151112.1.el7ev) Please open a second bug to track the positioning of the Beta keyowrd, we can pull that bug into a beta refresh (In reply to Fabian Deutsch from comment #6) > Please open a second bug to track the positioning of the Beta keyowrd, we > can pull that bug into a beta refresh OK, verify this bug according #c5 & #c6. New bug 1284350 can trace the positioning of the Beta keyword issue. 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-0378.html |