Project

General

Profile

Actions
Copy link

action #97229

closed

Create workaround for s390x polkit unexpected popup

Added by syrianidou_sofia over 3 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
Current
Start date:
2021-08-19
Due date:
% Done:

0%

Estimated time:

Description

After reporting bug#1177446 and getting a WONTFIX reply, it makes sense to add a soft failure for the occasions that polkit popup appears unexpectedly, instead of having test failures.

The popup appears after Desktop login:
https://openqa.suse.de/tests/6887955#step/first_boot/8

Actions
Copy link
 #1

Updated by syrianidou_sofia over 3 years ago

  • Project changed from openQA Tests (public) to qe-yam
Actions
Copy link
 #2

Updated by oorlov over 3 years ago

  • Tags set to qe-yast-refinement
  • Target version set to Current
Actions
Copy link
 #3

Updated by JERiveraMoya over 3 years ago

@sofia do we have any recent failure of this problem?

Actions
Copy link
 #4

Updated by syrianidou_sofia over 3 years ago

Yes, openqa is reporting linked failures on the bug. This month it happened twice: See last one https://bugzilla.suse.com/show_bug.cgi?id=1177446#c56

Actions
Copy link
 #5

Updated by openqa_review about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: lvm-encrypt-separate-boot
https://openqa.suse.de/tests/7430231

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions
Copy link
 #6

Updated by openqa_review about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: lvm-encrypt-separate-boot
https://openqa.suse.de/tests/7584510

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions
Copy link
 #7

Updated by JERiveraMoya about 3 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Rejected

This is supposed to be fixed here by desktop team: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13598

Actions
Copy link

Also available in: Atom PDF