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
Created attachment 1162380 [details] All the logs in RHEVH, kickstart file and screenshot in rhevm
Huijuan, is this bug gone on new respin build rhev-hypervisor7-ng-4.0-20160527.0?
(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.
According to comment 5, I will change the status to verified.
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