Created attachment 1056667 [details] Show's adding the admin user and admin privs, also error that project isn't specified. Description of problem: Currently to be able to create VM instances, you must be logged into Horizon under a project as a User, not Admin. If that User has Admin privs or if you have the Admin user as a member, you cannot create an instance. You get an error that a project must be provided. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. In Horizon, log in as Admin and create a new project, testproj 2. Create a new user, testuser as an admin 3. Log in as testuser and try to create an instance Actual results: Get error that a project must be specified, yet there is no project in the dropdown list and it won't allow you to enter anything in the project field. Expected results: Should be able to create an instance Additional info:
I'm unable to reproduce this. When I add created user to created project, I am able to select project in form and hence spawn instance as created user.
Let Benny deploy latest OSP7 using automation on futureville stamp and see if he can reproduce it. If yes, then Martin can access futureville stamp to see what is going on.
I had a similar report from Ido re: reproducibility. If we are able to reproduce it in the futureville stamp let's start gathering config differences and see what we find.
(In reply to Mike Orazi from comment #5) > I had a similar report from Ido re: reproducibility. If we are able to > reproduce it in the futureville stamp let's start gathering config > differences and see what we find. I'm unable to reproduce this bug. I tested it on last two builds
Possible duplicate of this: https://bugzilla.redhat.com/show_bug.cgi?id=1236620
*** This bug has been marked as a duplicate of bug 1236620 ***