QA (public) » openQA Project (public)

Just for the record, I don't see the problem locally or on osd, only on o3.
Can't see anything suspicious in the developer tools console / network log.

I cannot reproduce the problem Tina and me saw on o3 with any running job on o3. Note that this problem was also happening with currently running jobs, e.g. Tina sent me the link and the updates also got stuck when I opened the running job on my machine. Currently o3 isn't busy at all.

The workaround "Open the job result only after the job started" implies that there's another case when it is only broken if the job wasn't running when opening the tab. I could also not reproduce that case. Neither on o3 nor locally. Note that it can take a while until the test actually gets started. So a test still shows up as running when the worker downloads assets, isotovideo is launched, needles are initialized and the test schedule is created. That can take a while. Maybe it was just that and the reload was just done shortly before the test was actually starting so it only looked like it helped?

The workaround "Force a refresh of the browser window with "F5"" implies that refreshing would help. That wasn't really the case on the job Tina and me observed. It helped but shortly the job got stuck again.

I'll check again next week when o3 is more busy. Maybe that makes a difference. Once I find a job I'll investigate the workers pool directory and logs.

I've also found a job where the video was disabled (due to max. job time). In this case one also doesn't get a screen. I suppose that was not the case here. I'm just mentioning it because at a first look such a job looks like it would reproduce some of the mentioned issues.

Anybody, feel free to grab this ticket if you can reproduce it. I've opened a few tabs but so far haven't reproduced it.

I could still reproduce it as of today. Do you think it has something to do with my local environment, e.g. Firefox on Leap 15.3 x86_64 or something?

I don't think it is the Firefox version. Since this is about the image and likely also the log I don't think the relevant code requires any too new JavaScript features your possibly outdated browser doesn't have.

If you can reproduce it locally, you could open the developer tools in the tab and check whether anything shows up in the JavaScript console and network log when the job state switches to running.

Looked into this with mkittler:

1. mkittler and me can reproduce the problem on o3 100%
2. As soon as a second browser instance e.g. a second user opens the job details page of the same job that fixes the refresh for the first user
3. In browser development tools resending the "streaming" request fixes the refresh for the image
4. The problem can also be reproduced by circumventing the apache webproxy on o3 with an ssh bridge ssh -NT -L 9526:localhost:9526 o3

PR which should fix the problem (at least it does when provoking the problem as mentioned before): https://github.com/os-autoinst/openQA/pull/5060

It has been deployed on o3 and works.