Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1384462

Summary:	Hosted Engine deployment configuration available also in bare metal deployment
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	BLL.HostedEngine	Assignee:	Doron Fediuck <dfediuck>
Status:	CLOSED DUPLICATE	QA Contact:	meital avital <mavital>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.0.5.1	CC:	bugs, didi
Target Milestone:	ovirt-4.0.5	Flags:	sbonazzo: ovirt-4.0.z? sbonazzo: blocker? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-25 06:54:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***