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

Bug 1064060

Summary: Engine: unclear error message when trying to create a template when vm disk was created in nfs and target domain for template is iscsi
Product: [Retired] oVirt Reporter: Dafna Ron <dron>
Component: ovirt-engine-coreAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, amureini, gklein, iheim, yeylon
Target Milestone: ---   
Target Release: 3.4.1   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-08 13:38:27 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:
Attachments:
Description Flags
logs none

Description Dafna Ron 2014-02-11 22:27:05 UTC
Created attachment 862034 [details]
logs

Description of problem:

we do not support move of disk from sparse+raw to iscsi. 
when we have a vm with a disk which was created in nfs as raw+sparse and we try to create a template and move the nfs disk to the iscsi domain we will fail with the following: 

Error while executing action New VM Template: Incorrect Volume format

or from log: 

2014-02-11 17:04:50,773 ERROR [org.ovirt.engine.core.bll.CreateImageTemplateCommand] (ajp--127.0.0.1-8702-6) [6252c43a] Command org.ovirt.engine.core.bll.CreateImageTemplateCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.irsbroker.IrsOperationFailedNoFailoverException: IRSGenericException: IRSErrorException: Incorrect Volume format: ('00000000-0000-0000-0000-000000000000',) (Failed with error IncorrectFormat and code 202)

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

ovirt-engine-backend-3.4.0-0.7.beta2.el6.noarch

How reproducible:

100%

Steps to Reproduce:
1. create a pool with 1 iscsi and 1 nfs domains
2. create a vm with the 2 disks , one disk on the nfs domain
3. try to create a template from the vm and change the target domain to iscsi 

Actual results:

we fail with the following error:

ovirt-engine-backend-3.4.0-0.7.beta2.el6.noarch

Expected results:

1. if we have more than one disk I don't think the user will understand the problem 
2. "New VM Template" should be changed to a more human error (failed to create template $template name, disk $disk_name format is unsupported for the target domain. 

Additional info: logs

Comment 1 Itamar Heim 2014-02-16 08:23:56 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Ayal Baron 2014-02-17 17:04:27 UTC
might be a duplicate of bug 1063996

Comment 3 Allon Mureinik 2014-02-27 14:25:06 UTC
(In reply to Ayal Baron from comment #2)
> might be a duplicate of bug 1063996


I'm guessing the same patch will solve both issues, but I'd like to keep both BZs open for verification, since from a user perspective these are two different flows.

Comment 4 Sandro Bonazzola 2014-03-04 09:23:29 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 5 Allon Mureinik 2014-04-25 19:22:30 UTC
(In reply to Allon Mureinik from comment #3)
> (In reply to Ayal Baron from comment #2)
> > might be a duplicate of bug 1063996
> 
> 
> I'm guessing the same patch will solve both issues, but I'd like to keep
> both BZs open for verification, since from a user perspective these are two
> different flows.
Moving to MODIFIED by that logic.

Comment 6 Sandro Bonazzola 2014-05-08 13:38:27 UTC
This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.