subject:"\\\\\\\[ovirt\\\\\\\-users\\\\\\\] Error\\\\\\\: Storage format V3 is not supported"

Re: [ovirt-users] Error: Storage format V3 is not supported

2016-04-10 Thread Allon Mureinik

Patch was merged to master, should be available to you the next release.

On Thu, Apr 7, 2016 at 7:33 PM, Allon Mureinik  wrote:

> I've reproduced the issue on my env, and cooked up a patch that seems to
> solve it for me, in case anyone wants to cherry-pick and help verify it:
> https://gerrit.ovirt.org/#/c/55836
>
>
> On Wed, Apr 6, 2016 at 4:06 AM, Alex R  wrote:
>
>> Thank you!  This worked, though I wish I documented the process better
>>
>> Becuase I am not sure what I did exactly that helped?
>>
>> # cat
>> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
>>
>> CLASS=Backup
>> # changed
>> DESCRIPTION=eport_storage
>> IOOPTIMEOUTSEC=10
>> LEASERETRIES=3
>> LEASETIMESEC=60
>> LOCKPOLICY=
>> LOCKRENEWALINTERVALSEC=5
>> POOL_UUID=
>> # I removed this
>> REMOTE_PATH=..com:/mnt/export_ovirt/images # I
>> changed this to what is listed
>> ROLE=Regular
>> SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
>> TYPE=NFS
>> # changed
>> VERSION=0
>> # changed from 3 to 0   ### I have tried this before with no succes, so it
>> must be a combonation of other changes?
>> _SHA_CKSUM=16dac1d1c915c4d30433f35dd668dd35f60dc22c   # I
>> changed this to what was found in the logs
>>
>>
>>
>> -Alex
>>
>>
>>
>> On Sun, Apr 3, 2016 at 2:31 AM, Vered Volansky  wrote:
>>
>>> I've reported the issue:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1323462
>>>
>>> A verified workaround is to change the metadata Version to 0.
>>>
>>> Checksum should be compromised by it, so follow
>>> http://lists.ovirt.org/pipermail/users/2012-April/007149.html if you
>>> have any issues with adjusting it.
>>>
>>> Please let me know how this worked out for you.
>>>
>>> Regards,
>>> Vered
>>>
>>> On Thu, Mar 31, 2016 at 5:28 AM, Alex R  wrote:
>>>
 I am trying to import a domain that I have used as an export on a
 previous install.  The previous install was no older then v3.5 and was
 built with the all-in-one-plugin.  Before destroying that system I took a
 portable drive and made an export domain to export my VMs and templates.

 The new system is up to date an was built as a hosted engine.  When I
 try to import the domain I get the following error:

 "Error while executing action: Cannot add Storage. Storage format V3 is
 not supported on the selected host version."

 I just need to recover the VMs.

 I connect the USB hard drive to the host and make an export directory
 just like I did on the old host.

 # ls -ld /mnt/export_ovirt
 drwxr-xr-x. 5 vdsm kvm 4096 Mar  6 11:27 /mnt/export_ovirt

 I have tried both doing an NFS mount
 # cat /etc/exports.d/ovirt.exports
 /home/engineha  127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
 /mnt/backup-vm/ 10.3.1.0/24(rw,anonuid=36,anongid=36,all_squash)
 127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)

 # cat
 /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
 CLASS=Backup
 DESCRIPTION=eport_storage
 IOOPTIMEOUTSEC=10
 LEASERETRIES=3
 LEASETIMESEC=60
 LOCKPOLICY=
 LOCKRENEWALINTERVALSEC=5
 POOL_UUID=053926e4-e63d-450e-8aa7-6f1235b944c6
 REMOTE_PATH=/mnt/export_ovirt/images
 ROLE=Regular
 SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
 TYPE=LOCALFS
 VERSION=3
 _SHA_CKSUM=2e6e203168bd84f3dc97c953b520ea8f78119bf0

 # ls -l
 /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf

 -rw-r--r--. 1 vdsm kvm 9021 Mar  6 11:50
 /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf

 Thanks,
 Alex

 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users


