action #122440
Updated by okurz over 2 years ago
## 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 :)