Description of problem: The procedure for upgrading the engine VM from 3.6/el6 -> 4.0/el7 requires API access but it hardcodes the login as admin@internal while the user could also disable it on the engine. So let's always ask an administrative login and not just the password proposing admin@internal as the default Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. disable admin@internal on 3.6 engine 2. try upgrading the engine VM from 3.6/el6 -> 4.0/el7 3. Actual results: it requires admin@internal Expected results: It asks a different administrative user Additional info:
Verified on ovirt-hosted-engine-setup-2.1.3-1.el7ev.noarch [ INFO ] Connecting to the Engine [ ERROR ] The engine API didnt accepted the administrator password you provided Please enter it again to retry. Enter engine admin username [admin@internal]: admin@internal Enter engine admin password: [ INFO ] Connecting to the Engine [ INFO ] Connecting to the Engine [ INFO ] Waiting for the host to become operational in the engine. This may take several minutes...
Byron - it's the other way around. It used to always use admin@internal, now it does not always use that - instead it prompts also for the username (and defaults to admin@internal).