action #47408
closed
[functional][u] test fails in sle2docker
Added by dheidler about 5 years ago.
Updated about 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 24
Description
Observation¶
openQA test in scenario OpenQA::Schema::Result::TestSuites=HASH(0xb007090) fails in
sle2docker
Reproducible¶
Fails since (at least) Build 0112
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
In https://bugzilla.suse.com/show_bug.cgi?id=1123502 Flavio Castelli says:
sles images are now shipped via the official SUSE registry, meaning they have to be obtained via a simple docker pull.
sle2docker is also deprecated and is gone from SLE15 onward.
- Target version set to Milestone 24
- Assignee set to pcervinka
- Status changed from New to In Progress
Test shouldn't be scheduled for SLE12SP5. Conditions are somehow wrong in main_common.pm:
if (is_sle(">=12-sp3") && is_sle('<=12-SP4')) {
loadtest "console/sle2docker";
loadtest "console/docker_image";
}
Recommendation in reported bug is quite unclear and I'm not sure what is expected from sle2docker on 12sp5, so i asked few question there. When looking into history, test was limited to <=12sp4, but it was changed to <15 recently.
Quick solution would be to disable sle2docker and don't run it on 12sp5(let's wait on feedback in bsc#1123502).
Although there is no feedback on my questions in bsc#1123502, I still believe that statement about SUSE registry is not all right(not compatible with sle2docker). sle2docker and related images are part of SLE12 Container module(shared across all SP2/SP3/SP4), but I don't see it in repositories in installation job of SLE12SP5 job https://openqa.suse.de/tests/2506629#settings.
@dheidler, @okurz do you know if Container module available for SP5? Not sure what to do at the moment. Maybe is the best way, just disable sle2docker for SP5(if contm is not available for it).
- Status changed from In Progress to Feedback
PR waiting for review/approval.
- Status changed from Feedback to Rejected
Well, I know believe that workaround with soft fail is not needed(GitHUB PR closed). Job failure is correctly tagged with the bug.
Also available in: Atom
PDF