Actions
action #32065
closedVNC was redirected to a different job
Start date:
2018-02-21
Due date:
% Done:
0%
Estimated time:
Description
Up until https://openqa.suse.de/tests/1487054#step/scc_registration/3 the job is doing what is supposed to do but then the VNC connection seems to get output from a different VM: https://openqa.suse.de/tests/1487054#step/scc_registration/4. We should not ever see bootloader on Xen PV (as seen on the latter screen, it must be from some other place).
Updated by coolo about 6 years ago
we relogin to the VNC in between:
[2018-02-20T21:45:08.0064 CET] [debug] waiting for screen change: 0 1000000
[2018-02-20T21:45:08.0568 CET] [debug] waiting for screen change: 0 1000000
[2018-02-20T21:45:09.0071 CET] [debug] waiting for screen change: 1 1000000
[2018-02-20T21:45:09.0306 CET] [debug] considering VNC stalled, no update for 4.01 seconds
[2018-02-20T21:45:09.0556 CET] [debug] pointer type 0 0 720 400 -257
Looks like the VNC settings are inconsistent for xen.
Updated by coolo almost 6 years ago
- Category set to Regressions/Crashes
- Target version set to Ready
Updated by okurz over 4 years ago
- Status changed from New to Rejected
- Assignee set to okurz
I don't think we have enough information in this ticket to be able to fix it. @coolo please reopen if you think differently. I have never seen this myself when reviewing xen job results.
Actions