Red Hat Bugzilla – Bug 806555
isOvirt functions should check for ovirt-node-*-release
Last modified: 2012-08-09 03:58:47 EDT
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):
Steps to Reproduce:
1. take latest jenkins ovirt-node-iso build
2. install and try to register
vdsm-reg fails to rename the bridge to ovirtmgmt because it fails to detect that it is on an ovirt-node based image
registration should pass
closing ON_QA bugs as oVirt 3.1 was released: