Description of problem: content of /etc/ovirt-engine/extensions.d/*properties files was updated from various formats to 'org.ovirt.extension.(aaa|misc)[.something]'. Users need to be notified of this change so that LDAP/SSO authentication won't be broken by this change Version-Release number of selected component (if applicable): 4.4.0-24 build How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: when deploying from example files in /usr/share/ovirt-engine-extension-aaa-ldap/examples/*, there is no issue. Problem is when these files are used separately such as in Ondra's role: https://github.com/machacekondra/ansible-role-ovirt-aaa-ldap (issue: https://github.com/machacekondra/ansible-role-ovirt-aaa-ldap/issues/6 )
Configurations files of oVirt engine extensions has been changed in 4.4 as described in BZ1734720, BZ1734724, BZ1734725 and BZ1734727, so engine-setup should automatically convert those configurations to 4.4 format
Verified in ovirt-engine-4.4.1.8-0.7.el8ev engine-setup converts the old *.properties files to the newer format, for example: org.ovirt.engine-extensions.aaa.ldap -> org.ovirt.engine.extension.aaa.ldap
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.