action #109452
closed
[Timebox: 8h] Investigate script_output failure in validate_addon_extension_repo_*
Added by geor about 2 years ago.
Updated about 2 years ago.
Description
Motivation¶
Modules validate_addon_extension_repo_http and validate_addon_extension_repo_ftp fail sporadically in validate_repo_properties().
The failure occurs during inside script_ouput stage of parse_repo_data() and can be seen here, but it is most likely not related to the bsc#1193214 failure (seen here).
Acceptance criteria¶
AC1: Investigate the failure in script_output.
AC2: File a new progress issue (or a product bug) depending on the findings.
Further Information¶
It is a bit weird that in autoinst-log.txt we see command 'curl -f -v http://10.0.2.2:20063/k2w1yCaJzocsF6Je/current_script > /tmp/scriptC_1nj.sh' failed at /usr/lib/os-autoinst/testapi.pm line 953. but the command is different in the console before the failure
I do not understand the description, in "and can be seen here", "here" points to the test suite, not to a specific step, so I'm not seeing the issue you're mentioning. All I see is that the failure comes from the fact the "Alias" is "Repository" so for me it's correctly tagged with https://bugzilla.suse.com/show_bug.cgi?id=1193214.
- Description updated (diff)
JRivrain wrote:
I do not understand the description, in "and can be seen here", "here" points to the test suite, not to a specific step, so I'm not seeing the issue you're mentioning. All I see is that the failure comes from the fact the "Alias" is "Repository" so for me it's correctly tagged with https://bugzilla.suse.com/show_bug.cgi?id=1193214.
Updated. I put wrong link in the description. The Repository for Alias bug is correctly tagged and this failure is not related to this ticket (although it can be seen in the first module failing) but the other failure is the one I m describing.
- Tags deleted (
qe-yast-refinement)
- Status changed from New to Rejected
Also available in: Atom
PDF