Bug 1956986 - [AAA] changing default suffix for users - org.ovirt.engine-extensions.aaa.misc fails to load
Summary: [AAA] changing default suffix for users - org.ovirt.engine-extensions.aaa.mis...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-extension-aaa-misc
Version: 4.4.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Martin Perina
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 19:44 UTC by Anitha Udgiri
Modified: 2021-05-05 22:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Infra
Target Upstream Version:


Attachments (Terms of Use)

Description Anitha Udgiri 2021-05-04 19:44:08 UTC
Description of problem:
After an update to RHV 4.4, org.ovirt.engine-extensions.aaa.misc fails to load when ovirt-engine is restarted.

Version-Release number of selected component (if applicable):

ovirt-engine-extension-aaa-misc-1.1.0-1.el8ev.noarch


How reproducible:

100% , Always

Steps to Reproduce:
1. Follow steps in KCS : https://access.redhat.com/solutions/2104331
2. Restart the engine.


Actual results:

After an engine restart, mapping file does not load and errors out as follows :

ERROR [org.ovirt.engine.core.sso.utils.SsoExtensionsManager] (ServerService Thread Pool -- 46) [] Could not load extension based on configuration file '/etc/ovirt-engine/extensions.d/mapping1.properties'. Please check the configuration file is valid. Exception message is: Error loading extension 'mapping1': The module 'org.ovirt.engine-extensions.aaa.misc' cannot be loaded: org.ovirt.engine-extensions.aaa.misc


Expected results:

The mapping file should be loaded to enable users in the subdomain to login

Comment 2 Martin Perina 2021-05-05 11:51:29 UTC
There was a change in aaa-extensions naming in RHV 4.4, specifically change in ovirt-engine-extension-aaa-misc is descrived in BZ1734725:

1. RHV 4.3 "org.ovirt.engine-extensions.aaa" -> RHV 4.4 "org.ovirt.engine.extension.aaa"

2. RHV 4.3 "org.ovirt.engineextensions.aaa" -> RHV 4.3 "org.ovirt.engine.extension.aaa"

RHV 4.4 documentation has been updated:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/configuring_ldap_and_kerberos_for_single_sign-on

Also as a part of upgrade from 4.3 to 4.4 we are performing above renames automatically during engine-setup (more info in BZ1814212).

Anitha, could you please update KCS https://access.redhat.com/solutions/2104331 to reflect different configuration between RHV 4.4 and RHV <= 4.3?

But looking at customer case I have below questions:

1. Did customer perform upgrade from RHV 4.3 to 4.4 and extensions configuration haven't change? If so, could we get full logs from the upgrade?

2. Did customer perform new RHV 4.4 installation and then just copied existing RHV 4.3 extensions configurations? If so, then they need to rename extensions configuration manually as mentioned in RHV docs

Comment 3 Anitha Udgiri 2021-05-05 22:05:41 UTC
(In reply to Martin Perina from comment #2)
> There was a change in aaa-extensions naming in RHV 4.4, specifically change
> in ovirt-engine-extension-aaa-misc is descrived in BZ1734725:
> 
> 1. RHV 4.3 "org.ovirt.engine-extensions.aaa" -> RHV 4.4
> "org.ovirt.engine.extension.aaa"
> 
> 2. RHV 4.3 "org.ovirt.engineextensions.aaa" -> RHV 4.3
> "org.ovirt.engine.extension.aaa"
> 
> RHV 4.4 documentation has been updated:
> 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/
> html/administration_guide/configuring_ldap_and_kerberos_for_single_sign-on
> 
> Also as a part of upgrade from 4.3 to 4.4 we are performing above renames
> automatically during engine-setup (more info in BZ1814212).
> 
> Anitha, could you please update KCS
> https://access.redhat.com/solutions/2104331 to reflect different
> configuration between RHV 4.4 and RHV <= 4.3?
> 
> But looking at customer case I have below questions:
> 
> 1. Did customer perform upgrade from RHV 4.3 to 4.4 and extensions
> configuration haven't change? If so, could we get full logs from the upgrade?
> 
> 2. Did customer perform new RHV 4.4 installation and then just copied
> existing RHV 4.3 extensions configurations? If so, then they need to rename
> extensions configuration manually as mentioned in RHV docs

Martin,

The customer has a fresh installation of 4.4 on their systems. The only change needed will be for the mapping1.properties file. I'll go ahead and modify the KCS for 4.4 environments.

Thanks,
Anitha


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