Description of problem: When you provide a wrong oVirt user to openshift-install, the authentication with oVirt (as is to be expected) fails. However, user is prompted only to re-enter their password. And of course, even if they provide the correct password, authentication will fail again. Therefore their only option is to kill the installer and start again, which is not great UX. Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: 100 % Steps to Reproduce: https://pastebin.com/xdDWCMuB Actual results: Installer does not provide a change to input oVirt user again Expected results: When authentication fails, user should be prompted to enter both username and password again.
Jan, how about the approach below? If we fail to auth, we show to users the error and exit. INFO Detected: Engine CA as trusted locally... ? oVirt engine username admin@internal ? oVirt engine password ******** Failed to connect to oVirt platform Error during SSO authentication access_denied : Cannot authenticate user 'admin@internal': Unable to log in. Verify your login information or contact the system administrator.. Exiting....
Hi Douglas, in ideal world I'd rather see the installer prompting for username and password again. But if that proves too difficult to implement, your proposed solution works fine.
(In reply to Jan Zmeskal from comment #2) > Hi Douglas, in ideal world I'd rather see the installer prompting for > username and password again. But if that proves too difficult to implement, > your proposed solution works fine. Let's try the hard way ;-)
Hi Douglas, I basically verified this during verification of different BZ. Please see the comment here: https://bugzilla.redhat.com/show_bug.cgi?id=1814373#c19 I like the user experience much more now. The only thing I'm missing is that user does not know that they should press Ctrl+C to be able to provide username again. All they get is this: Sorry, your reply was invalid: failed to connect to Engine platform Error during SSO authentication access_denied : Cannot authenticate user 'homer@N/A': No valid profile found in credentials.. Could we also inform them in this message that they can re-enter the username by pressing Ctrl+C?
After offline agreement with Douglas, the defect described in comment 7 will be treated as a new bug, therefore moving this to VERIFIED.
Issue described in comment 7 is now tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1848987
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196