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

Bug 1580346

Summary:	Cluster properties 'Enable to set host/VM...' should be set by default (and hidden?)
Product:	[oVirt] ovirt-engine	Reporter:	Yaniv Kaul <ykaul>
Component:	Frontend.WebAdmin	Assignee:	Dana <delfassy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Eli Mesika <emesika>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bugs, emarcus, mperina
Target Milestone:	ovirt-4.3.0	Keywords:	EasyFix, Improvement, StudentProject
Target Release:	---	Flags:	rule-engine: ovirt-4.3+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.0_rc2	Doc Type:	Enhancement
Doc Text:	In this release, the cluster property "set maintenance reason" is enabled by default.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 07:45:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yaniv Kaul 2018-05-21 10:34:24 UTC

Description of problem:
We have 2 cluster properties:
- Enable to set VM maintenance reason
- Enable to set Host maintenance reason

1. Should be set to ON by default (checked)
2. Do not even need to appear in the UI - I don't see the point in disabling them. If you don't want to input a reason, don't.

I prefer removing them altogether, having them set to ON by default. It'll simplify a bit the UI and ensure these useful features are enabled by default.

Comment 1 Martin Perina 2018-11-30 15:59:13 UTC

Let's remove those settings from webadmin and by default enable to set maintenance reason in both UI and RESTAPI

Comment 2 Martin Perina 2019-01-16 11:56:51 UTC

Moving back to MODIFIED as RESTAPI verification requires new model as mentioned in https://gerrit.ovirt.org/96948

Comment 3 Sandro Bonazzola 2019-02-13 07:45:09 UTC

This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

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