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.

There is one machine running the ovirt engine and there are 2 additional hosts. The OS on the machines is Centos 8.

Thank you, Tim _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org 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/users@ovirt.org/message/GWIVRHYHNGUVJ NSQTYCDQBOG6VFXCZPB/

> On 12. Oct 2020, at 12:15, Vojtech Juranek <vjuranek(a)redhat.com&gt; wrote: > > On pátek 9. října 2020 19:02:32 CEST tim-nospam--- via Users 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. > > what is exact version of imageio? (rpm -qa|grep imageio) # rpm -qa|grep imageio ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch ovirt-imageio-daemon-2.0.10-1.el8.x86_64 ovirt-imageio-common-2.0.10-1.el8.x86_64 ovirt-imageio-client-2.0.10-1.el8.x86_64 > On which port imageio listens? You can use e.g. netstat etc. Also plase > check imageio logs (/var/log/ovirt-imageio/daemon.log), what is there, > there shold > be something like this: # netstat -tulpn | grep 543 tcp 0 0 0.0.0.0:54322 0.0.0.0:* LISTEN 2527872/platform-py tcp 0 0 127.0.0.1:54324 0.0.0.0:* LISTEN 2527872/platform-py > 2020-10-08 08:37:48,906 INFO (MainThread) [services] remote.service > listening on ('::', 54323) 2020-10-09 17:46:38,216 INFO (MainThread) [server] Starting (pid=2527872, version=2.0.10) 2020-10-09 17:46:38,220 INFO (MainThread) [services] remote.service listening on ('0.0.0.0', 54322) 2020-10-09 17:46:38,221 INFO (MainThread) [services] control.service listening on ('127.0.0.1', 54324) 2020-10-09 17:46:38,227 INFO (MainThread) [server] Ready for requests No entries for Port 54323 in the last 3 months. I found logentries in july though: [root@helios ~]# cat /var/log/ovirt-imageio/daemon.log | grep 54323 2020-07-11 10:13:24,777 INFO (MainThread) [services] remote.service listening on ('::', 54323) [...] 2020-07-16 19:54:13,398 INFO (MainThread) [services] remote.service listening on ('::', 54323) 2020-07-16 19:54:36,715 INFO (MainThread) [services] remote.service listening on ('::', 54323) > Also, please check if there are any other config files (*.conf) in > /etc/ovirt- imageio/conf.d or in /usr/lib/ovirt-imageio/conf.d I have, but I couldn't find anything interesting in those two files: # 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

The imageio daemon should listen on Port 54323: # /etc/ovirt-imageio/conf.d/50-engine.conf [...] [remote] # Port cannot be changed as it's currently hardcoded in engine code. port = 54323 [...] >> There is one machine running the ovirt >> engine and there are 2 additional hosts. The OS on the machines is Centos >> 8. >> >> >> >> >> Thank you, >> Tim >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> 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/users@ovirt.org/message/GWIVRHYHNGU >> VJ >> NSQTYCDQBOG6VFXCZPB/

> On 13. Oct 2020, at 10:01, Vojtech Juranek <vjuranek(a)redhat.com&gt; wrote: > > On úterý 13. října 2020 9:37:11 CEST Tim Bordemann wrote: >>> On 12. Oct 2020, at 12:15, Vojtech Juranek <vjuranek(a)redhat.com&gt; wrote: >>> >>> On pátek 9. října 2020 19:02:32 CEST tim-nospam--- via Users 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. >>> >>> what is exact version of imageio? (rpm -qa|grep imageio) >> >> # rpm -qa|grep imageio >> ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch >> ovirt-imageio-daemon-2.0.10-1.el8.x86_64 >> ovirt-imageio-common-2.0.10-1.el8.x86_64 >> ovirt-imageio-client-2.0.10-1.el8.x86_64 >> >>> On which port imageio listens? You can use e.g. netstat etc. Also plase >>> check imageio logs (/var/log/ovirt-imageio/daemon.log), what is there, >>> there shold >>> be something like this: >> # netstat -tulpn | grep 543 >> tcp 0 0 0.0.0.0:54322 0.0.0.0:* LISTEN >> 2527872/platform-py tcp 0 0 127.0.0.1:54324 >> 0.0.0.0:* LISTEN 2527872/platform-py >>> 2020-10-08 08:37:48,906 INFO (MainThread) [services] remote.service >>> listening on ('::', 54323) >> >> 2020-10-09 17:46:38,216 INFO (MainThread) [server] Starting (pid=2527872, >> version=2.0.10) 2020-10-09 17:46:38,220 INFO (MainThread) [services] >> remote.service listening on ('0.0.0.0', 54322) 2020-10-09 17:46:38,221 INFO >> (MainThread) [services] control.service listening on ('127.0.0.1', >> 54324) 2020-10-09 17:46:38,227 INFO (MainThread) [server] Ready for >> requests >> >> No entries for Port 54323 in the last 3 months. I found logentries in july >> though: >> >> [root@helios ~]# cat /var/log/ovirt-imageio/daemon.log | grep 54323 >> 2020-07-11 10:13:24,777 INFO (MainThread) [services] remote.service >> listening on ('::', 54323) [...] >> 2020-07-16 19:54:13,398 INFO (MainThread) [services] remote.service >> listening on ('::', 54323) 2020-07-16 19:54:36,715 INFO (MainThread) >> [services] remote.service listening on ('::', 54323) >>> Also, please check if there are any other config files (*.conf) in >>> /etc/ovirt- imageio/conf.d or in /usr/lib/ovirt-imageio/conf.d >> >> I have, but I couldn't find anything interesting in those two files: >> >> # 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 > > 50-vdsm.conf overwrites 50-engine.conf (later config taken alphabetically overwrites previous config if there is any). > > If you don't use engine as a host at the same time, stop an uninstall vdsm from engine (should remove also 50-vdsm.conf) and restart ovirt-imageio service. > > If you use engine as a host at the same time, note that this is unsupported. However, there were some patches in this area recently, but they are not released yet AFAICT. See [1, 2] for more details. > > [1] https://bugzilla.redhat.com/1871348 > [2] https://lists.ovirt.org/archives/list/users@ovirt.org/thread/W4OTINLXYDWG... Uninstalling vdsm would also remove nearly 500 packages on the machine. I have disabled and masked the vdsm service for now and restarted the imageio service. Uploading an image via the webui now works again. I will remove vdsm during a maintainence window and maybe even reinstall the machine completely.

On 12. Oct 2020, at 13:56, Nir Soffer <nsoffer(a)redhat.com&gt; wrote: On Sun, Oct 11, 2020, 11:58 tim-nospam--- via Users <users(a)ovirt.org&gt; 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?

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?

If you used engine host as hypervisor in the past, you will have vdsm configuration (60-vdsm.conf) overriding engine configuration.

Nir Thank you, Tim _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org 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/users@ovirt.org/message/GWIVRHYHNGU...