action #32548
closed[sle][functional][u][systemd][medium]userspace_systemd needs to be updated for more recent systemd version
0%
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-qa_userspace_systemd@64bit fails in
execute_test_run
and https://openqa.suse.de/tests/1509632#step/1_systemd/40
Reproducible¶
Fails since (at least) Build 414.13
Tasks¶
- Learn where and how "userspace" test suites are maintained
- Update test case according to suggestion in https://bugzilla.suse.com/show_bug.cgi?id=1082976#c1
Further details¶
Always latest result in this scenario: latest
Updated by okurz about 6 years ago
I guess it's https://build.suse.de/package/show/QA:Head/qa_test_systemd and probably something inside qa_test_systemd-1.tar.bz2 . The only reference to "rc-local" in there is the file "services" which is a simple list of services. I think we would solve the issue by just removing this line but I do not know how to test this.
Updated by yosun about 6 years ago
Simply remove rc-local from service list can solve the problem, but rc-local will not cover in this testsuite, maybe take care of it in somewhere else. qa_test_systemd, this test package is very simple, run this *run file in this package can check systemctl start/stop/status/restart... for each service in service list.
The fail for rc-local can understand for me, but the fail for named I can't understand. Because it can run pass in my physical server, but only always fail in openQA.
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qa_userspace_systemd
https://openqa.suse.de/tests/1541085
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qa_userspace_systemd
https://openqa.suse.de/tests/1582828
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qa_userspace_systemd
https://openqa.suse.de/tests/1624690
Updated by okurz almost 6 years ago
- Due date set to 2018-06-05
- Difficulty set to medium
Updated by okurz almost 6 years ago
- Blocks action #33982: [sle][functional][u] test fails in install_test_suite - because qa_test_systemd cannot be installed added
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qa_userspace_systemd
https://openqa.suse.de/tests/1689062
Updated by oorlov almost 6 years ago
How can I find the source code for 1_systemd?
OpenQA doesn't provide any logs for the failed test module. Also, while I'm clicking on the module name, I'm getting 404 PageNot Found.
Updated by okurz almost 6 years ago
oorlov wrote:
How can I find the source code for 1_systemd?
See #32548#note-1 . The relevant project here is https://build.suse.de/package/show/QA:Head/qa_test_systemd which has an archive which includes the relevant tests as executable code.
OpenQA doesn't provide any logs for the failed test module. Also, while I'm clicking on the module name, I'm getting 404 PageNot Found.
Yes, because the step details are not coming from a corresponding test module source file but are dynamically generated within the "execute_test_run" module. IIUC @mkittler is already working on improving the UI for these kinds of tests. Due to your low local distance you should talk to him if this is already tracked within his backlog.
Updated by oorlov almost 6 years ago
- Status changed from Workable to In Progress
- Assignee set to oorlov
Updated by oorlov almost 6 years ago
- Status changed from In Progress to Feedback
I've added executable file '/etc/init.d/boot.local' manually, as proposed in bsc#1082976 and the rc-local test started passing.
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5135
The only thing is that this module has two more failed tests - check-named and check-systemd-machined. I'll investigate the issues and add appropriate tickets if it is required.
Updated by oorlov almost 6 years ago
Both "systemctl status named" and "systemctl status systemd-machined" return "Unit {service name}.service could not be found" on the system under test.
The check-named test was appeared in Build 486.4 (28.02.2018) and failed since the first run.
The check-systemd-machined is in the test suite since the suite was added. It started failing since Build 538.1 (02.04.2018) and never passed after that.
Do someone know why they disappeared and is it expected? Should we still maintain those tests or just remove them?
Updated by oorlov almost 6 years ago
According to okurz's comment on my PR, the appropriate file should be added in test suite itself.
After researching with SLindoMansilla, it was decided to update 'qa_test_systemd.spec' file in the test suite.
GitHub Repo for test suites: https://github.com/SUSE/qa-testsuites
OBS: https://build.suse.de/package/show/QA:Head/qa_test_systemd
Currently, the work is in progress.
Updated by oorlov almost 6 years ago
We've added a dummy init file, but got an error message that we are not able to handle after our research.
Added an appropriate comment with ask for assistance in bsc#1082976
Updated by SLindoMansilla almost 6 years ago
- Status changed from Feedback to Blocked
Actually, we were updating the github source code, but in order to test it, we were applying the changes directly to a home branch and we got this error message.
[ 3s] E: Reserved file `boot.local' found in /home/abuild/rpmbuild/BUILDROOT/qa_test_systemd-1-0.x86_64/etc/init.d/!
[ 3s] ERROR: found one or more broken init or boot scripts, please fix them.
[ 3s] For more information about LSB headers please read the manual
[ 3s] page of of insserv by executing the command `man 8 insserv'.
[ 3s] If you don't understand this, mailto=werner@suse.de
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-06-05 to 2018-06-19
- Target version changed from Milestone 16 to Milestone 17
Updated by okurz almost 6 years ago
@SLindoMansilla, oorlov, blocked by what ticket?
Updated by SLindoMansilla almost 6 years ago
Updated by SLindoMansilla almost 6 years ago
I need to verify with systemd maintainer if the test we are trying to fix is something no more supported by SUSE, or if we have detected a regression about a missing feature.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-06-19 to 2018-07-03
- Status changed from Blocked to Workable
bug is marked as invalid - unblocking
Updated by oorlov almost 6 years ago
- Assignee changed from oorlov to SLindoMansilla
The bug bsc#1082976, but according to the comment#21 by @SLindoMansilla, we need to check if the test is still valid or not. Assigned to @SLindoMansilla.
Updated by SLindoMansilla almost 6 years ago
- Status changed from Workable to In Progress
What I can see is that actually the userspace_systemd is not testing systemd but a sort of services/units that programs packages install.
It is only testing systemctl start and systemctl stop of those services/units. It would be easy to port this userspace_systemd to an openQA module and, for example, execute it in test suite extra_tests_in_textmode.
I also suggest to use the name systemd_service_files for the new module instead of userspace_systemd.
Updated by okurz almost 6 years ago
- Due date deleted (
2018-07-03) - Status changed from In Progress to Workable
- Assignee deleted (
SLindoMansilla) - Target version changed from Milestone 17 to Milestone 21+
As discussed with SLindoMansilla in person as well: Currently we plan to not bring the userspace regression tests into SLE12SP4 which is our focus project for now and therefore we delay the work on this until e.g. we pick it up again in SLE15SP1
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qa_userspace_systemd
https://openqa.suse.de/tests/1771778
Updated by okurz over 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qa_userspace_systemd
https://openqa.suse.de/tests/1771778
Updated by okurz over 5 years ago
- Target version changed from Milestone 21+ to Milestone 23
Updated by okurz about 5 years ago
- Blocked by action #42101: [functional][u] include "userspace regressions" in "functional" added
Updated by okurz about 5 years ago
- Status changed from Workable to Blocked
- Assignee set to okurz
- Target version changed from Milestone 23 to Milestone 26
Updated by okurz almost 5 years ago
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 26 to Milestone 29
Updated by mgriessmeier over 4 years ago
- Target version changed from Milestone 29 to Milestone 30
needs to be discussed offline
Updated by SLindoMansilla almost 4 years ago
- Status changed from Blocked to Rejected
- Assignee changed from mgriessmeier to SLindoMansilla
QSF-U already communicated the deletion of "userspace regressions" tests.