Bug 1271111 - The message should show "Managed by: Engine https://XXXX" on the Status page after register to RHEVM successful.
Summary: The message should show "Managed by: Engine https://XXXX" on the Status page ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-3.6.1
: 3.6.1
Assignee: Douglas Schilling Landgraf
QA Contact: Chaofeng Wu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-13 08:02 UTC by Chaofeng Wu
Modified: 2016-03-09 14:40 UTC (History)
12 users (show)

Fixed In Version: ovirt-node-plugin-vdsm-0.6.1-2.el7ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 14:40:41 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
sosreport (5.38 MB, application/x-xz)
2015-10-13 08:03 UTC, Chaofeng Wu
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0378 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update for RHEV 3.6 2016-03-09 19:06:36 UTC
oVirt gerrit 47339 0 master MERGED engine_page: fix parms name to update /etc/default/ovirt Never
oVirt gerrit 47368 0 ovirt-3.6 MERGED engine_page: fix parms name to update /etc/default/ovirt Never

Description Chaofeng Wu 2015-10-13 08:02:18 UTC
Description of problem:
After register to RHEV-M3.6 successful, "Managed by: Engine https://XXXXX" should show on Status page.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.2-20151009.0.iso
ovirt-node-3.3.0-0.13.20151008git03eefb5.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. TUI install rhev-hypervisor7-7.2-20151009.0.iso and configure network with DHCP mode.
2. Register to RHEV-M on Engine page.
3. Approve on RHEV-M portal.

Actual results:
After step3, the system status is up on RHEV-M portal, on Status page still show "Status: Virtualization hardware was detected and is enabled" on RHEV-H. And Engine ip address does not show on Engine page.

Expected results:
After step3, the system status is up on RHEV-M portal, on Status page should show "Managed by: Engine https://XXXXX" on RHEV-H. And Engine ip address should show on Engine page.

Additional info:
This issues only happen with TUI installation, the CMD installation with parameter management_server does not seen this issue.

Do not find MANAGED_BY key word in /etc/default/ovirt after the RHEV-H registered successful.
[root@ibm-x3650m3-02 ~]# cat /etc/default/ovirt 
MANAGED_IFNAMES="ovirtmgmt"
OVIRT_BOOTIF="enp11s0f0"
OVIRT_BOOTPARAMS="ksdevice=bootif rd.dm=0 rd.md=0 crashkernel=256M lang= max_loop=256 rhgb quiet elevator=deadline rd.live.check rd.luks=0 rd.live.image"
OVIRT_BOOTPROTO="dhcp"
OVIRT_CONFIG_VERSION="3.3.0"
OVIRT_FIRSTBOOT="0"
OVIRT_INIT=""
OVIRT_INSTALL=""
OVIRT_INSTALL_ROOT="y"
OVIRT_KDUMP_LOCAL="true"
OVIRT_KEYBOARD_LAYOUT="us"
OVIRT_MANAGEMENT_SERVER=""
OVIRT_NODE_REGISTER="True"
OVIRT_ROOT_INSTALL="y"
OVIRT_SSH_PORT="22"
OVIRT_SSH_PWAUTH="yes"
OVIRT_STANDALONE="1"
OVIRT_UPGRADE=""
OVIRT_VOL_CONFIG_SIZE="5"
OVIRT_VOL_DATA_SIZE="396830"
OVIRT_VOL_EFI_SIZE="256"
OVIRT_VOL_LOGGING_SIZE="2048"
OVIRT_VOL_ROOT_SIZE="4300"
OVIRT_VOL_SWAP_SIZE="9969"
OVIRT_MANAGEMENT_PORT="None"

Comment 1 Chaofeng Wu 2015-10-13 08:03:35 UTC
Created attachment 1082294 [details]
sosreport

Comment 5 Chaofeng Wu 2015-11-12 13:31:17 UTC
Verified on the rhev-hypervisor7-7.2-20151104 build.

Version-Release number of selected component (if applicable):
ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch
rhev-hypervisor7-7.2-20151104.0.iso
ovirt-node-plugin-vdsm-0.6.1-2.el7ev.noarch

Steps:
1. Install rhev-hypervisor7-7.2-20151104
2. Register to RHEV-M

Result:
Register to RHEV-M successful and the status display correctly on the status page.

This bug is fixed, so change the status to VERIFIED.

Comment 7 errata-xmlrpc 2016-03-09 14:40:41 UTC
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


Note You need to log in before you can comment on or make changes to this bug.