Bug 1387490 - cfme appliance image on rhv4 (ovirt) defaults eth0 to "rhevm" network.
Summary: cfme appliance image on rhv4 (ovirt) defaults eth0 to "rhevm" network.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Build
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Satoe Imaishi
QA Contact: Dave Johnson
URL:
Whiteboard: rhev:appliance:build
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-21 05:27 UTC by amogh
Modified: 2018-10-02 14:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: In rhv40, the default management network has changed to "ovirtmgmt" from "rhevm" Consequence: the appliance vm on rhv4.0, does not get the network/ip automatically assigned. Workaround (if any): We now provide qcow2 image as well as ova. Using qcow2 image is the current workaround? Result:
Clone Of:
Environment:
Last Closed: 2018-10-02 14:29:37 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description amogh 2016-10-21 05:27:32 UTC 
Description of problem:
cfme appliance image defaults the eth0 on "rhevm" network.

In rhv40, the default management network has changed to "ovirtmgmt" from "rhevm"  and therefor the appliance vm on rhv4.0, does not get the network/ip automatically assigned. 

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

How reproducible:
always

Steps to Reproduce:
1. download cfme ova image for qe from http://file.cloudforms.lab.eng.rdu2.redhat.com/builds/cfme/5.7/stable/
2. create template and deploy/configure vm on rhv4.0 (where 'ovirtmgmt' default mgmt network and there is no "rhevm" network)
3. observe that appliance vm does not get the ip/network automatically.
However, assigning the "ovirtmgmt" network to appliance vm manually works fine.

Actual results:
cfme appliance image defaults the eth0 on "rhevm" network.

Expected results:
the default network needs to be "ovirtmgmt" on rhv4. This information needs to be documented with default network details.


Additional info:
in the ovf file inside the ova, default net is set: <rasd:Caption>Ethernet 0 rhevm</rasd:Caption>
Comment 2 Satoe Imaishi 2016-10-21 13:39:41 UTC 
This issue was reported upstream here:
https://github.com/ManageIQ/manageiq/issues/358

Imagefactory has the value set to 'rhevm'. Since that option isn't exposed, we're not able to change either.

Will check where imagefactory bug is tracked internally.
Comment 3 Satoe Imaishi 2016-11-02 21:09:44 UTC 
A solution is being discussed...
Comment 4 Satoe Imaishi 2017-04-07 15:17:54 UTC 
We now provide qcow2 image as well as ova.  Although ova image still has this problem, can we lower priority/severity as using qcow2 image will be an easy workaround?
Comment 6 Josh Carter 2018-10-02 14:29:37 UTC 
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!
Comment 7 Josh Carter 2018-10-02 14:32:18 UTC 
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

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