Thanks Dan! On Thu, Feb 22, 2018 at 7:15 PM, Dan Kenigsberg <danken@redhat.com> wrote:

On Thu, Feb 22, 2018 at 12:59 PM, Dafna Ron <dron@redhat.com> wrote:

...

Hi,

We had two failed tests reported in vdsm project last evening the patch reported seems to be related to the issue.

Link and headline of suspected patches:

momIF: change the way we connect to MOM - https://gerrit.ovirt.org/#/c/87944/

Link to Job:

http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5823/

Link to all logs:

http://jenkins.ovirt.org/job/ovirt-master_change-queue- tester/5823/artifacts

(Relevant) error snippet from the log:

<error>

2018-02-21 14:15:47,576-0500 INFO (MainThread) [vdsm.api] FINISH prepareForShutdown return=None from=internal, task_id=7d37a33b-0215-40c0-a821-9b94707caca6 (api:52) 2018-02-21 14:15:47,576-0500 ERROR (MainThread) [vds] Exception raised (vdsmd:158) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 156, in run serve_clients(log) File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 103, in serve_clients cif = clientIF.getInstance(irs, log, scheduler) File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 251, in getInstance cls._instance = clientIF(irs, log, scheduler) File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 121, in __init__ self.mom = MomClient(config.get("mom", "socket_path")) File "/usr/lib/python2.7/site-packages/vdsm/momIF.py", line 51, in __init__ raise MomNotAvailableError() MomNotAvailableError

</error>

this smells like a race between mom and vdsm startups (that bidirectional dependency is woderful!). I am sure that Francesco can fix it quickly, but until then I've posted a revert of the offending patch http://jenkins.ovirt.org/job/ovirt-system-tests_manual/2225/