Multiple errors while creating a new project
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Fix Committed
|
Medium
|
MOS Horizon | ||
| 5.0.x |
Won't Fix
|
Medium
|
MOS Horizon | ||
| 5.1.x |
Won't Fix
|
Medium
|
MOS Horizon | ||
| 6.0.x |
Fix Committed
|
Medium
|
MOS Horizon | ||
Bug Description
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "5.1"
api: "1.0"
build_number: "506"
build_id: "2014-09-
astute_sha: "b622d9b36dbdd1
fuellib_sha: "e3f947cc414221
ostf_sha: "1de6ed1c0b72f6
nailgun_sha: "82091e0d61f252
fuelmain_sha: "ca1b4839a70a10
BROWSER: FF 32 Linux
Steps to repro:
0. Login as 'admin'
1. Go to Admin -> Identity Panel -> Projects.
2. Create a new project. Specify name (e.g. 'test'), keep other fields unchanged.
Project created but UI shows Error: Unable to set project quotas. is shown
3. Click Modify Users next to 'test' project
4. Add user 'admin' into Project Members. Click 'Save'
2 messages are shown: Success: Modified project "test" and
Error: Modified project information and members, but unable to modify project quotas.
5. In project switch select project 'test'
The browser is forwarded to "http://
You do not have permission to access the resource:
/dashboard/admin/
Login as different user or go back to home page
"
It is expected that creating project should not lead to any errors.
| summary: |
- Improper behavior when creating new tenant + Multiple errors while creating a new project |
| Changed in mos: | |
| assignee: | nobody → MOS Horizon (mos-horizon) |
| Changed in mos: | |
| importance: | Undecided → Medium |
| Timur Sufiev (tsufiev-x) wrote | #1 |
| Timur Sufiev (tsufiev-x) wrote | #2 |
| Dmitry Borodaenko (angdraug) wrote | #3 |
| Timur Sufiev (tsufiev-x) wrote | #4 |
1) "Error: Unable to set/modify project quotas." is related to the Nova bug https:/
2) "You do not have permission to access the resource: /dashboard/admin/" is an expected behavior when one switches to the tenant where he doesn't have an 'admin' role - thus he hasn't access to 'Admin' dashboard. If, before switched from 'admin' project to 'test' one adds 'admin' role to and 'Admin' user in the 'test' project, he won't be kicked out of 'Admin' dashboard after project switching.