[Users] Storage domain does not exist
After an normal "yum update" i am unable to get one of the storage
domains "UP".
My systems is running Centos 6.3.
If I try to activate the domain in GUI I got following errors:
-
2012-08-14 12:16:22,594 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Lock Acquired to object EngineLock
[exclusiveLocks= key:
org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
5de36f78-8303-401b-b6c3-e04091077f9e
2012-08-14 12:16:22,610 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Running command:
ActivateStorageDomainCommand internal: false. Entities affected : ID:
5de36f78-8303-401b-b6c3-e04091077f9e Type: Storage
2012-08-14 12:16:22,618 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Lock freed to object EngineLock
[exclusiveLocks= key:
org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
5de36f78-8303-401b-b6c3-e04091077f9e
2012-08-14 12:16:22,709 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
(pool-5-thread-50) [539cbd7e] START,
ActivateStorageDomainVDSCommand(storagePoolId =
64a0f560-b9a1-4c87-8a30-0967b4ce3c81, ignoreFailoverLimit = false,
compatabilityVersion = null, storageDomainId =
5de36f78-8303-401b-b6c3-e04091077f9e), log id: 152cc8c3
2012-08-14 12:16:25,050 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(pool-5-thread-50) [539cbd7e] Error code StorageDomainDoesNotExist and
error message IRSGenericException: IRSErrorException: Failed to
ActivateStorageDomainVDS, error = Storage domain does not exist:
('5de36f78-8303-401b-b6c3-e04091077f9e',)
2012-08-14 12:16:25,050 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(pool-5-thread-50) [539cbd7e]
IrsBroker::Failed::ActivateStorageDomainVDS due to: IRSErrorException:
IRSGenericException: IRSErrorException: Failed to
ActivateStorageDomainVDS, error = Storage domain does not exist:
('5de36f78-8303-401b-b6c3-e04091077f9e',)
2012-08-14 12:16:25,058 ERROR
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Command
org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand throw Vdc
Bll exception. With error message VdcBLLException:
org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException:
IRSGenericException: IRSErrorException: Failed to
ActivateStorageDomainVDS, error = Storage domain does not exist:
('5de36f78-8303-401b-b6c3-e04091077f9e',)
2012-08-14 12:16:25,074 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Command
[id=6db5eb90-af14-43f7-8494-d59528a77c27]: Compensating
CHANGED_STATUS_ONLY of
org.ovirt.engine.core.common.businessentities.storage_pool_iso_map;
snapshot: EntityStatusSnapshot [id=storagePoolId =
64a0f560-b9a1-4c87-8a30-0967b4ce3c81, storageId =
5de36f78-8303-401b-b6c3-e04091077f9e, status=InActive].
-
Ho can I try to resolv it?
Regards //Ricky
0xB88C0B63.asc
Description: application/pgp-keys
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[Users] Storage domain does not exist
Hi,
I'm doing a fresh 3.1 install. I'm having a problem attaching newly
created storage. I followed
http://wiki.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues.
I seem to be able to create the storage ok. If I create it with the
default NFS version option=autonegotiate, I get a 500 error and "storage
does not exist" in the logs when trying to attach it. I can verify that
subdirectories and files were created.
#ls -l /exports/data/*/*
/exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/dom_md:
total 8
-rw-rw. 1 vdsm kvm 0 Aug 29 11:50 ids
-rw-rw. 1 vdsm kvm 0 Aug 29 11:50 inbox
-rw-rw. 1 vdsm kvm 512 Aug 29 11:50 leases
-rw-r--r--. 1 vdsm kvm 298 Aug 29 11:50 metadata
-rw-rw. 1 vdsm kvm 0 Aug 29 11:50 outbox
/exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/images:
total 0
Then as a test if I create the storage with the NFS version option=v3, I
get an internal ovirt error and a stack.
I followed the wiki and have v3 set on the engine node and
NFS4_SUPPORT="no" set on the machine exporting the share. Mounting the
share and creating/deleting files works fine.
any ideas?
thx
with NFS version option=autonegotiate
==
, sharedLocks= ]
2012-08-29 11:52:10,747 INFO
[org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand]
(ajp--0.0.0.0-8009-1) [595866b1] Running command:
AddStoragePoolWithStoragesCommand internal: true. Entities affected :
ID: 872ed943-cda1-4ec6-a4ea-36b97e7eff5a Type: StoragePool
2012-08-29 11:52:10,790 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] START,
ValidateStorageServerConnectionVDSCommand(vdsId =
1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
----, storageType = NFS, connectionList = [{
id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1, connection:
small.basin.com:/exports/data };]), log id: 721507
2012-08-29 11:52:10,807 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] FINISH,
ValidateStorageServerConnectionVDSCommand, return:
{4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 721507
2012-08-29 11:52:10,808 INFO
[org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] Running command:
ConnectStorageToVdsCommand internal: true. Entities affected : ID:
aaa0----123456789aaa Type: System
2012-08-29 11:52:10,811 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] START, ConnectStorageServerVDSCommand(vdsId =
1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
----, storageType = NFS, connectionList = [{
id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1, connection:
small.basin.com:/exports/data };]), log id: 3b13fdd8
2012-08-29 11:52:11,045 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] FINISH, ConnectStorageServerVDSCommand,
return: {4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 3b13fdd8
2012-08-29 11:52:11,050 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStoragePoolVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] START,
CreateStoragePoolVDSCommand(vdsId =
1c3207f8-f08d-11e1-8379-438e839e5efb,
storagePoolId=872ed943-cda1-4ec6-a4ea-36b97e7eff5a, storageType=NFS,
storagePoolName=basindatacenter,
masterDomainId=8f1e9376-8303-4660-948f-a6704b041e2e,
domainsIdList=[8f1e9376-8303-4660-948f-a6704b041e2e], masterVersion=10),
log id: 52930390
2012-08-29 11:53:15,434 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--0.0.0.0-8009-1) [2ec11b86] Failed in CreateStoragePoolVDS method
2012-08-29 11:53:15,436 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--0.0.0.0-8009-1) [2ec11b86] Error code StorageDomainDoesNotExist
and error message VDSGenericException: VDSErrorException: Failed to
CreateStoragePoolVDS, error = Storage domain does not exist:
('8f1e9376-8303-4660-948f-a6704b041e2e',)
2012-08-29 11:53:15,438 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--0.0.0.0-8009-1) [2ec11b86] Command
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStoragePoolVDSCommand
return value
Class Name:
org.ovirt.engine.core.vdsbroker.vdsbroker.StatusOnlyReturnForXmlRpc
mStatus Class Name:
org.ovirt.engine.core.vdsbroker.vdsbroker.StatusForXmlRpc
mCode 358
mMessage Storage domain does not exist:
('8f1e9376-8303-4660-948f-a6704b041e2e',)
with NFS version option=v3
==
, sharedLocks= ]
2012-08-29 11:46:44,542 INFO
[org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand]
(pool-3-thread-49) [330e12ac] Running command:
AddStoragePoolWithStoragesCommand internal: false. Entities affected :
ID: 872ed943-cda1-4ec6-a4ea-36b97e7eff5a Type: StoragePool
20
Re: [Users] Storage domain does not exist
Hi Ricky can you please add the log of VDSM, also the full engine log.
Regards,
Maor
On 08/14/2012 01:22 PM, Ricky Schneberger wrote:
> After an normal "yum update" i am unable to get one of the storage
> domains "UP".
>
> My systems is running Centos 6.3.
>
> If I try to activate the domain in GUI I got following errors:
>
> -
>
> 2012-08-14 12:16:22,594 INFO
> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
> (pool-5-thread-50) [539cbd7e] Lock Acquired to object EngineLock
> [exclusiveLocks= key:
> org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
> 5de36f78-8303-401b-b6c3-e04091077f9e
> 2012-08-14 12:16:22,610 INFO
> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
> (pool-5-thread-50) [539cbd7e] Running command:
> ActivateStorageDomainCommand internal: false. Entities affected : ID:
> 5de36f78-8303-401b-b6c3-e04091077f9e Type: Storage
> 2012-08-14 12:16:22,618 INFO
> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
> (pool-5-thread-50) [539cbd7e] Lock freed to object EngineLock
> [exclusiveLocks= key:
> org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
> 5de36f78-8303-401b-b6c3-e04091077f9e
> 2012-08-14 12:16:22,709 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
> (pool-5-thread-50) [539cbd7e] START,
> ActivateStorageDomainVDSCommand(storagePoolId =
> 64a0f560-b9a1-4c87-8a30-0967b4ce3c81, ignoreFailoverLimit = false,
> compatabilityVersion = null, storageDomainId =
> 5de36f78-8303-401b-b6c3-e04091077f9e), log id: 152cc8c3
> 2012-08-14 12:16:25,050 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
> (pool-5-thread-50) [539cbd7e] Error code StorageDomainDoesNotExist and
> error message IRSGenericException: IRSErrorException: Failed to
> ActivateStorageDomainVDS, error = Storage domain does not exist:
> ('5de36f78-8303-401b-b6c3-e04091077f9e',)
> 2012-08-14 12:16:25,050 ERROR
> [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
> (pool-5-thread-50) [539cbd7e]
> IrsBroker::Failed::ActivateStorageDomainVDS due to: IRSErrorException:
> IRSGenericException: IRSErrorException: Failed to
> ActivateStorageDomainVDS, error = Storage domain does not exist:
> ('5de36f78-8303-401b-b6c3-e04091077f9e',)
> 2012-08-14 12:16:25,058 ERROR
> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
> (pool-5-thread-50) [539cbd7e] Command
> org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand throw Vdc
> Bll exception. With error message VdcBLLException:
> org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException:
> IRSGenericException: IRSErrorException: Failed to
> ActivateStorageDomainVDS, error = Storage domain does not exist:
> ('5de36f78-8303-401b-b6c3-e04091077f9e',)
> 2012-08-14 12:16:25,074 INFO
> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
> (pool-5-thread-50) [539cbd7e] Command
> [id=6db5eb90-af14-43f7-8494-d59528a77c27]: Compensating
> CHANGED_STATUS_ONLY of
> org.ovirt.engine.core.common.businessentities.storage_pool_iso_map;
> snapshot: EntityStatusSnapshot [id=storagePoolId =
> 64a0f560-b9a1-4c87-8a30-0967b4ce3c81, storageId =
> 5de36f78-8303-401b-b6c3-e04091077f9e, status=InActive].
> -
>
> Ho can I try to resolv it?
>
> Regards //Ricky
>
>
>
> ___
> 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: [Users] Storage domain does not exist
Ricky, Try do the following :
go to the meta data of the data storage (in the storage server
go to {storage_domain_name}/##/dom_md/metadata)
delete the chksum line _SHA_CKSUM=
try to activate the storage domain again the DC (it should fail again)
vdsm.log should print the computed cksum of the storage domain (Should
be an error there which say "Meta Data seal is broken (checksum
mismatch) computed_cksum = ")
copy the comuted chksum to the meta data (_SHA_CKSUM={new chksum number}
try to activate it again.
Hope it will fix that.
Mean while I'm checking what caused the bug.
Regards,
Maor
On 08/14/2012 02:53 PM, Ricky Schneberger wrote:
> Hi
>
> I attached the logs.
>
> //Ricky
>
> On 2012-08-14 12:56, Maor Lipchuk wrote:
>> Hi Ricky can you please add the log of VDSM, also the full engine log.
>>
>> Regards,
>> Maor
>>
>>
>> On 08/14/2012 01:22 PM, Ricky Schneberger wrote:
>>> After an normal "yum update" i am unable to get one of the storage
>>> domains "UP".
>>>
>>> My systems is running Centos 6.3.
>>>
>>> If I try to activate the domain in GUI I got following errors:
>>>
>>> -
>>>
>>> 2012-08-14 12:16:22,594 INFO
>>> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
>>> (pool-5-thread-50) [539cbd7e] Lock Acquired to object EngineLock
>>> [exclusiveLocks= key:
>>> org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
>>> 5de36f78-8303-401b-b6c3-e04091077f9e
>>> 2012-08-14 12:16:22,610 INFO
>>> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
>>> (pool-5-thread-50) [539cbd7e] Running command:
>>> ActivateStorageDomainCommand internal: false. Entities affected : ID:
>>> 5de36f78-8303-401b-b6c3-e04091077f9e Type: Storage
>>> 2012-08-14 12:16:22,618 INFO
>>> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
>>> (pool-5-thread-50) [539cbd7e] Lock freed to object EngineLock
>>> [exclusiveLocks= key:
>>> org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
>>> 5de36f78-8303-401b-b6c3-e04091077f9e
>>> 2012-08-14 12:16:22,709 INFO
>>> [org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
>>> (pool-5-thread-50) [539cbd7e] START,
>>> ActivateStorageDomainVDSCommand(storagePoolId =
>>> 64a0f560-b9a1-4c87-8a30-0967b4ce3c81, ignoreFailoverLimit = false,
>>> compatabilityVersion = null, storageDomainId =
>>> 5de36f78-8303-401b-b6c3-e04091077f9e), log id: 152cc8c3
>>> 2012-08-14 12:16:25,050 ERROR
>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
>>> (pool-5-thread-50) [539cbd7e] Error code StorageDomainDoesNotExist and
>>> error message IRSGenericException: IRSErrorException: Failed to
>>> ActivateStorageDomainVDS, error = Storage domain does not exist:
>>> ('5de36f78-8303-401b-b6c3-e04091077f9e',)
>>> 2012-08-14 12:16:25,050 ERROR
>>> [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
>>> (pool-5-thread-50) [539cbd7e]
>>> IrsBroker::Failed::ActivateStorageDomainVDS due to: IRSErrorException:
>>> IRSGenericException: IRSErrorException: Failed to
>>> ActivateStorageDomainVDS, error = Storage domain does not exist:
>>> ('5de36f78-8303-401b-b6c3-e04091077f9e',)
>>> 2012-08-14 12:16:25,058 ERROR
>>> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
>>> (pool-5-thread-50) [539cbd7e] Command
>>> org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand throw Vdc
>>> Bll exception. With error message VdcBLLException:
>>> org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException:
>>> IRSGenericException: IRSErrorException: Failed to
>>> ActivateStorageDomainVDS, error = Storage domain does not exist:
>>> ('5de36f78-8303-401b-b6c3-e04091077f9e',)
>>> 2012-08-14 12:16:25,074 INFO
>>> [org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
>>> (pool-5-thread-50) [539cbd7e] Command
>>> [id=6db5eb90-af14-43f7-8494-d59528a77c27]: Compensating
>>> CHANGED_STATUS_ONLY of
>>> org.ovirt.engine.core.common.businessentities.storage_pool_iso_map;
>>> snapshot: EntityStatusSnapshot [id=storagePoolId =
>>> 64a0f560-b9a1-4c87-8a30-0967b4ce3c81, storageId =
>>> 5de36f78-8303-401b-b6c3-e04091077f9e, status=InActive].
>>> -
>>>
>>> Ho can I try to resolv it?
>>>
>>> Regards //Ricky
>>>
>>>
>>>
>>> ___
>>> 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: [Users] Storage domain does not exist
Hi Jon,
This seems like a postgres database issue:
- Original Message -
> From: "Jon Thomas"
> To: users@ovirt.org
> Sent: Wednesday, August 29, 2012 7:08:45 PM
> Subject: [Users] Storage domain does not exist
>
> Hi,
>
> I'm doing a fresh 3.1 install. I'm having a problem attaching newly
> created storage. I followed
> http://wiki.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues.
>
>
> I seem to be able to create the storage ok. If I create it with the
> default NFS version option=autonegotiate, I get a 500 error and
> "storage
> does not exist" in the logs when trying to attach it. I can verify
> that
> subdirectories and files were created.
>
>
> #ls -l /exports/data/*/*
> /exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/dom_md:
> total 8
> -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 ids
> -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 inbox
> -rw-rw. 1 vdsm kvm 512 Aug 29 11:50 leases
> -rw-r--r--. 1 vdsm kvm 298 Aug 29 11:50 metadata
> -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 outbox
>
> /exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/images:
> total 0
>
> Then as a test if I create the storage with the NFS version
> option=v3, I
> get an internal ovirt error and a stack.
>
> I followed the wiki and have v3 set on the engine node and
> NFS4_SUPPORT="no" set on the machine exporting the share. Mounting
> the
> share and creating/deleting files works fine.
>
> any ideas?
>
> thx
>
>
> with NFS version option=autonegotiate
> ==
> , sharedLocks= ]
> 2012-08-29 11:52:10,747 INFO
> [org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand]
> (ajp--0.0.0.0-8009-1) [595866b1] Running command:
> AddStoragePoolWithStoragesCommand internal: true. Entities affected :
> ID: 872ed943-cda1-4ec6-a4ea-36b97e7eff5a Type: StoragePool
> 2012-08-29 11:52:10,790 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
> (ajp--0.0.0.0-8009-1) [2ec11b86] START,
> ValidateStorageServerConnectionVDSCommand(vdsId =
> 1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
> ----, storageType = NFS,
> connectionList = [{ id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1,
> connection: small.basin.com:/exports/data };]), log id: 721507
> 2012-08-29 11:52:10,807 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
> (ajp--0.0.0.0-8009-1) [2ec11b86] FINISH,
> ValidateStorageServerConnectionVDSCommand, return:
> {4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 721507
> 2012-08-29 11:52:10,808 INFO
> [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand]
> (ajp--0.0.0.0-8009-1) [2ec11b86] Running command:
> ConnectStorageToVdsCommand internal: true. Entities affected : ID:
> aaa0----123456789aaa Type: System
> 2012-08-29 11:52:10,811 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
> (ajp--0.0.0.0-8009-1) [2ec11b86] START,
> ConnectStorageServerVDSCommand(vdsId =
> 1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
> ----, storageType = NFS,
> connectionList = [{ id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1,
> connection: small.basin.com:/exports/data };]), log id: 3b13fdd8
> 2012-08-29 11:52:11,045 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
> (ajp--0.0.0.0-8009-1) [2ec11b86] FINISH,
> ConnectStorageServerVDSCommand, return:
> {4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 3b13fdd8
> 2012-08-29 11:52:11,050 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStoragePoolVDSCommand]
> (ajp--0.0.0.0-8009-1) [2ec11b86] START,
> CreateStoragePoolVDSCommand(vdsId =
> 1c3207f8-f08d-11e1-8379-438e839e5efb,
> storagePoolId=872ed943-cda1-4ec6-a4ea-36b97e7eff5a, storageType=NFS,
> storagePoolName=basindatacenter,
> masterDomainId=8f1e9376-8303-4660-948f-a6704b041e2e,
> domainsIdList=[8f1e9376-8303-4660-948f-a6704b041e2e],
> masterVersion=10),
> log id: 52930390
> 2012-08-29 11:53:15,434 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
> (ajp--0.0.0.0-8009-1) [2ec11b86] Failed in CreateStoragePoolVDS
> method
> 2012-08-29 11:53:15,436 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
> (ajp--0.0.0.0-8009-1) [2ec11b86] Error code StorageDomainDoesNotExist
> and error message VDSGenericException: VDSErrorException: Failed to
> CreateStoragePoolVDS, error = Storage domain does not exist:
> ('8f1e9376-8303-4660-948f-a6704b041e2e',)
> 2012-08-29 11:53:15,438 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerComm
Re: [Users] Storage domain does not exist
Hi Jon,
could you please attach also the VDSM logs?
Thank you,
Tomas
- Original Message -
From: "Jon Thomas"
To: users@ovirt.org
Sent: Wednesday, August 29, 2012 6:08:45 PM
Subject: [Users] Storage domain does not exist
Hi,
I'm doing a fresh 3.1 install. I'm having a problem attaching newly
created storage. I followed
http://wiki.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues.
I seem to be able to create the storage ok. If I create it with the
default NFS version option=autonegotiate, I get a 500 error and "storage
does not exist" in the logs when trying to attach it. I can verify that
subdirectories and files were created.
#ls -l /exports/data/*/*
/exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/dom_md:
total 8
-rw-rw. 1 vdsm kvm 0 Aug 29 11:50 ids
-rw-rw. 1 vdsm kvm 0 Aug 29 11:50 inbox
-rw-rw. 1 vdsm kvm 512 Aug 29 11:50 leases
-rw-r--r--. 1 vdsm kvm 298 Aug 29 11:50 metadata
-rw-rw. 1 vdsm kvm 0 Aug 29 11:50 outbox
/exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/images:
total 0
Then as a test if I create the storage with the NFS version option=v3, I
get an internal ovirt error and a stack.
I followed the wiki and have v3 set on the engine node and
NFS4_SUPPORT="no" set on the machine exporting the share. Mounting the
share and creating/deleting files works fine.
any ideas?
thx
with NFS version option=autonegotiate
==
, sharedLocks= ]
2012-08-29 11:52:10,747 INFO
[org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand]
(ajp--0.0.0.0-8009-1) [595866b1] Running command:
AddStoragePoolWithStoragesCommand internal: true. Entities affected :
ID: 872ed943-cda1-4ec6-a4ea-36b97e7eff5a Type: StoragePool
2012-08-29 11:52:10,790 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] START,
ValidateStorageServerConnectionVDSCommand(vdsId =
1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
----, storageType = NFS, connectionList = [{
id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1, connection:
small.basin.com:/exports/data };]), log id: 721507
2012-08-29 11:52:10,807 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] FINISH,
ValidateStorageServerConnectionVDSCommand, return:
{4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 721507
2012-08-29 11:52:10,808 INFO
[org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] Running command:
ConnectStorageToVdsCommand internal: true. Entities affected : ID:
aaa0----123456789aaa Type: System
2012-08-29 11:52:10,811 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] START, ConnectStorageServerVDSCommand(vdsId =
1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
----, storageType = NFS, connectionList = [{
id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1, connection:
small.basin.com:/exports/data };]), log id: 3b13fdd8
2012-08-29 11:52:11,045 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] FINISH, ConnectStorageServerVDSCommand,
return: {4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 3b13fdd8
2012-08-29 11:52:11,050 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStoragePoolVDSCommand]
(ajp--0.0.0.0-8009-1) [2ec11b86] START,
CreateStoragePoolVDSCommand(vdsId =
1c3207f8-f08d-11e1-8379-438e839e5efb,
storagePoolId=872ed943-cda1-4ec6-a4ea-36b97e7eff5a, storageType=NFS,
storagePoolName=basindatacenter,
masterDomainId=8f1e9376-8303-4660-948f-a6704b041e2e,
domainsIdList=[8f1e9376-8303-4660-948f-a6704b041e2e], masterVersion=10),
log id: 52930390
2012-08-29 11:53:15,434 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--0.0.0.0-8009-1) [2ec11b86] Failed in CreateStoragePoolVDS method
2012-08-29 11:53:15,436 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--0.0.0.0-8009-1) [2ec11b86] Error code StorageDomainDoesNotExist
and error message VDSGenericException: VDSErrorException: Failed to
CreateStoragePoolVDS, error = Storage domain does not exist:
('8f1e9376-8303-4660-948f-a6704b041e2e',)
2012-08-29 11:53:15,438 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(ajp--0.0.0.0-8009-1) [2ec11b86] Command
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStoragePoolVDSCommand
return value
Class Name:
org.ovirt.engine.core.vdsbroker.vdsbroker.StatusOnlyReturnForXmlRpc
mStatus Class Name:
org.ovirt.engine.core.vdsbroker.vdsbroker.StatusForXmlRpc
mCode 358
mMessage Storage domain does not exist:
('8f1e9376-8303-4660-948f-a6704b041e2e',)
with NFS version option=v3
=
Re: [Users] Storage domain does not exist
Premature CTRL+ENTER, sorry about that.
>From the log:
Command
org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand
throw exception: java.lang.RuntimeException: Could not get JDBC
Connection; nested exception is java.sql.SQLException:
javax.resource.ResourceException: IJ000460: Error checking for a
transaction
Can you verify your DB is up and running in a proper fashion?
- Original Message -
> From: "Allon Mureinik"
> To: "Jon Thomas"
> Cc: users@ovirt.org
> Sent: Thursday, August 30, 2012 8:55:06 AM
> Subject: Re: [Users] Storage domain does not exist
>
> Hi Jon,
>
> This seems like a postgres database issue:
>
>
> - Original Message -
> > From: "Jon Thomas"
> > To: users@ovirt.org
> > Sent: Wednesday, August 29, 2012 7:08:45 PM
> > Subject: [Users] Storage domain does not exist
> >
> > Hi,
> >
> > I'm doing a fresh 3.1 install. I'm having a problem attaching newly
> > created storage. I followed
> > http://wiki.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues.
> >
> >
> > I seem to be able to create the storage ok. If I create it with the
> > default NFS version option=autonegotiate, I get a 500 error and
> > "storage
> > does not exist" in the logs when trying to attach it. I can verify
> > that
> > subdirectories and files were created.
> >
> >
> > #ls -l /exports/data/*/*
> > /exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/dom_md:
> > total 8
> > -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 ids
> > -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 inbox
> > -rw-rw. 1 vdsm kvm 512 Aug 29 11:50 leases
> > -rw-r--r--. 1 vdsm kvm 298 Aug 29 11:50 metadata
> > -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 outbox
> >
> > /exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/images:
> > total 0
> >
> > Then as a test if I create the storage with the NFS version
> > option=v3, I
> > get an internal ovirt error and a stack.
> >
> > I followed the wiki and have v3 set on the engine node and
> > NFS4_SUPPORT="no" set on the machine exporting the share. Mounting
> > the
> > share and creating/deleting files works fine.
> >
> > any ideas?
> >
> > thx
> >
> >
> > with NFS version option=autonegotiate
> > ==
> > , sharedLocks= ]
> > 2012-08-29 11:52:10,747 INFO
> > [org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand]
> > (ajp--0.0.0.0-8009-1) [595866b1] Running command:
> > AddStoragePoolWithStoragesCommand internal: true. Entities affected
> > :
> > ID: 872ed943-cda1-4ec6-a4ea-36b97e7eff5a Type: StoragePool
> > 2012-08-29 11:52:10,790 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
> > (ajp--0.0.0.0-8009-1) [2ec11b86] START,
> > ValidateStorageServerConnectionVDSCommand(vdsId =
> > 1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
> > ----, storageType = NFS,
> > connectionList = [{ id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1,
> > connection: small.basin.com:/exports/data };]), log id: 721507
> > 2012-08-29 11:52:10,807 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand]
> > (ajp--0.0.0.0-8009-1) [2ec11b86] FINISH,
> > ValidateStorageServerConnectionVDSCommand, return:
> > {4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 721507
> > 2012-08-29 11:52:10,808 INFO
> > [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand]
> > (ajp--0.0.0.0-8009-1) [2ec11b86] Running command:
> > ConnectStorageToVdsCommand internal: true. Entities affected : ID:
> > aaa0----123456789aaa Type: System
> > 2012-08-29 11:52:10,811 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
> > (ajp--0.0.0.0-8009-1) [2ec11b86] START,
> > ConnectStorageServerVDSCommand(vdsId =
> > 1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId =
> > ----, storageType = NFS,
> > connectionList = [{ id: 4b9fdb5c-d334-4056-a5fb-6946214e9ba1,
> > connection: small.basin.com:/exports/data };]), log id: 3b13fdd8
> > 2012-08-29 11:52:11,045 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
> > (ajp--0.0.0.0-8009-1) [2ec11b86] FINISH,
> > ConnectStorageServerVDSCommand, return:
> > {4b9fdb5c-d334-4056-a5fb-6946214e9ba1=0}, log id: 3b13fdd8
> > 2012-08-29 11:52:11,050 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.
Re: [Users] Storage domain does not exist
Hi, Thanks to those who replied. I managed to get this working. What I have is three machines: #1- 8G/4core 3.4.4-5.fc17.x86_64 machine with engine also serving the isodomain #2- 4G/4core 3.3.4-5.fc17.x86_64 node that is also serving nfs for the data share that I was trying to attach #3- 48GB/12core node with the oVirt f17 node image It worked by removing #3 and then attaching the storage. I only tried the autonegotiate option. So it seems it was the 3.5 kernel on #3 that was the problem. I've since reinstalled #3 with 3.3.4-5.fc17.x86_64 and the storage has stayed attached/active. I've since created a vm. I have a couple other things to investigate. For some reason #3 rejected the vm and installing the vm on #2 was really slow (rhel5 and ~4 hrs). Is there a storage best practice? Would one want to use a node to serve an nfs data share and also run a VM? I'm thinking not as the behavior of the install iterated between normal and then hanging for some amount of time as if it were blocking. I also saw some "D" state nfsd threads so there was something going on with nfs. thanks On Thu, 2012-08-30 at 01:56 -0400, Allon Mureinik wrote: > Premature CTRL+ENTER, sorry about that. > > From the log: > Command > org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand > throw exception: java.lang.RuntimeException: Could not get JDBC > Connection; nested exception is java.sql.SQLException: > javax.resource.ResourceException: IJ000460: Error checking for a > transaction > > Can you verify your DB is up and running in a proper fashion? > > - Original Message - > > From: "Allon Mureinik" > > To: "Jon Thomas" > > Cc: users@ovirt.org > > Sent: Thursday, August 30, 2012 8:55:06 AM > > Subject: Re: [Users] Storage domain does not exist > > > > Hi Jon, > > > > This seems like a postgres database issue: > > > > > > - Original Message - > > > From: "Jon Thomas" > > > To: users@ovirt.org > > > Sent: Wednesday, August 29, 2012 7:08:45 PM > > > Subject: [Users] Storage domain does not exist > > > > > > Hi, > > > > > > I'm doing a fresh 3.1 install. I'm having a problem attaching newly > > > created storage. I followed > > > http://wiki.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues. > > > > > > > > > I seem to be able to create the storage ok. If I create it with the > > > default NFS version option=autonegotiate, I get a 500 error and > > > "storage > > > does not exist" in the logs when trying to attach it. I can verify > > > that > > > subdirectories and files were created. > > > > > > > > > #ls -l /exports/data/*/* > > > /exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/dom_md: > > > total 8 > > > -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 ids > > > -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 inbox > > > -rw-rw. 1 vdsm kvm 512 Aug 29 11:50 leases > > > -rw-r--r--. 1 vdsm kvm 298 Aug 29 11:50 metadata > > > -rw-rw. 1 vdsm kvm 0 Aug 29 11:50 outbox > > > > > > /exports/data/8f1e9376-8303-4660-948f-a6704b041e2e/images: > > > total 0 > > > > > > Then as a test if I create the storage with the NFS version > > > option=v3, I > > > get an internal ovirt error and a stack. > > > > > > I followed the wiki and have v3 set on the engine node and > > > NFS4_SUPPORT="no" set on the machine exporting the share. Mounting > > > the > > > share and creating/deleting files works fine. > > > > > > any ideas? > > > > > > thx > > > > > > > > > with NFS version option=autonegotiate > > > == > > > , sharedLocks= ] > > > 2012-08-29 11:52:10,747 INFO > > > [org.ovirt.engine.core.bll.storage.AddStoragePoolWithStoragesCommand] > > > (ajp--0.0.0.0-8009-1) [595866b1] Running command: > > > AddStoragePoolWithStoragesCommand internal: true. Entities affected > > > : > > > ID: 872ed943-cda1-4ec6-a4ea-36b97e7eff5a Type: StoragePool > > > 2012-08-29 11:52:10,790 INFO > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand] > > > (ajp--0.0.0.0-8009-1) [2ec11b86] START, > > > ValidateStorageServerConnectionVDSCommand(vdsId = > > > 1c3207f8-f08d-11e1-8379-438e839e5efb, storagePoolId = > > > ----, storageType = NFS, > >
Re: [Users] Storage domain does not exist
> > I've since created a vm. I have a couple other things to investigate. > For some reason #3 rejected the vm and installing the vm on #2 was > really slow (rhel5 and ~4 hrs). First was "failed to open socket to sanlock daemon" and I set selinux to permissive to get around it. The slowness was improved with async. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Storage domain does not exist
Hey,
I am having an issue moving/copying vm's and templates around in my ovirt
environment. I am getting the following error in my VDSM Logs:
"2017-06-01 01:01:54,425-0500 ERROR (jsonrpc/5) [storage.Dispatcher]
{'status': {'message': "Storage domain does not exist:
(u'97258ca6-5acd-40c7-a812-b8cac02a9621',)", 'code': 358}} (dispatcher:77)"
I believe this started when i destroyed a data domain instead of removing
the domain correctly. I have since then rebuilt my ovirt environment,
importing my gluster domains back into my new setup.
I believe the issue is related to some stale metadata on my gluster storage
servers somewhere but do not know how to remove it or where it exists.
I found these two posts that seem to deal with the same problem i am seeing.
https://access.redhat.com/solutions/180623
and
https://access.redhat.com/solutions/2355061
Currently running 2 dedicated gluster servers and 2 Ovirt VM hosts servers,
one is acting as an arbiter for my replica 3 gluster file system.
All hosts are running CentOS Linux release 7.3.1611 (Core)
Thanks___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[Users] Storage domain does not exist & Error 477
Hi, I'm seeing the errors mentioned in the subject line with my new oVirt installation. I've tried to remove the metadata's checksum line and re-activate, to no avail. For background, please see: http://pastebin.com/raw.php?i=R2SH5ah8 I'm unable to detach and activate my ISO domain. Please advise. Thanks, Joshua -- Joshua Dotson Founder, Wrale Ltd ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Storage domain does not exist (SOLVED)
Thanks!
It did all the magic!
Regards //Ricky
On 2012-08-14 14:50, Maor Lipchuk wrote:
> Ricky, Try do the following :
>
> go to the meta data of the data storage (in the storage server
> go to {storage_domain_name}/##/dom_md/metadata)
> delete the chksum line _SHA_CKSUM=
> try to activate the storage domain again the DC (it should fail again)
> vdsm.log should print the computed cksum of the storage domain (Should
> be an error there which say "Meta Data seal is broken (checksum
> mismatch) computed_cksum = ")
> copy the comuted chksum to the meta data (_SHA_CKSUM={new chksum number}
> try to activate it again.
>
> Hope it will fix that.
>
> Mean while I'm checking what caused the bug.
>
> Regards,
> Maor
>
> On 08/14/2012 02:53 PM, Ricky Schneberger wrote:
>> Hi
>>
>> I attached the logs.
>>
>> //Ricky
>>
>> On 2012-08-14 12:56, Maor Lipchuk wrote:
>>> Hi Ricky can you please add the log of VDSM, also the full engine log.
>>>
>>> Regards,
>>> Maor
>>>
>>>
>>> On 08/14/2012 01:22 PM, Ricky Schneberger wrote:
After an normal "yum update" i am unable to get one of the storage
domains "UP".
My systems is running Centos 6.3.
If I try to activate the domain in GUI I got following errors:
-
2012-08-14 12:16:22,594 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Lock Acquired to object EngineLock
[exclusiveLocks= key:
org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
5de36f78-8303-401b-b6c3-e04091077f9e
2012-08-14 12:16:22,610 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Running command:
ActivateStorageDomainCommand internal: false. Entities affected : ID:
5de36f78-8303-401b-b6c3-e04091077f9e Type: Storage
2012-08-14 12:16:22,618 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Lock freed to object EngineLock
[exclusiveLocks= key:
org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand value:
5de36f78-8303-401b-b6c3-e04091077f9e
2012-08-14 12:16:22,709 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.ActivateStorageDomainVDSCommand]
(pool-5-thread-50) [539cbd7e] START,
ActivateStorageDomainVDSCommand(storagePoolId =
64a0f560-b9a1-4c87-8a30-0967b4ce3c81, ignoreFailoverLimit = false,
compatabilityVersion = null, storageDomainId =
5de36f78-8303-401b-b6c3-e04091077f9e), log id: 152cc8c3
2012-08-14 12:16:25,050 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase]
(pool-5-thread-50) [539cbd7e] Error code StorageDomainDoesNotExist and
error message IRSGenericException: IRSErrorException: Failed to
ActivateStorageDomainVDS, error = Storage domain does not exist:
('5de36f78-8303-401b-b6c3-e04091077f9e',)
2012-08-14 12:16:25,050 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(pool-5-thread-50) [539cbd7e]
IrsBroker::Failed::ActivateStorageDomainVDS due to: IRSErrorException:
IRSGenericException: IRSErrorException: Failed to
ActivateStorageDomainVDS, error = Storage domain does not exist:
('5de36f78-8303-401b-b6c3-e04091077f9e',)
2012-08-14 12:16:25,058 ERROR
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Command
org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand throw Vdc
Bll exception. With error message VdcBLLException:
org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException:
IRSGenericException: IRSErrorException: Failed to
ActivateStorageDomainVDS, error = Storage domain does not exist:
('5de36f78-8303-401b-b6c3-e04091077f9e',)
2012-08-14 12:16:25,074 INFO
[org.ovirt.engine.core.bll.storage.ActivateStorageDomainCommand]
(pool-5-thread-50) [539cbd7e] Command
[id=6db5eb90-af14-43f7-8494-d59528a77c27]: Compensating
CHANGED_STATUS_ONLY of
org.ovirt.engine.core.common.businessentities.storage_pool_iso_map;
snapshot: EntityStatusSnapshot [id=storagePoolId =
64a0f560-b9a1-4c87-8a30-0967b4ce3c81, storageId =
5de36f78-8303-401b-b6c3-e04091077f9e, status=InActive].
-
Ho can I try to resolv it?
Regards //Ricky
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>
0xB88C0B63.asc
Description: application/pgp-keys
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Storage domain does not exist
It seems related to the destroy of the storage domain since destroy
will still remove it from the engine if there is a problem.
Have you tried to restart VDSM, or reboot the Host?
There could be a problem with umount the storage domain.
Can you please send the VDSM logs
Regards,
Maor
On Thu, Jun 1, 2017 at 2:19 PM, Bryan Sockel wrote:
> Hey,
>
> I am having an issue moving/copying vm's and templates around in my ovirt
> environment. I am getting the following error in my VDSM Logs:
>
> "2017-06-01 01:01:54,425-0500 ERROR (jsonrpc/5) [storage.Dispatcher]
> {'status': {'message': "Storage domain does not exist:
> (u'97258ca6-5acd-40c7-a812-b8cac02a9621',)", 'code': 358}} (dispatcher:77)"
>
> I believe this started when i destroyed a data domain instead of removing
> the domain correctly. I have since then rebuilt my ovirt environment,
> importing my gluster domains back into my new setup.
>
> I believe the issue is related to some stale metadata on my gluster storage
> servers somewhere but do not know how to remove it or where it exists.
>
> I found these two posts that seem to deal with the same problem i am seeing.
>
> https://access.redhat.com/solutions/180623
> and
> https://access.redhat.com/solutions/2355061
>
> Currently running 2 dedicated gluster servers and 2 Ovirt VM hosts servers,
> one is acting as an arbiter for my replica 3 gluster file system.
>
> All hosts are running CentOS Linux release 7.3.1611 (Core)
>
> Thanks
>
> ___
> 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
