action #47318
closed[functional][y][fast] leap 42.3 openssh tests broken since february 7th
0%
Description
openSUSE Leap 42.3 started failing openssh tests on February 7, 17:00
https://openqa.opensuse.org/tests/849933#next_previous
The firewall seems not be started or has been stopped by something.
It might be related to oliver kurz merge regarding
f8e8ccc67fa9fef324e166820f3662e21ef01b69
that was merged on feb 6
Updated by okurz about 5 years ago
- Related to action #44450: [functional][y] Adjust test modules to yast lan changes added
Updated by okurz about 5 years ago
- Subject changed from leap 42.3 openssh tests broken since february 7th to [functional][y][fast leap 42.3 openssh tests broken since february 7th
- Due date set to 2019-02-12
- Category set to Bugs in existing tests
- Status changed from New to Workable
- Assignee set to riafarov
- Target version set to Milestone 22
@msmeissn for easier ticket creation you can use the openQA built-in reporting feature, see https://wiki.microfocus.net/index.php?title=RD-OPS_QA/openQA_review#Workflow_for_SLES.2C_SLED_and_HA_as_an_example for an example with screenshot.
@msmeissn are you sure that nothing changed in the product? I crosschecked the logfiles with the "last good" https://openqa.opensuse.org/tests/848612/file/autoinst-log.txt and could see no difference in regard of what we do with "SuSEfirewall2".
However, knowing that there were recent changes to yast2_lan, and this is where we install the firewall package I am asking to crosscheck
@riafarov could you please crosscheck if this is related to recent yast2_lan test module changes?
I am also wondering why do we even need to install SuSEfirewall2? Shouldn't it be installed by default? However this is nothing new as we already had this behaviour in openSUSE Leap 42.3 GM: https://openqa.opensuse.org/tests/451716#step/yast2_lan/11
Updated by okurz about 5 years ago
- Subject changed from [functional][y][fast leap 42.3 openssh tests broken since february 7th to [functional][y][fast] leap 42.3 openssh tests broken since february 7th
Updated by riafarov about 5 years ago
- Due date changed from 2019-02-12 to 2019-02-26
Anyway, that's next sprint anyway.
Updated by riafarov about 5 years ago
So yes, it's due to rollback, as we have installed SuSEfirewall in yast2_lan, it never had milestone flag, so it just exposed this issue which always had, as sshd relies on it.
Updated by riafarov about 5 years ago
- Status changed from Workable to Feedback
Change which affected scenario was reverted (removed the flag): https://openqa.opensuse.org/tests/852155#settings
I will create follow up tickets to make it right.
Updated by riafarov about 5 years ago
- Status changed from Feedback to Resolved