On Mon, Nov 14, 2016 at 5:04 AM, วีร์ ศรีทิพโพธิ์ <wee.s(a)forest.go.th>
wrote:
I just opened port 54322 for ovirt03.forest.go.th and the error
message
disappear. However, the status is always ‘Locked’ and no network activity
was detected from the browser
You mean, you are trying to upload, and the new generated disk is locked?
and nothing happens from that point?
Can you please attach engine logs?
Nothing new from journalctl -xeu ovirt-imageio-daemon and image-proxy.log at
all.
On Nov 8, 2559 BE, at 22:22, Amit Aviram <aaviram(a)redhat.com> wrote:
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?