action #43511
closed
[functional][u] Asset cache does not support ASSET_ assets
Added by szarate over 5 years ago.
Updated about 5 years ago.
Category:
Feature requests
Target version:
SUSE QA - Milestone 23
Description
Observation¶
In job this job there's an extra asset being defined, and Gru has already code to handle "external downloads" however the caching does not handle these, causing the job to die.
ASSET_1_URL https://w3.nue.suse.com/~slindomansilla/tmp/bootloader_poo40670.pm
SCHEDULE bootloader_poo40670,tests/installation/welcome
error on bootloader_poo40670.pm: Can't locate ../../../pool/1/bootloader_poo40670.pm in @INC (you may need to install the ..::..::..::pool::1::bootloader_poo40670 module) (@INC contains: ../../../pool/1 /var/lib/openqa/cache/tests/sle/lib /var/lib/openqa/pool/1/blib/arch /var/lib/openqa/pool/1/blib/lib /usr/lib/os-autoinst /usr/lib/perl5/site_perl/5.18.2/ppc64le-linux-thread-multi /usr/lib/perl5/site_perl/5.18.2 /usr/lib/perl5/vendor_perl/5.18.2/ppc64le-linux-thread-multi /usr/lib/perl5/vendor_perl/5.18.2 /usr/lib/perl5/5.18.2/ppc64le-linux-thread-multi /usr/lib/perl5/5.18.2 /usr/lib/perl5/site_perl .) at (eval 739) line 1.
In a more optimal scenario, the webUI shows a list of assets to download, and the cache just takes care of said list, except the repos.
Acceptance criteria¶
- AC1: A job scheduled with a downloadable override test module can run successfully on osd
Suggestions¶
- Hook into the detect_asset_keys method of OpenQA::Worker::Engines::isotovideo and add handling for the ASSET_*_URL.
- Subject changed from [y][u] Asset cache does not support 'other' assets to [functional][u] Asset cache does not support 'other' assets
- Description updated (diff)
- Assignee set to szarate
- Target version set to Milestone 21
@szarate please clarify the suggestions to make it workable
- Description updated (diff)
- Status changed from New to In Progress
After looking at changes to the cache, I think this can be done independantly. as we already support KERNEL and INITRD. and the handling for asset urls didn't change...
Working on this today.
- Status changed from In Progress to Feedback
PR merged, we should be able to test this tomorrow on o3 assuming that the auto-deployment of workers does its job.
I think the attempted fix here was wrong and would not have worked. I think https://github.com/os-autoinst/openQA/pull/1907 should fix it. If someone can check this out, that'd be great (I don't have worker caching enabled on the Fedora instances ATM, so I can't test it out Most Interesting Man In The World-style):
- Subject changed from [functional][u] Asset cache does not support 'other' assets to [functional][u] Asset cache does not support ASSET_ assets
- Assignee deleted (
szarate)
More information can be found on: https://github.com/os-autoinst/openQA/pull/1907#issuecomment-444394975
Long story short: loadtests needs to support loading test scripts out of tree (out of $CASEDIR), for this either the find_script or the load_tests itself needs to be modified in the os_autoinst project, by altering the behaviour if the SCHEDULE backend variable is set.
- Status changed from Feedback to Workable
Also as agreed we set back to "Workable", no use to have it in "Feedback" without an assignee.
szarate wrote:
More information can be found on: https://github.com/os-autoinst/openQA/pull/1907#issuecomment-444394975
Long story short: loadtests needs to support loading test scripts out of tree (out of $CASEDIR), for this either the find_script or the load_tests itself needs to be modified in the os_autoinst project, by altering the behaviour if the SCHEDULE backend variable is set.
But that is already working, see https://github.com/os-autoinst/os-autoinst/pull/1019 . The problem is only with cache it seems.
I m taking this one back for the time being :)
- Status changed from Workable to In Progress
I'm still looking at bits and pieces, but the asset isn't really downloaded for the time being to the pool nor is linked in the test. Initially cache wouldn't look at other assets except for kernel and initrd, downloadable assets were never meant to be part of cache (it came after)...
So for the time being I guess it's matter of registering a downloaded asset as part of a job (which somehow already is), and ensure the cache properly links it. Perhaps in the meantime, explain a bit better how it's all connected
- Target version changed from Milestone 21 to Milestone 22
- Status changed from In Progress to Workable
I will drop this one for now. I'm taking too long figuring out how to add unit tests for the download part in gru (Note that I mean both things together ;) not the unit tests that are in 14-grutasks.t)
- Related to action #45038: [functional][y][leap] test fails in installation - autoyast profile can not be retrieved, no network? added
- Status changed from Workable to In Progress
- Related to action #46094: [sle][functional][u] test fails in installation - missing assets or wrong link added
- Related to deleted (action #46094: [sle][functional][u] test fails in installation - missing assets or wrong link)
- Blocks action #46094: [sle][functional][u] test fails in installation - missing assets or wrong link added
- Status changed from In Progress to Feedback
- Target version changed from Milestone 22 to Milestone 23
- Blocks action #36994: Dynamic test flow definition + override added
- Status changed from Feedback to Resolved
Also available in: Atom
PDF