Hide Forgot
Created attachment 486804 [details] RHEVM and VDSM22 logs Description of problem: The status of non SPM host is non-responsive after attaching ISCSI Data storage domain to the datacenter Version-Release number of selected component (if applicable): RHEVM version:ic 104 vdsm22 on both hosts:vdsm22-4.5-63.24.el5_6 Steps to Reproduce: 1.Create data center and cluster (type iscsi version 2.2) 2.Add at least two hosts 3.Create ISCSI Data storage domain 4.Attach created storage 5.One host is SPM and another one is non-responsive Expected results: All hosts in status UP and One of them is SPM Additional info: *The same behaviour also with REST API
For how long does the non-SPM host stay non-responsive? Forever? Is this behavior new to rhev-m-2.3? Either way, Thread-12940::ERROR::2011-03-22 15:45:57,547::misc::66::irs::'masterValidate' Thread-12940::ERROR::2011-03-22 15:45:57,548::misc::67::irs::Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 978, in _run return fn(*args, **kargs) File "/usr/share/vdsm/storage/hsm.py", line 1696, in public_repoStats valid = (master_stats['masterValidate']['mount'] and KeyError: 'masterValidate' smells like the outcome of a race between adding a SD and reporting its repoStats.
(In reply to comment #1) > For how long does the non-SPM host stay non-responsive? Forever? > > Is this behavior new to rhev-m-2.3? > > Either way, > > Thread-12940::ERROR::2011-03-22 15:45:57,547::misc::66::irs::'masterValidate' > Thread-12940::ERROR::2011-03-22 15:45:57,548::misc::67::irs::Traceback (most > recent call last): > File "/usr/share/vdsm/storage/task.py", line 978, in _run > return fn(*args, **kargs) > File "/usr/share/vdsm/storage/hsm.py", line 1696, in public_repoStats > valid = (master_stats['masterValidate']['mount'] and > KeyError: 'masterValidate' > > smells like the outcome of a race between adding a SD and reporting its > repoStats. The non-SPM host stay forever on non-responsive state.
It looks like setup issue. I just added several logs and the problem disappeared. Let's try to reproduce it on RHEL6
Created attachment 491439 [details] vdsm log (RHEL6 log)
Reproduced in RHEL6 (log attached)