Bug 1751734

Summary:	Shutdown and Stop reason for VM not saved to DB
Product:	[oVirt] ovirt-engine	Reporter:	Liran Rotenberg <lrotenbe>
Component:	Backend.Core	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.3.6.5	CC:	bugs, rbarry
Target Milestone:	ovirt-4.4.0	Flags:	rbarry: ovirt-4.4?
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:	2019-09-13 13:29:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Liran Rotenberg 2019-09-12 13:17:37 UTC

Description of problem:
When we shut-down (gracefully or not) a VM we have an option to set the reason for the operation.

This bug is regarding the WEB-UI.
The REST API is fixed in bug 1450351.

Version-Release number of selected component (if applicable):
4.4.0 and ovirt-engine-4.3.6.5-0.1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Run a VM.
2. Shutdown / Power off the VM, set the reason for the operation.

Actual results:
VM went down as expected. There is no reason on the DB and no reason pointed out in the status column of the VM in the WEB-UI.

Expected results:
VM goes down, reason is in the DB -> WEB-UI will show the reason in the VM's status column

Comment 1 Ryan Barry 2019-09-13 13:29:16 UTC

Other half of the patch. I'll change the description on the other bug to reflect

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