> On 12. Oct 2020, at 13:56, Nir Soffer <[email protected]> wrote: > > > > On Sun, Oct 11, 2020, 11:58 tim-nospam--- via Users <[email protected]> wrote: > Hello. > > After an upgrade I am not able to upload images anymore via the ovirt ui. > When testing the connection, I always get the error message "Connection to > ovirt-imageio-proxy service has failed. Make sure the service is installed, > configured, and ovirt-engine certificate is registered as a valid CA in the > browser.". > > I found out that the imageio daemon doesn't listen on port 54323 anymore, so > the browser can not connect to it. The daemon is configured to listen on port > 54323 though: > > # cat /etc/ovirt-imageio/conf.d/50-engine.conf > [...] > [remote] > port = 54323 > [...] > > The imageio daemon has been started successfully on the engine host as well > as on the other hosts. > > I am currently stuck, what should I do next? > The ovirt version I am using is 4.4. > > 4.4 is not specific enough, can you share complete packages versions?
Sure. The list of installed ovirt packages is quite long, I hope the shortened list is enough though. # rpm -qa | grep ovirt- ovirt-openvswitch-ovn-common-2.11-0.2020061801.el8.noarch ovirt-hosted-engine-setup-2.4.6-1.el8.noarch ovirt-openvswitch-2.11-0.2020061801.el8.noarch ovirt-engine-metrics-1.4.1.1-1.el8.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch ovirt-engine-tools-backup-4.4.1.8-1.el8.noarch ovirt-ansible-repositories-1.2.5-1.el8.noarch ovirt-engine-dwh-setup-4.4.2.1-1.el8.noarch ovirt-engine-setup-plugin-cinderlib-4.4.2.6-1.el8.noarch ovirt-engine-extension-aaa-jdbc-1.2.0-1.el8.noarch ovirt-engine-dbscripts-4.4.1.8-1.el8.noarch ovirt-engine-tools-4.4.1.8-1.el8.noarch ovirt-engine-setup-4.4.2.6-1.el8.noarch [...] > There is one machine running the ovirt engine and there are 2 additional > hosts. The OS on the machines is Centos 8. > > Do you use engine host as another hypervisor or it only use for engine? I don't use the ovirt engine as a hypervisor. > If you used engine host as hypervisor in the past, you will have vdsm > configuration (60-vdsm.conf) overriding engine configuration. So vdsm shouldn't be running on the engine host? Even though I didn't intend to configure the engine host as a hypvervisor, there is vdsm running on it and there is also a config file in the imageio config folder: # ls -l /etc/ovirt-imageio/conf.d/ total 8 -rw-r--r--. 1 root root 1458 Oct 9 17:54 50-engine.conf -rw-r--r--. 1 root root 1014 Sep 15 11:16 50-vdsm.conf > Nir > > > Thank you, > Tim > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/GWIVRHYHNGUVJNSQTYCDQBOG6VFXCZPB/ _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/6JRNR5MDCDDTTF3LPBUPC2AHDWNO5JRC/
