action #122440
closed
[sporadic] openQA Assetpack download can fail on initial download size:M
Added by okurz over 1 year ago.
Updated about 1 year ago.
Category:
Feature requests
Description
Observation¶
https://openqa.opensuse.org/tests/2978761/logfile?filename=openqa_webui-openqa_nohup_out.txt shows
[info] Caching "https://cdn.datatables.net/1.10.16/css/dataTables.bootstrap4.css" to "/root/openQA/script/../assets/cache/cdn.datatables.net/1.10.16/css/dataTables.bootstrap4.css".
[info] Caching "https://cdn.jsdelivr.net/npm/fork-awesome@1.2.0/css/fork-awesome.min.css" to "/root/openQA/script/../assets/cache/cdn.jsdelivr.net/npm/fork-awesome@1.2.0/css/fork-awesome.min.css".
[warn] [AssetPack] Unable to download https://raw.githubusercontent.com/bootstrapthemesco/bootstrap-4-multi-dropdown-navbar/beta2.0/css/bootstrap-4-navbar.css: Connect timeout
Could not find input asset "https://raw.githubusercontent.com/bootstrapthemesco/bootstrap-4-multi-dropdown-navbar/beta2.0/css/bootstrap-4-navbar.css". at /usr/lib/perl5/vendor_perl/5.36.0/Mojolicious/Plugin/AssetPack.pm line 172.
openQA is licensed GPL-2.0 - Version 4.6.1671708203.c9f8b10
The openqa-investigate retry jobs passed so sporadic download issue
Acceptance criteria¶
- AC1: the openQA asset handling ensures that temporary network issues "Connect timeout" are handled with retrying
Suggestions¶
- We can probably do some retrying on download issues
- Check the code in the AssetPack Mojolicious plugin. As necessary propose upstream solution, as alternative handle with some hard-core log parsing in downstream and just retry :)
- Subject changed from openQA Assetpack download can fail on initial download to openQA Assetpack download can fail on initial download size:M
- Description updated (diff)
- Status changed from New to Workable
- Tags changed from reactive work to reactive work, sporadic, asset pack, download, openqa-in-openqa
- Subject changed from openQA Assetpack download can fail on initial download size:M to [sporadic] openQA Assetpack download can fail on initial download size:M
- Priority changed from Normal to High
These downloads are only done when a developer sets up openQA from a Git checkout. Normally I just retry on my own and don't find it very tedious as it happens only very rarely and its something one doesn't need to do very often. I suppose this is considered of high prio only because openQA tests fail but normally I'd consider this not very important.
Likely it makes most sense to add this feature on AssetPack level so other projects can benefit from it as well. Note that a retry could also be implemented in the openQA test itself but this would likely be slower.
I remember from retrying manually (when it happened locally) that one sometimes needed to get rid of some asset caching related files first. I'm not sure exactly about this anymore but one maybe need to keep it in mind.
mkittler wrote:
Likely it makes most sense to add this feature on AssetPack level so other projects can benefit from it as well. Note that a retry could also be implemented in the openQA test itself but this would likely be slower.
Agreed. We should just add that upstream.
- Status changed from Workable to In Progress
- Due date set to 2023-02-07
Setting due date based on mean cycle time of SUSE QE Tools
- Related to action #123496: [tools][openQA-in-openQA][sporadic] test fails in worker because of GNOME authentication dialog size:M added
- Status changed from In Progress to Feedback
Merged upstream, now we wait for it to reach factory.
- Due date changed from 2023-02-07 to 2023-02-17
Looks like Tumbleweed is still shipping with perl-Mojolicious-Plugin-AssetPack 2.13. So we've got to wait a little longer for 2.14.
- Status changed from Feedback to In Progress
- Related to action #124739: o3 deployment failed due to "run(/usr/bin/ruby) failed: Permission denied at /usr/lib/perl5/vendor_perl/5.26.1/Mojolicious/Plugin/AssetPack/Pipe.pm line 27" and then "run(/bin/sass) failed: No such file or directory" size:M added
- Due date changed from 2023-02-17 to 2023-02-24
- Status changed from In Progress to Feedback
openQA 4.6.1676888404.afe11c5-lp154.5596.1 deployed on o3 and everything seems to be ok
- Status changed from Feedback to Resolved
Also available in: Atom
PDF