Description of problem: "admin" username can't be used. But we are able to create such request wich will fail with : [[Azure::Armrest::BadRequestException]: The Admin Username specified is not allowed.] Message [[Azure::Armrest::BadRequestException]: The Admin Username specified is not allowed.] Version-Release number of selected component (if applicable):5.8.0.16 How reproducible:100% Steps to Reproduce: 1.use "admin" username during Instance provision on azure provider 2. 3. Actual results: Request gets created but fails Expected results: Warning message in UI
Yes, there is a list of usernames that are not allowed by Azure. Why? Not sure, must be some attempt at security. In any case, I'll add some hooks to catch those.
Part 1 here: https://github.com/ManageIQ/manageiq/pull/15513
Part 2 here: https://github.com/ManageIQ/manageiq-providers-azure/pull/88
Pretty sure it's a UI issue: https://github.com/ManageIQ/manageiq-ui-classic/issues/1630
https://github.com/ManageIQ/manageiq-ui-classic/pull/2990
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/9ebf810383c82e3b55251dd5e1ef49e4a0da77ad commit 9ebf810383c82e3b55251dd5e1ef49e4a0da77ad Author: Aparna Karve <akarve> AuthorDate: Fri Dec 8 11:30:01 2017 -0800 Commit: Aparna Karve <akarve> CommitDate: Fri Dec 8 11:31:00 2017 -0800 Fixes the vm_cloud routing for sort_template_grid https://bugzilla.redhat.com/show_bug.cgi?id=1454829 config/routes.rb | 1 + 1 file changed, 1 insertion(+)