Created attachment 597584 [details] engine.log * Create a POSIX domain (vfs type=glusterfs). * Backend sends validateStorageServerConnection with the correct vfs_type, then sends connectStorageServer with the wrong vfs_type (posixfs, which doesn't exist). This causes all new glusterfs domain creation to fail. Thread-378110::INFO::2012-07-06 09:07:50,107::logUtils::37::dispatcher::(wrapper) Run and protect: validateStorageServerConnection(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'port': '', 'connection': '10.35.97.44:/rep1', 'iqn': '', 'portal': '', 'user': '', 'vfs_type': 'glusterfs', 'password': '******', 'id': '00000000-0000-0000-0000-000000000000'}], options=None) [...] Thread-378111::INFO::2012-07-06 09:07:50,160::logUtils::37::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'port': '', 'connection': '10.35.97.44:/rep1', 'iqn': '', 'portal': '', 'user': '', 'vfs_type': 'posixfs', 'password': '******', 'id': '38b65427-1bfe-4069-9503-f9f6b10a7d6d'}], options=None)
laszlo - another duplicate of the posixfs/glusterfs issue in vdsm?
afaik 'posixfs' is accepted by vdsm (and used as a synonim of sharedfs), but then it is returned as 'sharedfs' at the moment, this is when things go wrong. It could be a duplicate.
i misread the bug - this isn't about a wrong type of storage domain, rather a wrong type of the vds_type sent inside (sending storage domain type instead of vfs_type somewhere)
Does not reproduce, I try to find the spcific commit number but still no luck Thread-7414::INFO::2012-08-02 21:26:42,480::logUtils::37::dispatcher::(wrapper) Run and protect: validateStorageServerConnection(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'port': '', 'con nection': '10.35.97.44:/vol2', 'mnt_options': '/tmp/tmp1', 'portal': '', 'user': '', 'iqn': '', 'vfs_type': 'glusterfs', 'password': '******', 'id': '00000000-0000-0000-0000-000000000000'}], options=None) Thread-7414::INFO::2012-08-02 21:26:42,480::logUtils::39::dispatcher::(wrapper) Run and protect: validateStorageServerConnection, Return response: {'statuslist': [{'status': 0, 'id': '00000000-0000-0000-0000-00000 0000000'}]} ...... Thread-7422::INFO::2012-08-02 21:26:56,199::logUtils::37::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=6, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'port': '', 'connection': ' 10.35.97.44:/vol2', 'iqn': '', 'portal': '', 'user': '', 'vfs_type': 'glusterfs', 'password': '******', 'id': 'a84deb23-6ec9-4cb1-b7cd-5cad37d435dc'}], options=None)
latest verify was from commit hash d5227631e4231eb21186ff22172e67d2d68c8060
This functionality is now even more broken (as seen in bug #845831). Unable to verify until this bug is fixed.
Checked on si13.1.