Bug 1340358 – Failed to add RHEV-H ng 4.0 to RHEV-M 4.0

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1340358 - Failed to add RHEV-H ng 4.0 to RHEV-M 4.0

Summary:	Failed to add RHEV-H ng 4.0 to RHEV-M 4.0

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	redhat-release-rhev-hypervisor (Show other bugs)
Sub Component:
Version:	4.0.0
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	ovirt-4.0.0-rc
Target Release:	---
Assigned To:	Ryan Barry
QA Contact:	Huijuan Zhao
Docs Contact:

URL:
Whiteboard:
Keywords:	TestBlocker

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-05-27 03:19 EDT by Huijuan Zhao
Modified:	2016-08-23 17:12 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-08-23 17:12:17 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Node
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
ovirt-host-deploy log in RHEV-M (233.69 KB, text/plain) 2016-05-27 03:19 EDT, Huijuan Zhao	no flags	Details
All the logs in RHEVH, kickstart file and screenshot in rhevm (6.04 MB, application/x-gzip) 2016-05-27 03:23 EDT, Huijuan Zhao	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:1688	normal	SHIPPED_LIVE	redhat-release-virtualization-host bug fix and enhancement update for RHV 4.0	2016-08-23 20:37:04 EDT

Groups: None (edit)

Description Huijuan Zhao 2016-05-27 03:19:46 EDT

Created attachment 1162379 [details]
ovirt-host-deploy log in RHEV-M

Description of problem:
Add RHEV-H ng 4.0 to RHEV-M 4.0 failed

Version-Release number of selected component (if applicable):
rhev-hypervisor7-ng-4.0-20160526.0
imgbased-0.6-0.1.el7ev.noarch
vdsm-4.18.0-0.el7ev.x86_64
Red Hat Enterprise Virtualization Manager Version: 4.0.0-0.7.master.el7ev

How reproducible:
100%
Keywords: blocker

Steps to Reproduce:
1. Install node ng 4.0
2. Add RHEV-H to RHEV-M 4.0

Actual results:
1. After step2, failed to add RHEV-H to RHEV-M, both cluster 4.0 and cluster 3.6 failed

Expected results:
1. After step2, should add RHEV-H to RHEV-M successful

Additional info:
Also add rhev-hypervisor7-ng-4.0-20160526.0 to RHEV-M 3.6 failed

Comment 1 Huijuan Zhao 2016-05-27 03:23 EDT

Created attachment 1162380 [details]
All the logs in RHEVH,   kickstart file and screenshot in rhevm

Comment 4 Ying Cui 2016-05-30 07:58:04 EDT

Huijuan, is this bug gone on new respin build rhev-hypervisor7-ng-4.0-20160527.0?

Comment 5 Huijuan Zhao 2016-05-30 22:10:09 EDT

(In reply to Ying Cui from comment #4)
> Huijuan, is this bug gone on new respin build
> rhev-hypervisor7-ng-4.0-20160527.0?

Ying, yes, this bug is fixed on new respin build rhev-hypervisor7-ng-4.0-20160527.0. 

Test Version:
rhev-hypervisor7-ng-4.0-20160527.0
imgbased-0.7.0-0.1.el7ev.noarch
vdsm-4.18.0-0.el7ev.x86_64
Red Hat Enterprise Virtualization Manager Version: 4.0.0-0.7.master.el7ev


Test Steps:
1. Install node ng 4.0
2. Add RHEV-H to RHEV-M 4.0

Test results:
1. After step2, add RHEV-H to RHEV-M successful

So this bug is fixed on build rhev-hypervisor7-ng-4.0-20160527.0. I will verify this bug once the status changing to ON_QA.

Comment 6 Huijuan Zhao 2016-05-30 22:52:38 EDT

According to comment 5, I will change the status to verified.

Comment 8 errata-xmlrpc 2016-08-23 17:12:17 EDT

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-1688.html

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