Actions
action #157774
closedcoordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #154780: [epic] openQA scenario definitions fully in git
Empty scenario definitions causing Use of uninitialized value $testsuite_name in hash element in lib/OpenQA/Schema/Result/JobGroups.pm size:S
Start date:
2024-03-22
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
This has not been flagged by any alerts as far as I am aware. It is visible in logs, though:
journal:
Mar 21 14:49:58 openqa openqa[29349]: Use of uninitialized value $testsuite_name in hash element at /usr/share/openqa/script/../lib/OpenQA/Schema/Result/JobGroups.pm line 413.
accesslog:
[21/Mar/2024:14:49:58 +0100] "POST /api/v1/job_templates_scheduling/510
[21/Mar/2024:14:49:58 +0100] "POST /api/v1/job_templates_scheduling/319
[21/Mar/2024:14:49:58 +0100] "POST /api/v1/job_templates_scheduling/456
This seems to be caused by this type of scenario:
scenarios:
# ...
s390x:
sle-15-SP6-Migration-from-SLE15-SPx-s390x:
- {}
See https://openqa.suse.de/admin/job_templates/319 at the time of this writing. Despite the errors/warnings this is valid with the current schema.
Suggestions¶
- Consider the proposed trivial fix but also notably the conversation in https://github.com/os-autoinst/openQA/pull/5540#discussion_r1534128393
- The proposed fix may not work as-is, but is good for discussion
- Verify the current behavior
- Confirm what the expectation of these uses is, and how else it could be achieved if it is considered wrong, e.g. ask in testing/ check who uses this syntax currently
- Consider changing or extending the YAML schema accordingly
Actions