>>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error: Storage format V3 is not supported

2016-04-07 Thread Allon Mureinik

I've reproduced the issue on my env, and cooked up a patch that seems to
solve it for me, in case anyone wants to cherry-pick and help verify it:
https://gerrit.ovirt.org/#/c/55836


On Wed, Apr 6, 2016 at 4:06 AM, Alex R  wrote:

> Thank you!  This worked, though I wish I documented the process better
>
> Becuase I am not sure what I did exactly that helped?
>
> # cat
> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
>
> CLASS=Backup
> # changed
> DESCRIPTION=eport_storage
> IOOPTIMEOUTSEC=10
> LEASERETRIES=3
> LEASETIMESEC=60
> LOCKPOLICY=
> LOCKRENEWALINTERVALSEC=5
> POOL_UUID=
> # I removed this
> REMOTE_PATH=..com:/mnt/export_ovirt/images # I
> changed this to what is listed
> ROLE=Regular
> SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
> TYPE=NFS
> # changed
> VERSION=0
> # changed from 3 to 0   ### I have tried this before with no succes, so it
> must be a combonation of other changes?
> _SHA_CKSUM=16dac1d1c915c4d30433f35dd668dd35f60dc22c   # I
> changed this to what was found in the logs
>
>
>
> -Alex
>
>
>
> On Sun, Apr 3, 2016 at 2:31 AM, Vered Volansky  wrote:
>
>> I've reported the issue:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1323462
>>
>> A verified workaround is to change the metadata Version to 0.
>>
>> Checksum should be compromised by it, so follow
>> http://lists.ovirt.org/pipermail/users/2012-April/007149.html if you
>> have any issues with adjusting it.
>>
>> Please let me know how this worked out for you.
>>
>> Regards,
>> Vered
>>
>> On Thu, Mar 31, 2016 at 5:28 AM, Alex R  wrote:
>>
>>> I am trying to import a domain that I have used as an export on a
>>> previous install.  The previous install was no older then v3.5 and was
>>> built with the all-in-one-plugin.  Before destroying that system I took a
>>> portable drive and made an export domain to export my VMs and templates.
>>>
>>> The new system is up to date an was built as a hosted engine.  When I
>>> try to import the domain I get the following error:
>>>
>>> "Error while executing action: Cannot add Storage. Storage format V3 is
>>> not supported on the selected host version."
>>>
>>> I just need to recover the VMs.
>>>
>>> I connect the USB hard drive to the host and make an export directory
>>> just like I did on the old host.
>>>
>>> # ls -ld /mnt/export_ovirt
>>> drwxr-xr-x. 5 vdsm kvm 4096 Mar  6 11:27 /mnt/export_ovirt
>>>
>>> I have tried both doing an NFS mount
>>> # cat /etc/exports.d/ovirt.exports
>>> /home/engineha  127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
>>> /mnt/backup-vm/ 10.3.1.0/24(rw,anonuid=36,anongid=36,all_squash)
>>> 127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
>>>
>>> # cat
>>> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
>>> CLASS=Backup
>>> DESCRIPTION=eport_storage
>>> IOOPTIMEOUTSEC=10
>>> LEASERETRIES=3
>>> LEASETIMESEC=60
>>> LOCKPOLICY=
>>> LOCKRENEWALINTERVALSEC=5
>>> POOL_UUID=053926e4-e63d-450e-8aa7-6f1235b944c6
>>> REMOTE_PATH=/mnt/export_ovirt/images
>>> ROLE=Regular
>>> SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
>>> TYPE=LOCALFS
>>> VERSION=3
>>> _SHA_CKSUM=2e6e203168bd84f3dc97c953b520ea8f78119bf0
>>>
>>> # ls -l
>>> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>>>
>>> -rw-r--r--. 1 vdsm kvm 9021 Mar  6 11:50
>>> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>>>
>>> Thanks,
>>> Alex
>>>
>>> ___
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error: Storage format V3 is not supported

2016-04-05 Thread Alex R

Thank you!  This worked, though I wish I documented the process better

