On Tue, Jul 3, 2018 at 11:47 PM Nir Soffer <nsof...@redhat.com> wrote:

> On Tue, 3 Jul 2018, 15:44 , <etienne.charl...@reduspaceservices.eu> wrote:
>
>> Hello,
>>
>> I' m trying without success to import a qcow2 file into ovirt. I tried on
>> a ISCSI datadomain and an nfs datadomain.
>>
>> I struggled quite a lot to have the "test connection" succed ( I write a
>> small shell script to "deploy" letsencryt certificates into ovirt engine)
>>
>> Doc is not clear on the fact that certificates for imageio-proxy are
>> different than for main engineā€¦
>>
>>
>> Now, the upload fails with
>>
>> Transfer was stopped by system. Reason: failed to add image ticket to
>> ovirt-imageio-proxy.
>> Image gets stuck in "transfer paused by system"
>>
>> Any idea ?
>>
>
> you probably have bad cretificate configuration in the proxy. Why not use
> the default certificates generated by engine setup? This is how we test the
> proxy.
>

Can  you share the contents of:
/etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf

And the proxy log at
/var/log/ovirt-imageio-proxy/image-proxy.log
Showing the time of the error (failed to add image ticket to
ovirt-imageio-proxy.)

Nir


>
>
>> ovrit is up to date: 4.2.4 on both engine and hosts.
>> _______________________________________________
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/FTC3PBZCRRTI2LBADOPOS2EYRCZ6EQA3/
>>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PRRW3GZYHURRFMSDSJMXWBX4DIGHXE43/

Reply via email to