Bug 964644

Summary:	webadmin [TEXT]: unclear warning when exporting a vm dependent on template without the template
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Dafna Ron <dron>
Component:	ovirt-engine-webadmin-portal	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ori Gofen <ogofen>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acanan, amureini, bsettle, ecohen, iheim, laravot, rbalakri, Rhev-m-bugs, scohen, tnisan
Target Milestone:	---
Target Release:	3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	storage
Fixed In Version:	ovirt-engine-3.5.0_alpha1.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-16 19:10:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1106458, 1107945, 1111153, 1116815
Bug Blocks:	1142923, 1156165

Description Dafna Ron 2013-05-19 10:50:42 UTC

Description of problem:

if we export a vm without its template and remove the template from the setup 
the vm will no longer be usable. 

the warning that we give the user is the below:

The following templates are missing on the target Export Domain:
Template testt (for testtt)

I am not sure that this explain the remifications to the user. 

Version-Release number of selected component (if applicable):

sf17

How reproducible:

100%

Steps to Reproduce:
1. create a vm based on template
2. export the vm to an export domain without the template
3.
  
Actual results:

we get a warning that alerts the user that the vm is exported without its template but I am not sure that the user will understand why we need the template to be backed up as well. 

Expected results:

I think that further info should be added to the warning. 

Additional info:

Comment 1 Liron Aravot 2013-07-09 11:29:07 UTC

Chreryn, perhaps you have a suggestion for a clearer message to the user?

Comment 2 Ayal Baron 2013-09-09 05:04:31 UTC

Andy, any suggestions?

Comment 3 Cheryn Tan 2013-09-09 06:16:08 UTC

Liron, I'm really sorry for the late reply, this seems to have slipped through my filters. 

Maybe a warning like this would work:

"Virtual machine ${vm-name} was created from template ${template-name}, and cannot be used in a domain where ${template-name} does not exist. Export template ${template-name} to ${target-export-domain}."

Comment 4 Ayal Baron 2014-02-09 12:47:11 UTC

(In reply to Cheryn Tan from comment #3)
> Liron, I'm really sorry for the late reply, this seems to have slipped
> through my filters. 
> 
> Maybe a warning like this would work:
> 
> "Virtual machine ${vm-name} was created from template ${template-name}, and
> cannot be used in a domain where ${template-name} does not exist. Export
> template ${template-name} to ${target-export-domain}."

This is does not explain the the problem.
The problem is that the user is now exporting virtual machines which cannot function without the templates and these templates do not exist on the export domain.  This means that later, when the user will want to import these VMs back into the system or into another system this will only be possible if the templates have been already imported or if the user exports the templates to the export domain after exporting the VMs.

The message should be something like:
"The following virtual machines are based on templates which do not exist on the export domain and are required for the virtual machines to function. If you proceed you will not be able to import these virtual machines unless you already have the relevant templates on the target domains. Continue? yes/no"

Comment 5 Cheryn Tan 2014-02-28 02:10:50 UTC

(In reply to Ayal Baron from comment #4)
> (In reply to Cheryn Tan from comment #3)
> > Liron, I'm really sorry for the late reply, this seems to have slipped
> > through my filters. 
> > 
> > Maybe a warning like this would work:
> > 
> > "Virtual machine ${vm-name} was created from template ${template-name}, and
> > cannot be used in a domain where ${template-name} does not exist. Export
> > template ${template-name} to ${target-export-domain}."
> 
> This is does not explain the the problem.
> The problem is that the user is now exporting virtual machines which cannot
> function without the templates and these templates do not exist on the
> export domain.  This means that later, when the user will want to import
> these VMs back into the system or into another system this will only be
> possible if the templates have been already imported or if the user exports
> the templates to the export domain after exporting the VMs.
> 
> The message should be something like:
> "The following virtual machines are based on templates which do not exist on
> the export domain and are required for the virtual machines to function. If
> you proceed you will not be able to import these virtual machines unless you
> already have the relevant templates on the target domains. Continue? yes/no"

Thanks for the explanation Ayal. The new error message looks good.

Comment 6 Ori Gofen 2014-07-29 11:28:29 UTC

verified on beta.2

Comment 8 Allon Mureinik 2015-02-16 19:10:00 UTC

RHEV-M 3.5.0 has been released, closing this bug.