Project

General

Profile

Actions

action #123277

closed

coordination #121858: [epic] Automation of YaST in Container

Automate YaST firewall in ALP

Added by JERiveraMoya over 1 year ago. Updated 5 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2023-01-18
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Another interesting module to tackle with libyui-rest-api for YaST in container is YaST2 firewall.

Prerequisites:
Firewall is activated by default in ALP, so this test assume that we will have some sort of test (or even inside the new test created in this task) that will stop firewalld via command line before interacting with UI with libyui-rest-api and start to send GET and POST calls.
Steps:

  1. Open YaST2 Firewall in container (directly, not though the control center)
  2. Check current status is Inactive
  3. Change Service Configuration to Start/Start on boot
  4. Navigate to public zone and tab Ports
  5. Add libyui-rest-api port to TCP Ports
  6. Accept
  7. Verify that firewalld is active and enabled
  8. Check with firewall-cmd that the port is open

Acceptance criteria

AC1: Create new test to enable firewall and and open port for libyui-rest-api
AC2: Schedule new test as the first one in the test suite
AC3: Use POM pattern without Controllers to design this test

Additional information

We did recent work with firewalld in opensuse/sle but we were still using controllers.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15496
We could reuse some parts, but we should improve and simplify even more the development not using controllers and providing proper POM.

Take a look to the example we have for POM without controllers at the moment:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16072/files

Actions

Also available in: Atom PDF