by standalone do you mean all-in-one? or separate engine and hosts?
I THINK all-in-one. :)
The following are the commands that I ran:
sudo yum install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
sudo yum module -y enable javapackages-tools pki-deps postgresql:12
sudo yum install ovirt-engine
sudo engine-setup
sudo mkdir -p /data/images
sudo mkdir /data/iso
sudo chown 36:36 /data/iso
sudo chmod 0755 /data/iso
In 4.4 the change in imageio means it's not compatible with
all-in-one anymore.
Yes, in reading through your recent email thread here, that's what I picked up on.
I was pretty sure that I hit the same bug, but wasn't positive.
So, what's the point of all-in-one if you cannot upload ISOs and boot VMs off of
ISOs?
Is there an alternative way to setup a VM in all-in-one, such as boot from PXE or
something?
Regardless, the all-in-one setup was just for learning purposes.
I may try a different install approach, and try to get the self-hosted engine working.
That said, I'm still unclear on the exact differences between the "self-hosted
engine" and the standalone Manager. I'll go re-read earlier responses to my
questions on that, as well as the glossary of sorts that Didi was so kind to write in your
earlier thread on the imageio issue.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, August 22, 2020 7:49 AM, Michael Jones <mj(a)mikejonesey.co.uk> wrote:
I see you are using 4.4 standalone;
by standalone do you mean all-in-one? or separate engine and hosts?
In 4.4 the change in imageio means it's not compatible with
all-in-one
anymore, i'll be raising a bug request to support this later today (but
officially all-in-one support ended in 4.0 so i don't know if the bug
will be actioned).
Kind Regards,
Mike
On 22/08/2020 12:06, David White via Users wrote:
> Ok, that at least got the certificate trusted.
> Thank you for the fast response on that!
> The certificate is now installed and trusted, and I removed the exception in
Firefox.
> (Screenshots attached)
> Unfortunately, the upload is still not working.
> I'm still getting the same error message that "Connection to
ovirt-imageio-proxy service has failed."