Bug 749400 - Cannot add a rhev-h host to RHEV-M due to change in /etc/rhev-hypervisor-release file
Summary: Cannot add a rhev-h host to RHEV-M due to change in /etc/rhev-hypervisor-rele...
Keywords:
Status: CLOSED DUPLICATE of bug 748005
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhev-hypervisor6
Version: 6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 6.2
Assignee: Mike Burns
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-26 23:09 UTC by Mike Burns
Modified: 2016-04-26 14:59 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-27 13:38:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
vdsm-reg.log (3.80 KB, text/plain)
2011-10-26 23:09 UTC, Mike Burns 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike Burns 2011-10-26 23:09:01 UTC 
Created attachment 530402 [details]
vdsm-reg.log

Description of problem:
Approval of RHEV-H hosts fail due to an inability to change the name of the breth0 bridge to rhevm.

Version-Release number of selected component (if applicable):
vdsm-4.9-110

How reproducible:
Always

Steps to Reproduce:
1.Install RHEV-H
2.Add to rhev-m either through RHEV-M Add Host or through RHEV-H TUI
3.
  
Actual results:
if RHEV-M add host, sits in pending when it should auto-approve
if rhev-h tui, then fails to ever show up in rhev-m

Expected results:
add is completed successfully

Additional info:
Comment 1 Dan Kenigsberg 2011-10-27 13:09:35 UTC 
MainThread::ERROR::2011-10-26 23:08:23,219::deployUtil::785::root::makeBridge found existing bridge named: breth4

shows up only if fIsBridgeDevice and not fIsOvirt.

Could it be that os.path.exists('/etc/rhev-hypervisor-release') returns false?
Comment 2 Mike Burns 2011-10-27 13:32:56 UTC 
Yes, it does it does.  Rename from rhev-hypervisor to rhev-hypervisor6 had the unintended consequence of changing the file to /etc/rhev-hypervisor6-release.  

Moving to rhev-hypervisor6 component to be fixed.
Comment 3 Mike Burns 2011-10-27 13:38:57 UTC 

*** This bug has been marked as a duplicate of bug 748005 ***
Note You need to log in before you can comment on or make changes to this bug.