Bug 1322783 - [z-stream clone - 3.6.5] Network status shows "Unknown ovirtmgmt" after register to rhevm3.6 with HE configured
Summary: [z-stream clone - 3.6.5] Network status shows "Unknown ovirtmgmt" after regis...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-3.6.5
: 3.6.5
Assignee: Ryan Barry
QA Contact: cshao
URL:
Whiteboard:
Depends On: 1300188
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-31 10:43 UTC by rhev-integ
Modified: 2016-04-20 16:24 UTC (History)
13 users (show)

Fixed In Version: ovirt-node-3.6.1-9.0
Doc Type: Bug Fix
Doc Text:
Clone Of: 1300188
Environment:
Last Closed: 2016-04-20 16:24:23 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0664 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update for RHEV 3.6.5 2016-04-20 20:23:40 UTC
oVirt gerrit 53684 0 master MERGED Bridge.slave_for_nic needs to exclude vnet devices 2016-03-31 10:43:42 UTC
oVirt gerrit 55486 0 ovirt-3.6 MERGED Bridge.slave_for_nic needs to exclude vnet devices 2016-03-31 10:43:42 UTC

Comment 2 cshao 2016-04-01 04:00:48 UTC
Test Version: 
rhev-hypervisor7-7.2-20160330.0
ovirt-node-3.6.1-9.0.el7ev.noarch
ovirt-node-plugin-hosted-engine-0.3.0-7.el7ev.noarch
ovirt-hosted-engine-ha-1.3.5.2-1.el7ev.noarch
ovirt-hosted-engine-setup-1.3.5.0-1.el7ev.noarch
ovirt-node-plugin-vdsm-0.6.1-9.el7ev.noarch
rhevm-appliance-20160323.1-1.3.6

Test steps:
1. TUI clean install rhevh
2. Login rhevh, setup network via dhcp
3. Configure Hosted engine with correct steps.
4. Reboot host.
5. Focus on network status.

Test results:
Network status shows "connected ovirtmgmt" after register to rhevm3.6 with HE configured, and HE can work well.

So the bug is fixed, change bug status to VERIFIED.

Comment 5 errata-xmlrpc 2016-04-20 16:24:23 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-0664.html


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