action #30409
closed[tools] send_key fails to send 'home' to an s390x zkvm SUT
0%
Updated by coolo over 6 years ago
- Subject changed from [tools] send_key fails to send 'home' to an s390x zkvm SUT to send_key fails to send 'home' to an s390x zkvm SUT
What makes you sure the home is not sent? I see a product not behaving as your test expects.
Updated by SLindoMansilla over 6 years ago
Because when I start the remote ssh installation manually and I get to this step, the home key works properly.
After szarate's feedback, I will start a vnc remote installation using xvnc manually to prove if xvnc is the cause or os-autoinst.
Updated by SLindoMansilla about 6 years ago
- Subject changed from send_key fails to send 'home' to an s390x zkvm SUT to [tools] send_key fails to send 'home' to an s390x zkvm SUT
Steps done
- Manually started Xvnc in loewe in display :182.
- Started an xterm on display :182
- Connected through ssh to the zkvm-SUT.
- Started remote ssh installation (yast.ssh)
- Verified that the key 'home' works in the product as expected.
So I assume that the problem is on the os-autoinst backend.
Updated by okurz over 4 years ago
- Status changed from New to Rejected
- Assignee set to okurz
@SLindoMansilla as the only reference is a test job on your personal instance and the job is already gone it is hard to reproduce. To me it seems like it is a product behaviour specific issue depending on timing. This is also most likely why you could not reproduce it manually, because you are way slower than openQA is. Please reopen if you have more information, see this happening in production, have a way to reproduce, etc. Thanks.