Bug 1814212 - Convert existing oVirt engine extensions configuration files to the new content required by oVirt engine 4.4
Summary: Convert existing oVirt engine extensions configuration files to the new conte...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.4.1
: 4.4.1.4
Assignee: Martin Perina
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-17 11:40 UTC by David Jaša
Modified: 2020-08-05 06:25 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.4.1.4
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-05 06:25:29 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+
mperina: blocker?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 109659 0 master MERGED core: Align package naming of internal-builtin extension 2020-10-20 11:22:58 UTC
oVirt gerrit 109660 0 master MERGED setup: Converts extensions configuration from 4.3 to 4.4 2020-10-20 11:22:58 UTC

Description David Jaša 2020-03-17 11:40:16 UTC
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 )

Comment 1 Martin Perina 2020-06-15 07:13:48 UTC
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

Comment 2 Pavel Novotny 2020-07-15 21:57:21 UTC
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

Comment 3 Sandro Bonazzola 2020-08-05 06:25:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.