Bug 1384462 - Hosted Engine deployment configuration available also in bare metal deployment
Summary: Hosted Engine deployment configuration available also in bare metal deployment
Keywords:
Status: CLOSED DUPLICATE of bug 1369827
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.HostedEngine
Version: 4.0.5.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.0.5
: ---
Assignee: Doron Fediuck
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-13 10:21 UTC by Sandro Bonazzola
Modified: 2017-05-11 09:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-25 06:54:27 UTC
oVirt Team: SLA
Embargoed:
sbonazzo: ovirt-4.0.z?
sbonazzo: blocker?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

Description Sandro Bonazzola 2016-10-13 10:21:13 UTC 
Description of problem:
Engine allows to deploy a host as hosted engine host even in a bare metal deployment

This shouldn't happen also because no configuration is available to be sent to host-deploy
Comment 1 Yedidyah Bar David 2016-10-13 12:35:46 UTC 
Perhaps change summary line, and change our terminology all-around, to 'standalone' instead of 'bare metal'. Engine can also run in a "normal" libvirt/kvm VM, and it can also run in a vm managed by another engine (not itself).
Comment 2 Doron Fediuck 2016-10-25 06:54:27 UTC 
See comment 1 in the duplicate bz:
"
It should allow to make a standard host an HE node /if hosted engine is already installed/.
"

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