Description of problem: A non admin user tries to open the Import VM wizard, he gets an option to pick a provider with no hint that it will not work. If he pick any of the providers, the next thing what happens is that he will be presented by permission error messages with no hint that in general, as a non admin, he will not be able to open run the import. We need to prevent the user to fall into this trap. We need to either hide the import button for non admin users or we need to open the wizard but dont let him proceed from the first screen and just let him know that only admins are allowed to do this.
@Matt: I think that to be consistent with OCP, we should hide the button completely in case the user is not an admin one. Would you agree?
I'd suggest we just disable it. It would be nice in the future if we could consider adding either a tool tip or sub text that clarifies that it's disabled. Ultimately it would be good to better understand developers and their need for import generally.
clarification: the final decision was to hide the button for the current implementation
no I vote we just disabled it not hide it entirely. That should follow the convention set by the console
that is not easy to do at the moment, since it requires not so simple changes to the console core code.
also it might be convention in other places with dropdowns, but disabling is not used for create dropdowns at the moment.
I'm ok with hiding it for now. We don't have a clear direction yet on how informed developers should be on import if they can't perform it. I'd like to raise this as a larger discussion around what devs should know is possible through admin permissions.
verified on master UI, the import wizard is hiden.
*** Bug 1871109 has been marked as a duplicate of this bug. ***
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