action #179074
closed[tools][openQA][autoinst] autoinst url of repositories 404 Not Found size:S
0%
Description
Observation¶
I am using autoinst_url with repositories resources on openqa.suse.de, for example, http://openqa.suse.de/assets/repo/SLE-15-SP7-Full-x86_64-Build74.1-Media1/.
But the returned url from autoinst_url can not be found, for example, http://grenache-1.oqa.prg2.suse.org:20173/C4NO59dGxWGL_Osp/assets/repo/SLE-15-SP7-Full-x86_64-Build74.1-Media1/.
Because curl --silent -I does not return 200 OK. Instead it returns 404 Not Found.
Please refer to failed test runs because of this issue:
https://openqa.suse.de/tests/17082300#step/unified_guest_installation/354
https://openqa.suse.de/tests/17082301#step/unified_guest_installation/342.
Have no such issue with hdd resources, for example, http://worker33.oqa.prg2.suse.org:20173/nqWRrLSMHm7B_vPp/assets/hdd/SL-Micro.x86_64-6.2-Default-encrypted-Build5.5.raw.xz from http://openqa.suse.de/assets/hdd/SL-Micro.x86_64-6.2-Default-encrypted-Build5.5.raw.xz.
Steps to reproduce¶
- Call autoinst_url with repository resources on openqa.suse.de
Impact¶
Can not use repositories resources from worker machine
Problem¶
- A defect ???
Suggestions¶
- Need clarification whether repositories can be used from worker machine: openQA syncs iso and hdd assets to workers but repos are not synced. So maybe we just need a better error handling about autoinst_url?
- Be aware about a semi-related discussion in a Slack thread on #eng-testing https://suse.slack.com/archives/C02CANHLANP/p1742278969087459 (about HDD assets from NUE2 ending up with 403 because of CC-related restrictions) and also follow https://suse.slack.com/archives/C02CANHLANP/p1742287692534429 about this ticket
Workaround¶
Use directly without calling autoinst_url
Updated by okurz 16 days ago
- Tags set to reactive work, support
- Subject changed from [openQA][autoinst] autoinst url of repositories 404 Not Found to [tools][openQA][autoinst] autoinst url of repositories 404 Not Found
- Category set to Infrastructure
- Priority changed from Normal to High
- Target version set to Ready
Updated by waynechen55 15 days ago
@okurz The issue still persists. See https://openqa.suse.de/tests/17101393#step/unified_guest_installation/342.
Updated by waynechen55 14 days ago
If you think repo can not be used from worker machine, I will switch back to use openQA url directly. @okurz
Updated by okurz 13 days ago
waynechen55 wrote in #note-6:
If you think repo can not be used from worker machine, I will switch back to use openQA url directly. @okurz
Well, repos can be used "from worker machines" but the repos are only on the openQA server, not synced to workers. And it's not clear how autoinst_url should behave which is planned to be better understood as part of this ticket.
Updated by waynechen55 11 days ago ยท Edited
okurz wrote in #note-7:
waynechen55 wrote in #note-6:
If you think repo can not be used from worker machine, I will switch back to use openQA url directly. @okurz
Well, repos can be used "from worker machines" but the repos are only on the openQA server, not synced to workers. And it's not clear how autoinst_url should behave which is planned to be better understood as part of this ticket.
I am OK with only openQA server if you do not think this is a very necessary case to be used.
Updated by mkittler 10 days ago
- Status changed from In Progress to Feedback
I think using autoinst_url for repository assets is simply not going to work. What this function does is returning a URL so an asset can be downloaded from an HTTP server that runs locally on the worker host. The problem is that repository assets are simply not copied to the worker host (unlike iso, hdd and other assets).
So I'd say simply don't use that function to access repository assets. Note that it also is not required to access those. We restricted access to assets but the restriction only applies to HDD assets. So you only need to use autoinst_url for those assets. (Sorry if I have suggested something else previously on Slack.)
Updated by mkittler 7 days ago
- Status changed from Feedback to Resolved
The PR has been merged. I haven't gotten any feedback so I am just resolving this ticket with the explanation from #179074#note-11.
Updated by waynechen55 3 days ago
mkittler wrote in #note-13:
The PR has been merged. I haven't gotten any feedback so I am just resolving this ticket with the explanation from #179074#note-11.
LGTM