On Sun, May 14, 2017 at 5:14 PM Shlomo Ben David <sbendavi@redhat.com> wrote:
Link to suspected patches: N/A Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6665/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6665/artifa...
Error snippet from the log:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 878,
in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2132, in getAllTasksStatuses allTasksStatus = self._pool.getAllTasksStatuses() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state
This means that getAllTasksStatuses (SPM verb) was called on a host which is not the SPM. This is an error in the caller, not in vdsm. We already have a bug abut this: https://bugzilla.redhat.com/1426429 However this build logs do not contain enough info. These patches adds more info that can help to identify the caller: https://gerrit.ovirt.org/76771 This error is not related to the real error in this build. Nir