Becuase I am not sure what I did exactly that helped?

# cat
/mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata

CLASS=Backup
# changed
DESCRIPTION=eport_storage
IOOPTIMEOUTSEC=10
LEASERETRIES=3
LEASETIMESEC=60
LOCKPOLICY=
LOCKRENEWALINTERVALSEC=5
POOL_UUID=
# I removed this
REMOTE_PATH=..com:/mnt/export_ovirt/images # I
changed this to what is listed
ROLE=Regular
SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
TYPE=NFS
# changed
VERSION=0
# changed from 3 to 0   ### I have tried this before with no succes, so it
must be a combonation of other changes?
_SHA_CKSUM=16dac1d1c915c4d30433f35dd668dd35f60dc22c   # I
changed this to what was found in the logs



-Alex



On Sun, Apr 3, 2016 at 2:31 AM, Vered Volansky  wrote:

> I've reported the issue:
> https://bugzilla.redhat.com/show_bug.cgi?id=1323462
>
> A verified workaround is to change the metadata Version to 0.
>
> Checksum should be compromised by it, so follow
> http://lists.ovirt.org/pipermail/users/2012-April/007149.html if you have
> any issues with adjusting it.
>
> Please let me know how this worked out for you.
>
> Regards,
> Vered
>
> On Thu, Mar 31, 2016 at 5:28 AM, Alex R  wrote:
>
>> I am trying to import a domain that I have used as an export on a
>> previous install.  The previous install was no older then v3.5 and was
>> built with the all-in-one-plugin.  Before destroying that system I took a
>> portable drive and made an export domain to export my VMs and templates.
>>
>> The new system is up to date an was built as a hosted engine.  When I try
>> to import the domain I get the following error:
>>
>> "Error while executing action: Cannot add Storage. Storage format V3 is
>> not supported on the selected host version."
>>
>> I just need to recover the VMs.
>>
>> I connect the USB hard drive to the host and make an export directory
>> just like I did on the old host.
>>
>> # ls -ld /mnt/export_ovirt
>> drwxr-xr-x. 5 vdsm kvm 4096 Mar  6 11:27 /mnt/export_ovirt
>>
>> I have tried both doing an NFS mount
>> # cat /etc/exports.d/ovirt.exports
>> /home/engineha  127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
>> /mnt/backup-vm/ 10.3.1.0/24(rw,anonuid=36,anongid=36,all_squash)
>> 127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
>>
>> # cat
>> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
>> CLASS=Backup
>> DESCRIPTION=eport_storage
>> IOOPTIMEOUTSEC=10
>> LEASERETRIES=3
>> LEASETIMESEC=60
>> LOCKPOLICY=
>> LOCKRENEWALINTERVALSEC=5
>> POOL_UUID=053926e4-e63d-450e-8aa7-6f1235b944c6
>> REMOTE_PATH=/mnt/export_ovirt/images
>> ROLE=Regular
>> SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
>> TYPE=LOCALFS
>> VERSION=3
>> _SHA_CKSUM=2e6e203168bd84f3dc97c953b520ea8f78119bf0
>>
>> # ls -l
>> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>>
>> -rw-r--r--. 1 vdsm kvm 9021 Mar  6 11:50
>> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>>
>> Thanks,
>> Alex
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error: Storage format V3 is not supported

2016-04-03 Thread Vered Volansky

I've reported the issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1323462

A verified workaround is to change the metadata Version to 0.

Checksum should be compromised by it, so follow
http://lists.ovirt.org/pipermail/users/2012-April/007149.html if you have
any issues with adjusting it.

Please let me know how this worked out for you.

Regards,
Vered

On Thu, Mar 31, 2016 at 5:28 AM, Alex R  wrote:

