Re: [ovirt-users] Can't upload qcow2 images via web UI
On Tue, Nov 8, 2016 at 12:50 PM, วีร์ ศรีทิพโพธิ์wrote: > > On Nov 8, 2559 BE, at 16:50, Amit Aviram wrote: > > Hi Wee. > Looking in your logs, it looks like "ovirt-imageio-daemon" service, which > runs in the oVirt's host (ovirt03.forest.go.th), doesn't accept the > requests as should. Please, log into this host and restart this service, > running: > > *service ovirt-imageio-daemon restart* > > > And try upload. > > If this won't work, please send us the output of "journalctl -xeu > ovirt-imageio-daemon" from ovirt03.forest.go.th. > > Thanks, Amit. > > > Hi Amit, > > I restarted ‘overt-imageio-daemon’ service in > > ovirt03.forest.go.th but still can’t upload. Here is the output from > ‘journalctl -xeu overt-imageio-daemon’ command in ovirt03.forest.go.th: > > > > Thank you, > Wee. > > Indeed the requests from ovirt-imageio-proxy doesn't get to ovirt-imageio-daemon. you can see in the proxy logs that a "No route to host" is logged. Initially our setup opens up the needed ports in iptables in order to allow this connection, but if it was changed somehow it will break the upload flow. Can you make sure that port 54322 is open for input requests in ovirt03.forest.go.th, and also open for output request where the proxy resides? Or whatever reason for the host not be reachable? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can't upload qcow2 images via web UI
On Nov 8, 2559 BE, at 16:50, Amit Aviramwrote:Hi Wee.Looking in your logs, it looks like "ovirt-imageio-daemon" service, which runs in the oVirt's host (ovirt03.forest.go.th), doesn't accept the requests as should. Please, log into this host and restart this service, running:service ovirt-imageio-daemon restartAnd try upload.If this won't work, please send us the output of "journalctl -xeu ovirt-imageio-daemon" from ovirt03.forest.go.th.Thanks, Amit.Hi Amit,I restarted ‘overt-imageio-daemon’ service in ovirt03.forest.go.th but still can’t upload. Here is the output from ‘journalctl -xeu overt-imageio-daemon’ command in ovirt03.forest.go.th:-- Logs begin at Thu 2016-10-13 19:41:49 ICT, end at Tue 2016-11-08 17:45:20 ICT. -- Oct 25 15:04:21 ovirt03.forest.go.th systemd[1]: Starting oVirt ImageIO Daemon... -- Subject: Unit ovirt-imageio-daemon.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ovirt-imageio-daemon.service has begun starting up. Oct 25 15:04:21 ovirt03.forest.go.th systemd[1]: Started oVirt ImageIO Daemon. -- Subject: Unit ovirt-imageio-daemon.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ovirt-imageio-daemon.service has finished starting up. -- -- The start-up result is done. Nov 08 14:18:51 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - [08/Nov/2016 14:18:51] "PUT /tickets/1346bbb2-3b0a-4517-94bb-41959dba996d HTTP/1.1" 200 0 Nov 08 14:19:07 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - [08/Nov/2016 14:19:07] "DELETE /tickets/1346bbb2-3b0a-4517-94bb-41959dba996d HTTP/1.1" 204 0 Nov 08 14:42:07 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - [08/Nov/2016 14:42:07] "PUT /tickets/06a78ba7-47e1-45fd-a1eb-58058bb8d1e9 HTTP/1.1" 200 0 Nov 08 14:42:21 ovirt03.forest.go.th ovirt-imageio-daemon[13577]: / - - [08/Nov/2016 14:42:21] "DELETE /tickets/06a78ba7-47e1-45fd-a1eb-58058bb8d1e9 HTTP/1.1" 204 0 Nov 08 17:39:32 ovirt03.forest.go.th systemd[1]: Stopping oVirt ImageIO Daemon... -- Subject: Unit ovirt-imageio-daemon.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ovirt-imageio-daemon.service has begun shutting down. Nov 08 17:39:34 ovirt03.forest.go.th systemd[1]: Starting oVirt ImageIO Daemon... -- Subject: Unit ovirt-imageio-daemon.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ovirt-imageio-daemon.service has begun starting up. Nov 08 17:39:34 ovirt03.forest.go.th systemd[1]: Started oVirt ImageIO Daemon. -- Subject: Unit ovirt-imageio-daemon.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ovirt-imageio-daemon.service has finished starting up. -- -- The start-up result is done. Nov 08 17:40:30 ovirt03.forest.go.th ovirt-imageio-daemon[7486]: / - - [08/Nov/2016 17:40:30] "PUT /tickets/f4659c11-5c4d-4d63-b521-f299149c3fed HTTP/1.1" 200 0 Nov 08 17:40:50 ovirt03.forest.go.th ovirt-imageio-daemon[7486]: / - - [08/Nov/2016 17:40:50] "DELETE /tickets/f4659c11-5c4d-4d63-b521-f299149c3fed HTTP/1.1" 204 0 Thank you,Wee.___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Can't upload qcow2 images via web UI
On Tue, Nov 8, 2016 at 10:24 AM, วีร์ ศรีทิพโพธิ์wrote: > Hi, > > I’m trying to transfer one of my VM from KVM to oVirt. My understanding is > that I can upload its qcow2 to oVirt via ’Upload > Start’ in ‘Disks’ tab of > the web UI. > > However, the upload won’t start. I found this message in the events tab: > > "Unable to upload image to disk 2a2e3afc-825b-4022-b402-669731003f3a 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." > > I already installed the CA from 'https://[engine address]/ > ovirt-engine/services/pki-resource?resource=ca- > certificate=X509-PEM-CA’ and ovirt-imageio-proxy is still running. > > [root@oengine ~]# systemctl status ovirt-imageio-proxy > *●* ovirt-imageio-proxy.service - oVirt ImageIO Proxy >Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; > enabled; vendor preset: disabled) >Active: *active (running)* since Tue 2016-11-08 02:06:55 UTC; 5h 28min > ago > Main PID: 503 (ovirt-imageio-p) >CGroup: /system.slice/ovirt-imageio-proxy.service >└─503 /usr/bin/python /usr/bin/ovirt-imageio-proxy > > Please guide me in this regard, > Wee. > > oVirt Engine Version: 4.0.4.4-1.el7.centos > > Logs: > > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > Hi Wee. Looking in your logs, it looks like "ovirt-imageio-daemon" service, which runs in the oVirt's host (ovirt03.forest.go.th), doesn't accept the requests as should. Please, log into this host and restart this service, running: *service ovirt-imageio-daemon restart* And try upload. If this won't work, please send us the output of "journalctl -xeu ovirt-imageio-daemon" from ovirt03.forest.go.th . Thanks, Amit. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Can't upload qcow2 images via web UI
Hi,I’m trying to transfer one of my VM from KVM to oVirt. My understanding is that I can upload its qcow2 to oVirt via ’Upload > Start’ in ‘Disks’ tab of the web UI.However, the upload won’t start. I found this message in the events tab:"Unable to upload image to disk 2a2e3afc-825b-4022-b402-669731003f3a 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."I already installed the CA from 'https://[engine address]/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA’ and ovirt-imageio-proxy is still running.[root@oengine ~]# systemctl status ovirt-imageio-proxy● ovirt-imageio-proxy.service - oVirt ImageIO Proxy Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2016-11-08 02:06:55 UTC; 5h 28min ago Main PID: 503 (ovirt-imageio-p) CGroup: /system.slice/ovirt-imageio-proxy.service └─503 /usr/bin/python /usr/bin/ovirt-imageio-proxyPlease guide me in this regard,Wee.oVirt Engine Version: 4.0.4.4-1.el7.centosLogs: image-proxy.log Description: Binary data ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users