On Wed, May 11, 2022 at 1:29 AM <louisb@ameritech.net> wrote:
Made the suggestion that you made earlier I continued to get the same results. Sharing the files/things you requested below:
ovirt-imageio --show-config
...
"control": { "port": 54324, "prefer_ipv4": true, "remove_timeout": 60, "socket": "/run/ovirt-imageio/sock", "transport": "unix" },
So your ovirt-imageio service is configured for vdsm. This confirms that your engine host is also used a hypervisor (all-in-one deprecated configuration). ...
}, "remote": { "host": "::", "port": 54322 },
Since the ovirt-imageio service listen on port 54322, engine UI should not try to connect to the proxy (port 54323). This is done by disabling the proxy as I explained in the previous email.
"tls": { "ca_file": "/etc/pki/vdsm/certs/cacert.pem", "cert_file": "/etc/pki/vdsm/certs/vdsmcert.pem", "enable": true, "enable_tls1_1": false, "key_file": "/etc/pki/vdsm/keys/vdsmkey.pem" } }
Using vdsm pki, works for all-in-one setup. Did you run engine-config as root? Did you restart ovirt-engine after disabling the proxy? Just to be sure - do this and share the output: sudo engine-config -s ImageTransferProxyEnabled=false sudo engine-config -g ImageTransferProxyEnabled sudo systemctl restart ovirt-engine engine-config should report: ImageTransferProxyEnabled: false version: general After the engine is restarted, try the "Test connection" again from the upload UI. If it works, upload should also work. If not, we will have to dig deeper. Nir