action #102344
closedjeos-containers@RPi3 has a wrong schedule
0%
Description
jeos-containers@RPi3
has a wrong schedule, see: https://openqa.opensuse.org/tests/2032095
It tries to run boot_to_desktop
instead of prepare_firstboot
etc.
The only diff I can spot in Settings is:
+CONTAINER_RUNTIME docker,podman
Updated by ggardet_arm over 2 years ago
This also affects jeos-containers@aarch64-HD24G
Updated by ggardet_arm over 2 years ago
This may be related to https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13605
Updated by jlausuch over 2 years ago
It is actually being addressed:
https://progress.opensuse.org/issues/102272
https://progress.opensuse.org/issues/102278
with PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13672
But I need to still work on some proposal to tidy up container tests in 15.3 Images...
Feel free to close this one as duplicate. Otherwise, all the 3 tickets will be solved at once, which is also fine.
Updated by ggardet_arm over 2 years ago
Thanks for the links. Let's keep it open for now, with the 2 others, until fixed.
Updated by ggardet_arm over 2 years ago
- Related to action #102272: [opensuse] [qa-c] test fails in host_configuration added
Updated by ggardet_arm over 2 years ago
- Related to action #102278: test fails in boot_to_desktop added
Updated by jlausuch over 2 years ago
- Project changed from openQA Tests to Containers
- Status changed from New to In Progress
- Assignee set to jlausuch
Updated by jlausuch over 2 years ago
- Status changed from In Progress to Feedback
Updated by jlausuch over 2 years ago
BTW, JeOS tests shouldn't have BOOT_HDD_IMAGE=1
variable. They are scheduled here https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/products/opensuse/main.pm#L261
So, I will remove that variable from the job, at least for containers, since it will mess the schedule in containers... https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/main_containers.pm#L90
Updated by jlausuch over 2 years ago
- Status changed from Feedback to Resolved
Fixed together with the related tickets.