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

Bug 1321796

Summary:	Allow editing hosted engine VM
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Roy Golan <rgolan>
Component:	rhevm-setup-plugins	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED ERRATA	QA Contact:	Artyom <alukiano>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6.3	CC:	bgraveno, gklein, lsurette, mgoldboi, sbonazzo, ykaul
Target Milestone:	ovirt-3.6.5	Keywords:	Triaged, ZStream
Target Release:	3.6.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	It is now possible to edit the self-hosted engine Manager virtual machine. Before version 3.6.5, a configuration value prevented the self-hosted engine Manager virtual machine from being edited because the functionality was not available. A plugin automatically changed the default configuration value from true to false, which prevented editing. The functionality to edit the self-hosted engine Manager virtual machine is now available, and therefore the plugin has been removed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-20 17:04:17 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:
Bug Depends On:
Bug Blocks:	1160094

Description Roy Golan 2016-03-29 07:52:47 UTC

Following fixes for Bug 1160094, editing the hosted engine VM should be allowed by default and the current config value should be 'true' by default.

this reverts 8a3474d5de672917c06a782b19a6c9228208d28d

Comment 2 Artyom 2016-04-13 11:22:28 UTC

Verified on rhevm-3.6.5.3-0.1.el6.noarch
AllowEditingHostedEngine: true version: general

I believe we need to doc, that value will be equal to true just in case of clean install.

Comment 4 errata-xmlrpc 2016-04-20 17:04:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0656.html