[Users] Unable to add storage

While Importing storage domain, I see the error message - Error: A Request to the Server failed with the following Status Code: 500 I don't see any error in engine.log - 2012-08-09 17:50:00,018 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-50) Checking autorecoverable storage domains done 2012-08-09 17:53:50,502 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand] (ajp--0.0.0.0-8009-1) [2a6492da] START, ValidateStorageServerConnectionVDSCommand(vdsId = 07b72d80-e1e2-11e1-8351-00fffe0000eb, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = NFS, connectionList = [{ id: null, connection: 192.168.68.209:/iso-cluster3 };]), log id: 1cfa03b5 2012-08-09 17:53:50,545 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ValidateStorageServerConnectionVDSCommand] (ajp--0.0.0.0-8009-1) [2a6492da] FINISH, ValidateStorageServerConnectionVDSCommand, return: {00000000-0000-0000-0000-000000000000=0}, log id: 1cfa03b5 2012-08-09 17:53:50,562 INFO [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand] (ajp--0.0.0.0-8009-1) [2a6492da] Running command: ConnectStorageToVdsCommand internal: false. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: System 2012-08-09 17:53:50,565 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (ajp--0.0.0.0-8009-1) [2a6492da] START, ConnectStorageServerVDSCommand(vdsId = 07b72d80-e1e2-11e1-8351-00fffe0000eb, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = NFS, connectionList = [{ id: null, connection: 192.168.68.209:/iso-cluster3 };]), log id: 648b117 2012-08-09 17:53:50,708 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (ajp--0.0.0.0-8009-1) [2a6492da] FINISH, ConnectStorageServerVDSCommand, return: {00000000-0000-0000-0000-000000000000=0}, log id: 648b117 2012-08-09 17:53:50,878 INFO [org.ovirt.engine.core.bll.storage.GetExistingStorageDomainListQuery] (ajp--0.0.0.0-8009-11) START, GetExistingStorageDomainListQuery(org.ovirt.engine.core.common.queries.GetExistingStorageDomainListParameters@5fc57c29), log id: 739b67f2 2012-08-09 17:53:50,886 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand] (ajp--0.0.0.0-8009-11) START, HSMGetStorageDomainsListVDSCommand(vdsId = 07b72d80-e1e2-11e1-8351-00fffe0000eb, storagePoolId=00000000-0000-0000-0000-000000000000, storageType=NFS, storageDomainType=ISO, path=192.168.68.209:/iso-cluster3), log id: 28e978af 2012-08-09 17:55:00,002 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-10) Checking autorecoverable hosts 2012-08-09 17:55:00,009 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-10) Autorecovering 0 hosts 2012-08-09 17:55:00,009 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-10) Checking autorecoverable hosts done 2012-08-09 17:55:00,010 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-10) Checking autorecoverable storage domains 2012-08-09 17:55:00,011 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-10) Autorecovering 0 storage domains 2012-08-09 17:55:00,012 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-10) Checking autorecoverable storage domains done 2012-08-09 17:55:55,995 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainsListVDSCommand] (ajp--0.0.0.0-8009-11) FINISH, HSMGetStorageDomainsListVDSCommand, return: [], log id: 28e978af 2012-08-09 17:55:55,997 INFO [org.ovirt.engine.core.bll.storage.GetExistingStorageDomainListQuery] (ajp--0.0.0.0-8009-11) FINISH, GetExistingStorageDomainListQuery, log id: 739b67f2 2012-08-09 18:00:00,004 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (QuartzScheduler_Worker-80) Checking autorecoverable hosts I am running ovirt-engine-3.1.0-2.fc17. -Sharad Mishra

On 10/08/2012, at 9:38 AM, snmishra@linux.vnet.ibm.com wrote: <snip>
I am running ovirt-engine-3.1.0-2.fc17.
Hi Sharad, Yeah, this is a known problem (recent). Seems to be caused by kernel-3.5.0 series. If you're able to drop back to an earlier kernel, for example the 3.4.6 one prior to it, then NFS mounts will work. Hope that helps. :) Regards and best wishes, Justin Clift
-Sharad Mishra
-- Aeolus Community Manager http://www.aeolusproject.org
participants (2)
-
Justin Clift
-
snmishraï¼ linux.vnet.ibm.com