> I am trying to import a domain that I have used as an export on a previous
> install.  The previous install was no older then v3.5 and was built with
> the all-in-one-plugin.  Before destroying that system I took a portable
> drive and made an export domain to export my VMs and templates.
>
> The new system is up to date an was built as a hosted engine.  When I try
> to import the domain I get the following error:
>
> "Error while executing action: Cannot add Storage. Storage format V3 is
> not supported on the selected host version."
>
> I just need to recover the VMs.
>
> I connect the USB hard drive to the host and make an export directory just
> like I did on the old host.
>
> # ls -ld /mnt/export_ovirt
> drwxr-xr-x. 5 vdsm kvm 4096 Mar  6 11:27 /mnt/export_ovirt
>
> I have tried both doing an NFS mount
> # cat /etc/exports.d/ovirt.exports
> /home/engineha  127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
> /mnt/backup-vm/ 10.3.1.0/24(rw,anonuid=36,anongid=36,all_squash)
> 127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
>
> # cat
> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
> CLASS=Backup
> DESCRIPTION=eport_storage
> IOOPTIMEOUTSEC=10
> LEASERETRIES=3
> LEASETIMESEC=60
> LOCKPOLICY=
> LOCKRENEWALINTERVALSEC=5
> POOL_UUID=053926e4-e63d-450e-8aa7-6f1235b944c6
> REMOTE_PATH=/mnt/export_ovirt/images
> ROLE=Regular
> SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
> TYPE=LOCALFS
> VERSION=3
> _SHA_CKSUM=2e6e203168bd84f3dc97c953b520ea8f78119bf0
>
> # ls -l
> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>
> -rw-r--r--. 1 vdsm kvm 9021 Mar  6 11:50
> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>
> Thanks,
> Alex
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error: Storage format V3 is not supported

2016-03-31 Thread Alex R

Thanks for you suggestion Vered, but it is not working.

I copied all files except for 4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/
metadata

I even did a sha256sum on some of the files to verify:
62941ad5c53cb95ef211fbc11919872bae9b2c49f1fa37223162380b13b73a74  /mnt
/backup-vm
/0b7e96ae-f5e9-4fea-8cf6-33d39ef90162/images/1217e5a7-2cae-4662-a865-047acf2c831a/f84bfd41-622c-4078-a858-fd53a0d4e5ce

62941ad5c53cb95ef211fbc11919872bae9b2c49f1fa37223162380b13b73a74  /mnt
/export_ovirt
/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/images/1217e5a7-2cae-4662-a865-047acf2c831a/f84bfd41-622c-4078-a858-fd53a0d4e5ce

