"
Install optional extension packages if they were installed on the Red Hat Virtualization Manager 4.3 machine.
# yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc ovirt-engine-extension-logger-log4j
NOTE
The configuration for these package extensions must be manually reapplied
because they are not migrated as part of the backup and restore process.
"
In my case I had ovirt-engine-extension-aaa-ldap and ovirt-engine-extension-aaa-misc installed on 4.3.10.
So after "engine-backup --mode=restore ...." command I executed:
[root@ovmgr1 ~]# yum install ovirt-engine-extension-aaa-ldap ovirt-engine-extension-aaa-misc
Last metadata expiration check: 0:01:11 ago on Tue 06 Oct 2020 11:23:04 AM CEST.
Dependencies resolved.
==========================================================================================
Package Arch Version Repository Size
==========================================================================================
Installing:
ovirt-engine-extension-aaa-ldap noarch 1.4.1-1.el8 ovirt-4.4 127 k
ovirt-engine-extension-aaa-misc noarch 1.1.0-1.el8 ovirt-4.4 37 k
Installing dependencies:
unboundid-ldapsdk noarch 4.0.14-2.el8 ovirt-4.4-centos-ovirt44 4.0 M
Transaction Summary
==========================================================================================
Install 3 Packages
Total download size: 4.2 M
Installed size: 4.5 M
and followed the next upgrade flow steps.
After finishing the engine upgrade with the "engine-setup" step, it seems actually that I can still connect to my engine with my AD accounts, so that I don't have to do any manual step described...
Does it match any one other experience?
Gianluca