action #34015
closed
[functional][y][easy] yast2/vnc doesn't have rules for firewalld -> workaround for bsc#1088647
Added by dimstar about 6 years ago.
Updated almost 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit fails in
yast2_vnc
Reproducible¶
Fails since (at least) Build 20171029
Expected result¶
SLE 15
Further details¶
Always latest result in this scenario: latest
The VNC test module records a softfailure, and then seems to expect a cleared screen. This needs to be evaluated if the test has wrong assumptions - or if yast would be supposed to clear the screen to black.
- Related to action #30106: [sle][functional][sle15][yast][y][easy] yast2_vnc failed - update to current behaviour added
- Subject changed from yast2/vnc expects 'cleared screen' to [functional][y]yast2/vnc expects 'cleared screen'
- Target version set to Milestone 16
- Due date set to 2018-05-08
- Subject changed from [functional][y]yast2/vnc expects 'cleared screen' to [functional][y] yast2/vnc doesn't have rules for firewalld
- Description updated (diff)
- Status changed from New to Workable
It looks like a bug actually, as tigervnc should contain service definition for firewalld and works fine for Leap15.
- Assignee set to JERiveraMoya
- Subject changed from [functional][y] yast2/vnc doesn't have rules for firewalld to [functional][y][easy] yast2/vnc doesn't have rules for firewalld -> workaround for bsc#1088647
- Difficulty set to easy
Check how we do it for tests/console/yast2_nis.pm
- Status changed from Workable to In Progress
According with developer, it is just wait a little bit for the fix appears in next builds. The reason why we only see this in TW is because we are really installing xorg-x11 by code and this package installs dependency xorg-x11-Xvnc which is in charge to provide definition for service tigervnc and tigervnc-https in the firewall but there is a request about to reload firewall rules when the package is installed that is not present at the moment. In other product we don't see this because xorg-x11 is installed in installation time not in our test, so after rebooting the system and booting again the reload is not required. For instance, Leap recommends xorg-x11-Xvnc https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0/patterns-base/patterns-base.spec?expand=1 but Tw not https://build.opensuse.org/package/view_file/system:install:head/patterns-base/patterns-base.spec?expand=1. Developer wants to create a bug about more specific information related with these control files.
Workaround is easy, I tested and in tw the problem dissapears if we reload the firewall after installing the package (just firewall-cmd --reload after doing the zypper in xorg-x11), but it is better to wait for the fix as it should arrive really soon.
- Related to action #31375: [sle][functional][ipmi][u][hard] test fails in first_boot - VNC installation on SLE 15 failed because of various issues (ipmi worker, first_boot, boot_from_pxe, await_install) added
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF