Bug 1295946 - oVirt appliance defaults to applicationMode=virt
Summary: oVirt appliance defaults to applicationMode=virt
Keywords:
Status: CLOSED DUPLICATE of bug 1295945
Alias: None
Product: ovirt-appliance
Classification: oVirt
Component: Core
Version: 3.6
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-05 20:57 UTC by Charlie Inglese
Modified: 2016-01-06 15:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-06 15:47:10 UTC
oVirt Team: ---
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Charlie Inglese 2016-01-05 20:57:53 UTC
Description of problem:
The oVirt appliance /root/ovirt-engine-answers file only support appliance mode virt.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.3.1.4-1.el7.centos.noarch
ovirt-engine-appliance-3.6-20151216.1.el7.centos.noarch

How reproducible:
Everytime

Steps to Reproduce:
1. Install oVirt engine appliance
2. Note /root/ovirt-engine-answers variables on ovirt-engine (applicationMode=virt)
3.

Actual results:
applicationMode=virt

Expected results:
applicationMode should be a cloudInit variable that can be passed in using the ovirt-hosted-engine answer file, or at least be defaulted to "Both"

Additional info:

Comment 2 Charlie Inglese 2016-01-06 15:47:10 UTC

*** This bug has been marked as a duplicate of bug 1295945 ***


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