Project

General

Profile

Actions

action #65283

closed

many screenshots on o3 show no result, no popup, update of URL in address bar only flashes for a second

Added by okurz about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2020-04-03
Due date:
% Done:

0%

Estimated time:

Description

Observation

On multiple jobs many screenshots show no results. There is no popup and the update of the URL in the address bar only flash up for a second. Some other steps still work, e.g. https://openqa.opensuse.org/tests/1222737#step/yast2_samba/80 but one before is not clickable. Clicking on the screenshot corresponding to https://openqa.opensuse.org/tests/1222737#step/yast2_samba/79 trigger an error in the browser web console "Failed to load data from: /tests/1222737/modules/yast2_samba/steps/79 test_result.js:19:175".

The corresponding (minified) javascript code of test_result.js:19:175 (previous line and current):

var link=a.find('a');if(!link||!link.data('url')){return;}
a.addClass('current_preview');setResultHash(link.attr('href'),true);$.get({url:link.data('url'),success:function(data){previewSuccess(data,force);}}).fail(function(){console.warn('Failed to load data from: '+link.data('url'));setCurrentPreview(null);});}

Could be related to #65202 even though that seems to be less severe by now.

Steps to reproduce

See test link above, https://openqa.opensuse.org/tests/1222737#step/yast2_samba/80 , and go to a previous step. The same is reproducible at the time of writing for multiple other jobs.

Suggestions

  • Crosscheck requests in logs on o3

Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #65202: o3 is very slow/unresponsive and runs into timeoutsResolvedmkittler2020-04-02

Actions
Actions #1

Updated by okurz about 4 years ago

  • Related to action #65202: o3 is very slow/unresponsive and runs into timeouts added
Actions #2

Updated by ggardet_arm about 4 years ago

In the web browser console, I get the following error:

bootstrap.js:670 GET https://openqa.opensuse.org/tests/1223277/modules/bootloader_uefi/steps/9 500 (Internal Server Error)

followed by the following warning:

test_result.js:19 Failed to load data from: /tests/1223277/modules/bootloader_uefi/steps/9
Actions #3

Updated by okurz about 4 years ago

  • Priority changed from Normal to Urgent

This problem is still happening, reported by multiple persons. Also reported by @ybonatakis for his own instance in https://chat.suse.de/channel/testing?msg=aWiN4b8AmoWgtPEa9 which sounds like the same problem.

Actions #4

Updated by favogt about 4 years ago

The webui log file shows

[2020-04-06T11:25:59.0604 UTC] [error] [UGG3hkBJ] Undefined subroutine &OpenQA::WebAPI::Controller::Step::find_bug_number called at /usr/share/openqa/script/../lib/OpenQA/WebAPI/Controller/Step.pm line 324

Actions #5

Updated by livdywan about 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to livdywan

favogt wrote:

The webui log file shows

[2020-04-06T11:25:59.0604 UTC] [error] [UGG3hkBJ] Undefined subroutine &OpenQA::WebAPI::Controller::Step::find_bug_number called at /usr/share/openqa/script/../lib/OpenQA/WebAPI/Controller/Step.pm line 324

I was just looking into that same code path. I will try and come up with a gix for that.

Actions #6

Updated by okurz about 4 years ago

https://github.com/os-autoinst/openQA/pull/2906 should be a very simple fix for the obvious problem that "find_bug_number" is not imported. Why this fails now and what else could be missing I did not investigate.

Actions #8

Updated by okurz about 4 years ago

  • Priority changed from Urgent to Normal

with https://github.com/os-autoinst/openQA/pull/2906 merged and properly applied the problem isn't urgent anymore.

Actions #9

Updated by livdywan about 4 years ago

  • Status changed from In Progress to Resolved
  • Target version set to Current Sprint

With https://github.com/os-autoinst/openQA/pull/2909 merged we also have test coverage for this and the issue seems to have been resolved

Actions

Also available in: Atom PDF