Project

General

Profile

Actions

action #111054

closed

coordination #103323: [epic] BCI testing

Extend coverage for init container.

Added by jlausuch about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2022-05-13
Due date:
% Done:

100%

Estimated time:

Description

Current init coverage is very low.
https://openqa.suse.de/tests/8743924

We are running the 5 common tests in test_all.py and a single specific test from test_init.py test_systemd_present.

It would be nice to extend the coverage for specific init tests, focusing on systemd.
The implementation is up to the one who picks the ticket, but here are some ideas:

1) Run simple command like systemctl list-units and make sure it works and outputs units.

2) systemctl list-units --type=service --state=active should show active services, like dbus.service or systemd-journald.service (we would need to get a requirement of which services SHOULD be running)

3) systemctl status dbus.service should return Active: active (running) and also we could check the cgroup row, e.g.
CGroup: /machine.slice/libpod-693272c530216bd2e3d795d7548c2a2d99e2d1fa8c03428fed2c9430e8584503.scope/system.slice/dbus.service

4) Play around with some services, e.g. systemctl restart systemd-journald.service (or stop/start) and make sure it is active again.

etc

Actions #1

Updated by ph03nix about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to ph03nix
Actions #2

Updated by ph03nix about 2 years ago

Actions #3

Updated by ph03nix about 2 years ago

  • % Done changed from 0 to 50

The PR is now ready for review. I added new tests for a couple of components, details are to be found in the PR description.

Actions #5

Updated by ph03nix about 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100
Actions

Also available in: Atom PDF