Bug 806555

Summary: isOvirt functions should check for ovirt-node-*-release
Product: [Retired] oVirt Reporter: Mike Burns <mburns>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abaron, acathrow, bazulay, dyasny, iheim, ilvovsky, mburns, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm-4.10.0-4.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-09 07:58:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike Burns 2012-03-24 19:17:58 UTC
Description of problem:
ovirt-node images can contain different release files depending on how they were built.  Currently those files are "ovirt-node-image-release and ovirt-node-iso-release"  

vdsm currently depends on this file being ovirt-node-image-release causing engine registration to fail if it happens to be ovirt-node-iso-release.

Version-Release number of selected component (if applicable):
4.9.3.3

How reproducible:
Always

Steps to Reproduce:
1. take latest jenkins ovirt-node-iso build
2. install and try to register
3.
  
Actual results:
vdsm-reg fails to rename the bridge to ovirtmgmt because it fails to detect that it is on an ovirt-node based image

Expected results:
registration should pass

Additional info:

Comment 1 Mike Burns 2012-03-24 19:20:28 UTC
Possible patch:

http://gerrit.ovirt.org/3055

Comment 2 Itamar Heim 2012-08-09 07:58:47 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/