Hide Forgot
Description of problem: There's no check for legacy kerberos/ldap directory intergration and thus migration fails almost in the end. This is annoying, I spent an hour while waiting for 'dd', 'qemu-img convert' to finish and such thing caused failure. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.0.1.4-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. have 3.6 with legacy kerberos/ldap directory intergration 2. hosted-engine --upgrade-appliance 3. Actual results: time spent and it fails in the end Expected results: setup obviously does not do enough checks before it runs real action and thus fails almost in the end (again) Additional info:
Can be problematic if legacy kerberos/ldap directory servers run as VMs and were shutted down during this migration process :/ Thus another rollback-upgrade, start IPA and AD, and then I would try to use https://github.com/machacekondra/ovirt-engine-kerbldap-migration
(In reply to Jiri Belka from comment #0) > Description of problem: > > There's no check for legacy kerberos/ldap directory intergration and thus > migration fails almost in the end. From engine-setup's POV, it fails right when it should have failed, during stage "Validation". From appliance upgrade tool POV, this is indeed late into the game. Perhaps we should allow asking the user whether to try running engine-setup again, after the user hopefully manually fixes things.
We should add this validation before we start appliance upgrade like other checks we do.
(In reply to Yaniv Dary from comment #4) > We should add this validation before we start appliance upgrade like other > checks we do. We ask the user to manually backup the engine and provide the backup file. Then we do some verification on this backup file. We can add something there for current bug. If we find there a new aaa setup, fine. Otherwise we should probably tell the user to manually handle this (upgrade to new aaa), backup again and provide new backup. This will not save all of the spent time but some of it. We can also provide a new, unrelated tool which we didn't introduce so far, say "check-migration-to-4.0-readiness" to run on the engine (not host). Either package in 3.6.9 or provide it as an independent tool to be copied and ran. Such a tool can also help bug 1368589 and similar stuff.
Didi please work with Simone on this.
ok, ovirt-hosted-engine-setup-2.0.2.2-2.el7ev.noarch ... [ INFO ] Connecting to the Engine [ ERROR ] ['ad-w2k8r2.example.com']: such AAA domains are still configured in a deprecated way that is not compatible with the current release; please upgrade them to ovirt-engine-extension mechanism before proceeding. [ ERROR ] Failed to execute stage 'Environment customization': Unsupported AAA mechanism [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine upgrade failed Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20160916161859-1x9wnl.log