[ovirt-devel] Re: OST: How to run ost.sh with a local custom repo?
Marcin Sobczyk <msobczyk(a)redhat.com> writes:
On 8/4/21 1:30 PM, Milan Zamazal wrote:
> Hi,
>
> when I try to run ost.sh on a local repo with
> --custom-repo=file:///home/pdm/rpmbuild/repodata/repomd.xml, I get the
> following error:
>
> requests.exceptions.InvalidSchema: No connection adapters were
> found for 'file:///home/pdm/rpmbuild/repodata/repomd.xml
>
> I tried using file:/home/... and /home/... but neither works.
> https://... works fine.
>
> How can I run the script with a custom repo in a local directory?
Hi,
this is most probably caused by:
https://github.com/oVirt/ovirt-system-tests/blob/0ad56d467ac0e608c568f597...
you can comment out this line and most probably your problems will go
away.
It stops reporting the original error but it still doesn't work:
Curl error (37): Couldn't read a file:// file for
file:///home/ost/rpmbuild/repodata/repomd.xml [Couldn't open file
/home/ost/rpmbuild/repodata/repomd.xml]
The file exists and is world readable so the problem apparently is the
local directory repo is not propagated to the right location.
If it works, please let us know here, and I'll adapt the code to
make
it work
with local repos like these.
Michal Skrivanek <michal.skrivanek(a)redhat.com> writes:
> On 4. 8. 2021, at 13:47, Marcin Sobczyk
<msobczyk(a)redhat.com> wrote:
>
>
>
> On 8/4/21 1:30 PM, Milan Zamazal wrote:
>> Hi,
>>
>> when I try to run ost.sh on a local repo with
>> --custom-repo=file:///home/pdm/rpmbuild/repodata/repomd.xml, I get the
>> following error:
>>
>> requests.exceptions.InvalidSchema: No connection adapters were
>> found for 'file:///home/pdm/rpmbuild/repodata/repomd.xml
>>
>> I tried using file:/home/... and /home/... but neither works.
>> https://... works fine.
>>
>> How can I run the script with a custom repo in a local directory?
You have those VMs running, you can just copy whatever files or vdsm rpm or whatnot, and
run tests…
Do you mean as an end user? The VMs are not running initially and
copying files manually is cumbersome.
If it cannot be automated in OST then the easiest solution may be to run
a web server on the host serving the repo(s). The host IP is reachable
from the VMs so it should work some way. Did I say that running OST
from Podman has its advantages? ;-)