Il giorno ven 4 dic 2020 alle ore 18:15 Artur Socha <asocha@redhat.com> ha scritto:

Hi, 

I am working at the moment on the migration of Ovirt Engine to Wildfly 21.

I have encountered an issue with the http-remoting-connector which uses the 'default' connector. After the switch to Wildfly 21 this is no longer working. There is an error in server.log complaining about this service not being started ... however, I have not noticed that anything from the engine's core functionality is broken. There are even OST passing with this error.

Does anyone know about any usages of remoting components in ovirt engine?  Perhaps this could be removed as 'dead' configuration?

I'm only guessing, I have no real knowledge that can support this. But I guess it may be related to ovirt-scheduler-proxy or ovirt-optimizer.

 

Assuming, it is being used  - I have a patch that seems to fix the problem [1]. The thing is that I still don't understand why this change is now required. 'Default'  in reference configuration ie. standalone-full.xml is just http with redirect to https.

Any help much appreciated.

[1] https://gerrit.ovirt.org/#/c/ovirt-engine/+/112505/

--

Artur Socha
Senior Software Engineer, RHV
Red Hat

_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@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/devel@ovirt.org/message/L2ZHNKXT7YLCK6JEZBXQF3FBVIRYQ2AL/

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.