action #37057
closed[sle][functional][medium][s390x][fast][u] test fails in gpg - operation cancelled
0%
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
Updated by okurz almost 6 years ago
- Priority changed from Normal to High
- Target version set to Milestone 17
Updated by mgriessmeier almost 6 years ago
hmm, first I thought that it might be the same Bug as in SLE 15 -> https://openqa.suse.de/tests/1749585#step/gpg/6 (https://bugzilla.suse.com/show_bug.cgi?id=1073704)
but looks different, so this needs more investigation for sure ;)
Updated by mgriessmeier almost 6 years ago
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
Updated by jorauch almost 6 years ago
- Status changed from New to In Progress
- Assignee set to jorauch
further investigation going on
Updated by jorauch almost 6 years ago
Suggestions:
run with '-v' and maybe with '-o gpg.log' to get more logging data
Updated by jorauch almost 6 years ago
Apparently no gpg-agent is running:
http://pinky.arch.suse.de/tests/1257#step/gpg/6
Updated by jorauch almost 6 years ago
Also the passphrase window crashes when being 'ignored' for too long
Updated by jorauch almost 6 years ago
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)
Updated by jorauch almost 6 years ago
Created:
https://bugzilla.suse.com/show_bug.cgi?id=1097610
Will implement a workaround for s390x now
Updated by jorauch almost 6 years ago
- Status changed from In Progress to Feedback
PR with workaround
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5223
Updated by jorauch almost 6 years ago
PR merged, waiting over the weekend if stuff breaks
Updated by jorauch almost 6 years ago
- Status changed from Feedback to In Progress
okurz suggested to check for that specific error (most likely via needle) should be done by today
Updated by mgriessmeier almost 6 years ago
jorauch wrote:
okurz suggested to check for that specific error (most likely via needle) should be done by today
+1
Updated by jorauch almost 6 years ago
Updated by okurz almost 6 years ago
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.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by jorauch almost 6 years ago
- Status changed from In Progress to Blocked
Went fine and as expected on s390x after merge:
https://openqa.suse.de/tests/1762719
Still working on x86:
https://openqa.suse.de/tests/1762899
Consider this as resolved until we hear something new from the bug: https://bugzilla.suse.com/show_bug.cgi?id=1097610
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-06-19 to 2018-07-03
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-07-03 to 2018-07-17
Updated by okurz almost 6 years ago
- 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.