Multiple errors while creating a new project

Bug #1368258 reported by Ilya Shakhat
6
This bug affects 1 person
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-10_00-01-12"
  astute_sha: "b622d9b36dbdd1e03b282b9ee5b7435ba649e711"
  fuellib_sha: "e3f947cc4142210499a282bc5f183c333552fa23"
  ostf_sha: "1de6ed1c0b72f6687ffb4bebc2c939b135a88e34"
  nailgun_sha: "82091e0d61f252619a0842d0f8debb6b602a61fe"
  fuelmain_sha: "ca1b4839a70a10041f8eaf8b9ac995c8b0d4521a"

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://172.16.44.50/dashboard/auth/login/?next=/dashboard/admin/" which is login screen with error: "
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.

Tags: horizon
Ilya Shakhat (shakhat)
summary: - Improper behavior when creating new tenant
+ Multiple errors while creating a new project
Igor Marnat (imarnat)
Changed in mos:
assignee: nobody → MOS Horizon (mos-horizon)
Changed in mos:
importance: Undecided → Medium
Revision history for this message
Timur Sufiev (tsufiev-x) wrote :

1) "Error: Unable to set/modify project quotas." is related to the Nova bug https://bugs.launchpad.net/mos/+bug/1332457/ - and will be fixed in Horizon as soon as Nova provides some means to detect whether quotas are enabled or not
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.

Revision history for this message
Timur Sufiev (tsufiev-x) wrote :

I propose to use this bug for tracking a Horizon UX fix which aims to prevent modifying Nova quotas for a project in Dashboard if quotas extension in Nova is disabled. I will be able to provide the fix when https://bugs.launchpad.net/mos/+bug/1332457/ is fixed (because I don't know for sure how Nova quotas extension should be disabled).

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Bug is targeted for 5.x but not High or Critical priority.

Also, bug description must be fixed: non-specific bugs "feature isn't working" are harmful, every specific error or failure that prevents a feature from working must be filed as a separate bug. Pick most critical of those problems and narrow down bug description. Create separate bugs for other problems.

Revision history for this message
Timur Sufiev (tsufiev-x) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.