[ https://ovirt-jira.atlassian.net/browse/OVIRT-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38222#comment-38222 ] Greg Sheremeta commented on OVIRT-2538: --------------------------------------- view-source:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10601/artifac... right click view source on that raise exception_class(message, screen, stacktrace) 'Message: timeout\n (Session info: chrome=64.0.3282.140)\n (Driver info: chromedriver=2.35.528139 (47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 3.10.0-862.3.2.el7.x86_64 x86_64)\n\n-------------------- >> begin captured stdout << ---------------------\n _init_browser, connecting to hub at http://172.18.0.2:4444/wd/hub setting window size navigating to engine at https://192.168.201.4/ovirt-engine/webadmin --------------------- and then it times out. Seems like the browser isn't starting. The containers are up and did respond to wget's. Very odd.

ovirt-engine master failure on test 008_basic_ui_sanity.initialize_chrome ---------------------------------------------------------------------------

Key: OVIRT-2538 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2538 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: High Labels: ost_failures, ost_race

I have seen random failures of test 008_basic_ui_sanity.initialize_chrome which are not related to the changes. Here is the latest failure which I confirmed with didi is not a real failure and is not related to the change https://gerrit.ovirt.org/#/c/89572/ https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10601/ I cannot see anything in the http logs and in engine logs. I can see a warn on ssl and some issues which seems to be resolved later on domain names: '[Mon Oct 15 02:56:26.041204 2018] [ssl:warn] [pid 18661] AH01909: RSA certificate configured for 192.168.201.4:443 does NOT include an ID which matches the server name' I think the issue is the test since the only errors I can see are in the lago logs. I saved logs to allow debugging of the test failure. [~gbenhaim@redhat.com] [~gshereme@redhat.com] Can you please check this issue?

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)