[ovirt-users] Uploading big raw disks into storage

Mon Jan 22 22:19:13 UTC 2018

Hi again!

Well, I discovered something new.... importing using the upload_disk.py
from sdk4 "created" thousands of shards on my glusterfs volume. Is there a
way to remove this files? What will happen if I delete all files from
.shard/*? Will break my volume?

Thanks, if needed I will ask directly on glusterfs mailing-list.

Best Regards Gabriel

Gabriel Stein
------------------------------
Gabriel Ferraz Stein
Tel.: +49 (0)  170 2881531

2018-01-22 21:37 GMT+01:00 Gabriel Stein <gabrielstein at gmail.com>:

> Thanks for your answers!
>
> @Matthias:
>  I used it and didn't works, same error. Now I have another big problem:
> all uploads that I made weren't deleted and my domain storage is full, I
> will need to wipe them, don't known how.
>
> @Sandro
>
> Looking forward, thank you!
>
> All the best
>
> Gabriel
>
> Gabriel Stein
> ------------------------------
> Gabriel Ferraz Stein
> Tel.: +49 (0)  170 2881531
>
> 2018-01-22 16:07 GMT+01:00 Matthias Leopold <matthias.leopold at meduniwien.
> ac.at>:
>
>>
>>
>> Am 2018-01-22 um 11:36 schrieb Gabriel Stein:
>>
>>> Hello!
>>>
>>> I'm still migrating the VMs from Proxmox to oVirt, migrating all disks,
>>> one by one.
>>>
>>> Google Chrome doesn't accept anymore the certificates from ovirt-engine,
>>> firefox it's ok.
>>>
>>> Error(I receive that direct from start from upload on google chrome, on
>>> firefox works):
>>> /
>>> /
>>> /Unable to upload image to disk a-b-c due to a network error. Make sure
>>> ovirt-imageio-proxy service is installed and configured, and ovirt-engine's
>>> certificate is registered as a valid CA in the browser. The certificate can
>>> be fetched from https://<engine_url>/ovirt-eng
>>> ine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA/
>>>
>>>
>>> BUT! When I'm uploading big disks(using firefox), such > 100GB,
>>> ovirt-engine interrupts the process, giving the same error above. I think
>>> that is a kind of timeout and the error doesn't show the real problem.
>>>
>>> On engine.log is the same error. on image-proxy.log:
>>>
>>> (Thread-5834) WARNING 2018-01-22 10:46:07,708 web:89:web:(log_response)
>>> 1.1.1.1 - PUT /d69d1a59-ed5c-4097-a9af-5e2d36299181 401 360 (0.00s)
>>> (Thread-5835) INFO 2018-01-22 10:46:10,716 web:89:web:(log_response)
>>> 1.1.1.1 - OPTIONS /d69d1a59-ed5c-4097-a9af-5e2d36299181 204 0 (0.00s)
>>> (Thread-5836) ERROR 2018-01-22 10:46:10,722
>>> session:314:root:(_decode_ovirt_ticket) Failed to verify proxy ticket:
>>> Ticket life time expired
>>> (Thread-5836) ERROR 2018-01-22 10:46:10,722
>>> session:137:root:(start_session) Error starting session: Unable to
>>> verify proxy ticket
>>> Traceback (most recent call last):
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 135, in start_session
>>>      session_id = _create_update_session(ticket, session_id)
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 194, in _create_update_session
>>>      ticket_vars = _decode_proxy_ticket(authorization)
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 237, in _decode_proxy_ticket
>>>      payload = _decode_ovirt_ticket(ticket)
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 315, in _decode_ovirt_ticket
>>>      raise ValueError("Unable to verify proxy ticket")
>>> ValueError: Unable to verify proxy ticket
>>> (Thread-5836) WARNING 2018-01-22 10:46:10,722 web:89:web:(log_response)
>>> 1.1.1.1 - PUT /d69d1a59-ed5c-4097-a9af-5e2d36299181 401 360 (0.00s)
>>> (Thread-5837) INFO 2018-01-22 10:46:13,731 web:89:web:(log_response)
>>> 1.1.1.1 - OPTIONS /d69d1a59-ed5c-4097-a9af-5e2d36299181 204 0 (0.00s)
>>> (Thread-5838) ERROR 2018-01-22 10:46:13,737
>>> session:314:root:(_decode_ovirt_ticket) Failed to verify proxy ticket:
>>> Ticket life time expired
>>> (Thread-5838) ERROR 2018-01-22 10:46:13,737
>>> session:137:root:(start_session) Error starting session: Unable to
>>> verify proxy ticket
>>> Traceback (most recent call last):
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 135, in start_session
>>>      session_id = _create_update_session(ticket, session_id)
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 194, in _create_update_session
>>>      ticket_vars = _decode_proxy_ticket(authorization)
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 237, in _decode_proxy_ticket
>>>      payload = _decode_ovirt_ticket(ticket)
>>>    File "/usr/lib/python2.7/site-packages/ovirt_imageio_proxy/session.py",
>>> line 315, in _decode_ovirt_ticket
>>>      raise ValueError("Unable to verify proxy ticket")
>>> ValueError: Unable to verify proxy ticket
>>> (Thread-5838) WARNING 2018-01-22 10:46:13,738 web:89:web:(log_response)
>>> 1.1.1.1 - PUT /d69d1a59-ed5c-4097-a9af-5e2d36299181 401 360 (0.00s)
>>> (Thread-5839) INFO 2018-01-22 10:46:16,745 web:89:web:(log_response)
>>> 1.1.1.1 - OPTIONS /d69d1a59-ed5c-4097-a9af-5e2d36299181 204 0 (0.00s)
>>> (Thread-5840) ERROR 2018-01-22 10:46:16,750
>>> session:314:root:(_decode_ovirt_ticket) Failed to verify proxy ticket:
>>> Ticket life time expired
>>> (Thread-5840) ERROR 2018-01-22 10:46:16,750
>>> session:137:root:(start_session) Error starting session: Unable to
>>> verify proxy ticket
>>>
>>> There is a bugzilla bug, but it's confusing, I'm already using the
>>> version 4.2 and the error persists.
>>>
>>> Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1514887(no, I'm not
>>> restaring the daemon, the it seems something similar....)
>>>
>>> A thread on version 4.05:
>>>
>>> http://lists.ovirt.org/pipermail/users/2016-November/077706.html
>>>
>>> I need some help...
>>>
>>
>> Hi Gabriel,
>>
>> i posted to this list with a similar issue on 2017-09-12. you can upload
>> disks via CLI, an example script "upload_disk.py" is part of the package
>> python-ovirt-engine-sdk4. i had some trouble using the script, but it was
>> mainly my fault. as far as i can remember it worked in the end...
>>
>> good luck
>> Matthias
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180122/f7aaf076/attachment.html>