action #37057
closed
[sle][functional][medium][s390x][fast][u] test fails in gpg - operation cancelled
Added by jorauch almost 6 years ago.
Updated almost 6 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 17
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-s390x-extra_tests_in_textmode@s390x-kvm-sle12 fails in
gpg
Looks like the SUT got a signal to cancel or gpg is broken on s390x
This needs to be investigated further and be acted on accordingly
Reproducible¶
Fails since (at least) Build 0254 (current job)
Expected result¶
x86 as reference:
https://openqa.suse.de/tests/1754808#step/gpg/7
Further details¶
Always latest result in this scenario: latest
- Description updated (diff)
- Priority changed from Normal to High
- Target version set to Milestone 17
so when I try to manually reproduce this, I get a window rendered where i should enter the passphrase.
If not providing something, this times out and I get the same error message
gpg-agent[2370]: command get_passphrase failed: Operation cancelled
gpg: cancelled by user
gpg: Key generation canceled.
So either this window gets rendered somewhere or not at all
- Status changed from New to In Progress
- Assignee set to jorauch
further investigation going on
Suggestions:
run with '-v' and maybe with '-o gpg.log' to get more logging data
Also the passphrase window crashes when being 'ignored' for too long
Looks like we are in a root console that is 'su'ed to user bernhard and therefore we have problems with the environment
http://pastebin.suse.de/21299
This can be reproduced manually
mgriessmeier mentioned that riafarov knows about this
riafarov: pass '-p' to su (might not apply here)
- Status changed from In Progress to Feedback
PR merged, waiting over the weekend if stuff breaks
- Status changed from Feedback to In Progress
okurz suggested to check for that specific error (most likely via needle) should be done by today
jorauch wrote:
okurz suggested to check for that specific error (most likely via needle) should be done by today
+1
merged, I suggest to retrigger a job on osd to have the verification run as well as provide more details in the corresponding bug report.
- Target version changed from Milestone 17 to Milestone 17
- Status changed from In Progress to Blocked
- Due date changed from 2018-06-19 to 2018-07-03
- Due date changed from 2018-07-03 to 2018-07-17
- Status changed from Blocked to Resolved
I don't this is blocked. @jorauch as you stated correctly in #37057#note-18 I think this issue is resolved, no need to further shift around.
Also available in: Atom
PDF