Project

General

Profile

Actions
Copy link

action #49409

closed

[functional][y] test fails in yast2_firewall

Added by dimstar about 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
riafarov
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-03-18
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in
yast2_firewall

Test suite description

Maintainer: zluo, riafarov

Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.

Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104).

Reproducible

Fails since (at least) Build 20190315

Expected result

Last good: 20190313 (or more recent)

Further details

Always latest result in this scenario: latest

In the last couple runs, the yast2_gui test did not perform the right tests (scheduling errors) so it is not exactly clear when this broke - and what change in the product might cause it. This ticket shall serve to pintpoint the issue and if needed, file a relevant product bug.

Actions
Copy link
 #1

Updated by riafarov about 5 years ago

  • Subject changed from test fails in yast2_firewall to [functional][y] test fails in yast2_firewall
  • Status changed from New to Rejected
  • Assignee set to riafarov

It's same as before: https://bugzilla.suse.com/show_bug.cgi?id=1114673 , which is fixed now, so should get resolved.

Actions
Copy link
 #2

Updated by dimstar about 5 years ago

Considering that bug was fixed 2 weeks ago - and the thing still failing: how do you come to the conclusion that it must be the same? If so, I'd say you should at leats have reopened the bug

in fact, we had yast2-firewall 4.1.10 since January in Tumbleweed:

r74 | dimstar_suse | 2019-01-24 13:01:21 | 02d444d1ffb44348c432b9f0cfd394a0 | 4.1.10 | rq668113

Actions
Copy link
 #3

Updated by riafarov about 5 years ago

dimstar wrote:

Considering that bug was fixed 2 weeks ago - and the thing still failing: how do you come to the conclusion that it must be the same? If so, I'd say you should at leats have reopened the bug

in fact, we had yast2-firewall 4.1.10 since January in Tumbleweed:

r74 | dimstar_suse | 2019-01-24 13:01:21 | 02d444d1ffb44348c432b9f0cfd394a0 | 4.1.10 | rq668113
firewall-cmd --list-interfaces --zone=public | grep ens4 fails and https://openqa.opensuse.org/tests/881879#step/yast2_firewall/53 shows us that ens4 is assigned to the public zone.

Bug is in state resolved fixed and not verified fixed. I would expect that you know about submissions better, I don't reopen bugs just because test continues to fail as sometimes SRs do not reach distribution for weeks. In this case I believe it makes sense to reopen.

Actions
Copy link

Also available in: Atom PDF