When I tried to import a VM or template the error was:
2016-03-31 12:18:45,090 ERROR [org.ovirt.engine.core.dal.dbbroker.
auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-8-thread-1)
[52c3dca3] Correlation ID: null, Call Stack: null, Custom Event ID: -1,
Message: VDSM command failed: Image is not a legal chain:
(u'1217e5a7-2cae-4662-a865-047acf2c831a',)
2016-03-31 12:18:45,090 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.
CopyImageVDSCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3] Command
'CopyImageVDSCommand( CopyImageVDSCommandParameters:{runAsync='true',
storagePoolId='0001-0001-0001-0001-0341',
ignoreFailoverLimit='false',
storageDomainId='0b7e96ae-f5e9-4fea-8cf6-33d39ef90162',
imageGroupId='1217e5a7-2cae-4662-a865-047acf2c831a',
imageId='f84bfd41-622c-4078-a858-fd53a0d4e5ce',
dstImageGroupId='1217e5a7-2cae-4662-a865-047acf2c831a',
vmId='4873de49-9090-40b1-a21d-665633109aa2',
dstImageId='f84bfd41-622c-4078-a858-fd53a0d4e5ce',
imageDescription='', dstStorageDomainId='e5597ac8-91db-4b9e-b9d3-26dd4cfdd07e',
copyVolumeType='SharedVol', volumeFormat='RAW', preallocate='Sparse',
postZero='false', force='false'})' execution failed: IRSGenericException:
IRSErrorException: Image is not a legal chain:
(u'1217e5a7-2cae-4662-a865-047acf2c831a',)
2016-03-31 12:18:45,091 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.
CopyImageVDSCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3] FINISH,
CopyImageVDSCommand, return: ----, log id:
250060f7
2016-03-31 12:18:45,091 ERROR [org.ovirt.engine.core.bll.
CopyImageGroupCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
Command 'org.ovirt.engine.core.bll.CopyImageGroupCommand' failed:
EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.
IrsOperationFailedNoFailoverException: IRSGenericException:
IRSErrorException: Image is not a legal chain:
(u'1217e5a7-2cae-4662-a865-047acf2c831a',) (Failed with error
ImageIsNotLegalChain and code 262)
2016-03-31 12:18:45,098 INFO  [org.ovirt.engine.core.bll.tasks.
AsyncTaskManager] (org.ovirt.thread.pool-8-thread-1) [52c3dca3] Removed
task 'ca149917-82dc-44a4-ae4c-fdeb6600ef05' from DataBase
2016-03-31 12:18:45,100 ERROR [org.ovirt.engine.core.bll.
CopyImageGroupCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
Transaction rolled-back for command 'org.ovirt.engine.core.bll
.CopyImageGroupCommand'.
2016-03-31 12:18:45,100 INFO  [org.ovirt.engine.core.utils.transaction.
TransactionSupport] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
transaction rolled back
2016-03-31 12:18:45,100 ERROR [org.ovirt.engine.core.bll.
ImportVmTemplateCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
Command 'org.ovirt.engine.core.bll.ImportVmTemplateCommand' failed:
EngineException: ImageIsNotLegalChain (Failed with error
ImageIsNotLegalChain and code 262)
2016-03-31 12:18:45,101 INFO  [org.ovirt.engine.core.bll.
ImportVmTemplateCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
Command [id=532f69a8-7eaa-4eda-8fe4-a2597c78fc8e]: Compensating
NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.network.
VmNetworkStatistics; snapshot: 4c699f71-7244-48dc-a57f-e76d48be4686.
2016-03-31 12:18:45,101 INFO  [org.ovirt.engine.core.vdsbroker.irsbroker.
GetVmsInfoVDSCommand] (default task-13) [] FINISH, GetVmsInfoVDSCommand,
log id: ddb9374
2016-03-31 12:18:45,101 INFO  [org.ovirt.engine.core.bll.
ImportVmTemplateCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
Command [id=532f69a8-7eaa-4eda-8fe4-a2597c78fc8e]: Compensating
NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.network.VmNic;
snapshot: 4c699f71-7244-48dc-a57f-e76d48be4686.
2016-03-31 12:18:45,102 INFO  [org.ovirt.engine.core.bll.
ImportVmTemplateCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
Command [id=532f69a8-7eaa-4eda-8fe4-a2597c78fc8e]: Compensating
NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage.
DiskImageDynamic; snapshot: f84bfd41-622c-4078-a858-fd53a0d4e5ce.
2016-03-31 12:18:45,102 INFO  [org.ovirt.engine.core.bll.
ImportVmTemplateCommand] (org.ovirt.thread.pool-8-thread-1) [52c3dca3]
Command [id=532f69a8-7eaa-4eda-8fe4-a2597c78fc8e]: Compensating
NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.storage.
DiskImage; snapshot: 1217e5a7-2cae-4662-a865-047acf2c831a.
2016-03-31 12:18:45,103 INFO  [org.ovirt.engine.core.bll.

Re: [ovirt-users] Error: Storage format V3 is not supported

2016-03-31 Thread Vered Volansky

Hi Alex,

This looks like a bug occurring with export domain on local storage, which
I'm currently trying to reproduce.
In the meantime, please try the following work around:

Create an export domain in your new setup.
Copy the images and vms directly to the mounted export directory (from old
export mount path to new export mount path)
Do not copy the metadata, it looks like this is the origin of the problem.

I will report back once I confirm the issue.

Regards,
Vered

On Thu, Mar 31, 2016 at 5:28 AM, Alex R  wrote:

> I am trying to import a domain that I have used as an export on a previous
> install.  The previous install was no older then v3.5 and was built with
> the all-in-one-plugin.  Before destroying that system I took a portable
> drive and made an export domain to export my VMs and templates.
>
> The new system is up to date an was built as a hosted engine.  When I try
> to import the domain I get the following error:
>
> "Error while executing action: Cannot add Storage. Storage format V3 is
> not supported on the selected host version."
>
> I just need to recover the VMs.
>
> I connect the USB hard drive to the host and make an export directory just
> like I did on the old host.
>
> # ls -ld /mnt/export_ovirt
> drwxr-xr-x. 5 vdsm kvm 4096 Mar  6 11:27 /mnt/export_ovirt
>
> I have tried both doing an NFS mount
> # cat /etc/exports.d/ovirt.exports
> /home/engineha  127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
> /mnt/backup-vm/ 10.3.1.0/24(rw,anonuid=36,anongid=36,all_squash)
> 127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
>
> # cat
> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
> CLASS=Backup
> DESCRIPTION=eport_storage
> IOOPTIMEOUTSEC=10
> LEASERETRIES=3
> LEASETIMESEC=60
> LOCKPOLICY=
> LOCKRENEWALINTERVALSEC=5
> POOL_UUID=053926e4-e63d-450e-8aa7-6f1235b944c6
> REMOTE_PATH=/mnt/export_ovirt/images
> ROLE=Regular
> SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
> TYPE=LOCALFS
> VERSION=3
> _SHA_CKSUM=2e6e203168bd84f3dc97c953b520ea8f78119bf0
>
> # ls -l
> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>
> -rw-r--r--. 1 vdsm kvm 9021 Mar  6 11:50
> /mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf
>
> Thanks,
> Alex
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Error: Storage format V3 is not supported

2016-03-30 Thread Alex R

I am trying to import a domain that I have used as an export on a previous
install.  The previous install was no older then v3.5 and was built with
the all-in-one-plugin.  Before destroying that system I took a portable
drive and made an export domain to export my VMs and templates.

The new system is up to date an was built as a hosted engine.  When I try
to import the domain I get the following error:

"Error while executing action: Cannot add Storage. Storage format V3 is not
supported on the selected host version."

I just need to recover the VMs.

I connect the USB hard drive to the host and make an export directory just
like I did on the old host.

# ls -ld /mnt/export_ovirt
drwxr-xr-x. 5 vdsm kvm 4096 Mar  6 11:27 /mnt/export_ovirt

I have tried both doing an NFS mount
# cat /etc/exports.d/ovirt.exports
/home/engineha  127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)
/mnt/backup-vm/ 10.3.1.0/24(rw,anonuid=36,anongid=36,all_squash)
127.0.0.1/32(rw,anonuid=36,anongid=36,all_squash)

# cat
/mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/dom_md/metadata
CLASS=Backup
DESCRIPTION=eport_storage
IOOPTIMEOUTSEC=10
LEASERETRIES=3
LEASETIMESEC=60
LOCKPOLICY=
LOCKRENEWALINTERVALSEC=5
POOL_UUID=053926e4-e63d-450e-8aa7-6f1235b944c6
REMOTE_PATH=/mnt/export_ovirt/images
ROLE=Regular
SDUUID=4be3f6ac-7946-4e7b-9ca2-11731c8ba236
TYPE=LOCALFS
VERSION=3
_SHA_CKSUM=2e6e203168bd84f3dc97c953b520ea8f78119bf0

# ls -l
/mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf

-rw-r--r--. 1 vdsm kvm 9021 Mar  6 11:50
/mnt/export_ovirt/images/4be3f6ac-7946-4e7b-9ca2-11731c8ba236/master/vms/4873de49-9090-40b1-a21d-665633109aa2/4873de49-9090-40b1-a21d-665633109aa2.ovf

Thanks,
Alex
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Error: Storage format V3 is not supported

Re: [ovirt-users] Error: Storage format V3 is not supported

Re: [ovirt-users] Error: Storage format V3 is not supported

Re: [ovirt-users] Error: Storage format V3 is not supported

Re: [ovirt-users] Error: Storage format V3 is not supported

Re: [ovirt-users] Error: Storage format V3 is not supported

[ovirt-users] Error: Storage format V3 is not supported

7 matches

Site Navigation

Mail list logo

Footer information