Created attachment 960635 [details] screenshot for rhevm options Description of problem: It should be better to keep consistent to name RHEV-Manager as RHEV-M in rhevh6.6 for rhev3.4.z instead of "oVirt Engine". Version-Release number of selected component (if applicable): rhevh-6.6-20141119.0.el6ev ovirt-node-3.0.1-19.el6.24.noarch How reproducible: 100% Steps to Reproduce: 1. Clean install rhevh-6.6-20141119.0.el6ev 2. Check the TUI page Actual results: 1. After step2, it display "oVirt Engine" instead of "RHEV-M". Expected results: 1. It should display "RHEV-M" to keep consistent with RHEV-Manager. Additional info:
I think there is already a fix for this in 3.5 we just need to backport it.
Hello Bronce, Could you please review this bug and provie the pm flag? Thanks!
Hello Pavel, Could you please review the QA flag for this bug? Thanks
For reference only, the iso rhev-hypervisor6-6.6-20141119.0.iso contain ovirt-node-plugin-vdsm-0.2.0-12.el6ev.noarch.
verified RHEV-M displayed @ RHEV-H 20141212.0.el7ev
Test version: rhev-hypervisor6-6.6-20150123.0.iso ovirt-node-3.0.1-19.el6.27.noarch Test step: 1. Clean install rhev-hypervisor6-6.6-20150123.0.iso 2. Check the TUI page Test result: 1. After step2, it display "oVirt Engine" instead of "RHEV-M". So this issue is not fixed in rhev-hypervisor6-6.6-20150123.0.iso. Change the status to assign.
(In reply to wanghui from comment #8) > Test version: > rhev-hypervisor6-6.6-20150123.0.iso > ovirt-node-3.0.1-19.el6.27.noarch ovirt-node-plugin-vdsm-0.1.1-29.el6ev.noarch > > Test step: > 1. Clean install rhev-hypervisor6-6.6-20150123.0.iso > 2. Check the TUI page > > Test result: > 1. After step2, it display "oVirt Engine" instead of "RHEV-M". > > So this issue is not fixed in rhev-hypervisor6-6.6-20150123.0.iso. Change > the status to assign.
This bug is only occurred in rhevh6.6 for rhev3.4.z, no such issue in rhev3.5. Due to this bug is for rhev3.5, so no need to change to assign.
RHEV 3.5.0 has been released. I am closing this bug, because it has been VERIFIED.