Description of problem: cloud init can be used to set passwords in guests. The UI should provide a hint to the user that a password was (likely) set using cloud init and should give the user the ability to see the password in the ui Version-Release number of selected component (if applicable): 2.4.0 How reproducible: Steps to Reproduce: 1. Set a password in cloud init 2. Try to find th epassword from the UI 3. Actual results: yaml needs to be read to find password Expected results: UI gives me a way to disover the password Additional info: We gareed that parsing cloud initi is not good. OTOH this is needed for the fix of bug 1874403. What we could do: We start with an UI to display passwords, but have different sources for this. Now cloud init, in future an API which is getting implemnted to set passwords (for different access modes, i.e. ssh) IOW there will be an api which supports setting different access credentials. Today we could start working on such a UI and in future use this to be implemented api
follow up questions: If I understand this correctly - we could display the (likely) password in the UI. Would the console page be the best place for this? It could also be the details page - thinking through where different users would go to find this. We will also need a message around it not being 100% successful and if it doesn't work see the YAML file for the password?
I vote for console page, then user don't need to switch tab to find the password for login.
also vote for console page
Console page would also be fine for me for this bug, but a few notes: 1. The API we are working on will allow us to set several access credentials (SSH, windows [possibly], local [this]) Thus we might want to have in future, on the details tab "Display access credentials" 2. Not display passwords by default, but require a click In order to avoid that somebody sees the password (could be personal) when looking over a users shoulder
ok thanks please see this design for the suggestion https://xd.adobe.com/view/d972d192-59b8-41fe-8ece-7ce9b3e3a71f-8c21/ I suggested the details but maybe as an additional place this would surface in the future.
> If the "user" is not set, the username and the password is the same. This is not correct behavior, if the user is not set, leave the username blank. #cloud-config password: fedora123 chpasswd: { expire: False } For example when above cloud-init data is provided, user can login with fedora/fedora123, but not fedora123/fedora123.
interesting. So, instead of blank I'd say something like "default user for your operating system". @Matt, WDYT?
I think stating "No username set, see operating system documentation for the default username" is most helpful
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