+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1430243 +++ ====================================================================== ## Description of problem: When I try to upload a disk image, it fails with the error: WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [cor-id] Correlation ID: [cor-id], Call Stack: null, Custom Event ID: -1, Message: Unable to upload image to disk <disk-img> 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. ## Version-Release number of selected component (if applicable): rhevm-4.0.6.3-0.1.el7ev.noarch ovirt-engine-4.0.6.3-0.1.el7ev.noarch ovirt-imageio-common-0.3.0-0.el7ev.noarch ovirt-imageio-proxy-0.4.0-0.el7ev.noarch ovirt-imageio-proxy-setup-0.4.0-0.el7ev.noarch ## How reproducible: Always ## Steps to Reproduce: 1. import CA 2. click 'disks' -> 'upload' -> start 3. select image to upload ## Actual results: Some traffic can be seen over port 54323 (between client and rhevm), but then the status goes to 'paused by system'. After a log time, originally stated error appears in the event tab ## Expected results: disk image to import, or a more specific error provided as to the cause of the problem. ## Additional info required ports are open, and 'ImageProxyAddress' is correct (Originally by Marcus West)
Hi Marcus, Please make sure: * The *engine* ca is imported, i.e.: http://<engine_url>/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA * Network isn't blocked (firewall, etc) * You're logged to the WebAdmin using https and fqdn. (Originally by Daniel Erez)
(In reply to Marcus West from comment #0) Which browser are you using? did you try with another browser? (Originally by Nir Soffer)
@Marcus: * Does the client machine have any limitation on upload transfer speed? * Can you please try to reduce the value of UploadImageChunkSizeKB (in vdc_options table) and check whether it mitigates the issue. (Originally by Daniel Erez)
Another solution: try increasing the 'imaged_read_timeout_sec' value (e.g. 300), located in the proxy conf file (/etc/ovirt-imageio-proxy/ovirt-imageio-proxy.conf), and restart the proxy service.. (Originally by Daniel Erez)
> which version of rhel and webob are installed in the working 4.0 env? on rhevmhe1: Red Hat Enterprise Linux Server release 7.3 (Maipo) python-webob-1.2.3-6.el7.noarch eap7-jboss-metadata-web-10.0.0-6.Final_redhat_1.1.ep7.el7.noarch eap7-jboss-websocket-api_1.1_spec-1.1.1-1.Final_redhat_1.1.ep7.el7.noarch ovirt-engine-4.0.6.3-0.1.el7ev.noarch ovirt-imageio-common-0.5.0-0.el7ev.noarch ovirt-imageio-proxy-0.5.0-0.el7ev.noarch ovirt-imageio-proxy-setup-0.5.0-0.el7ev.noarch > Which browser are you using? did you try with another browser? browser: Firefox 45.4.0, on RHEL7 CSB I also have Chrome 54.0.2840.59, will try that also (Originally by Marcus West)
Nir / Daniel, Anything special in the scenario that should be tested? It seems to me just a regular UI upload.. (Originally by Natalie Gavrilov)
Verified using: ovirt-engine-4.1.2.2-0.1.el7.noarch rhevm-4.1.2.2-0.1.el7.noarch ovirt-imageio-common-1.0.0-0.el7ev.noarch ovirt-imageio-proxy-1.0.0-0.el7ev.noarch ovirt-imageio-daemon-1.0.0-0.el7ev.noarch vdsm-4.19.15-1.el7ev.x86_64 Scenario tested: Upload images using python-sdk: a. rate: 1MB/s b. rate 512KB/s Also checked data integrity using md5sum.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1692