Hi, I've successfully installed OKD <= 4.8 in my ovirt 4.3 self-hosted engine setup. However, I have now found out that the imageio-proxy and/or imageio-deamon has changed it's API calls and ports to make the OKD install fail on self-hosted (all-in-one) setups on ovirt 4.4 and 4.5. Since I've upgraded to version 4.5 I can no longer install OKD with Installer Provisioned Infrastructure.
I recently read throough a long thread in bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1871348) on how to get image uploads working from the GUI but haven't found any solutions for making the OKD install work. The suggested solution, engine-config -s "EnableImageioProxy=false", didn't solve my problem. Would it be possible to tweak the setup so that the OKD installer can upload it's image through imageio? I don't use the imageio service for anything else since I (almost) only kickstart my new vm's from my foreman servers so if other use cases than the OKD install would fail I can live with that. I take it the problem only appears for a self-hosted setup. If it was possible to migrate the engine to a standalone host (not a powerful compute node but somewhere with 4vCPU and 16 GB RAM) would that make the solution easier? I would lose a lot of my current infrastructure if I had to reinstall but if I can't find a better solution I will have to. Any help would be appreciated. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/ZAV5LRB6GJJ36KGQWUJBOCBHTBBFNGTA/