Bug 1250243 - launch instance not respecting picked project
launch instance not respecting picked project
Status: CLOSED UPSTREAM
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity medium
: ---
: 7.0 (Kilo)
Assigned To: Masco
Ido Ovadia
: ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-04 15:51 EDT by Jon Schlueter
Modified: 2016-04-08 07:21 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-08 04:24:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1481469 None None None Never

  None (edit)
Description Jon Schlueter 2015-08-04 15:51:29 EDT
Description of problem: 

If you have a user with more than one project and admin role on one of the projects you get an additional pane when launching an instance.  If you pick a project to launch under that isn't the current active project and try to launch a new instance the instance is launched under the current project not the selected project.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Have a user with 2 projects and an admin role on one of the projects
2. log in as that user
3. identity -> projects -> set as active (project with admin role)
4. project -> instances -> Launch Instance -> Projects & Users -> Select non active project
5. Launch Instance (simple instance is fine)

Actual results:
Instance launched within current project


Expected results:
Instance launched within requested project

Additional info:

python-django-horizon-2015.1.0-10.el7ost.noarch (OSP7 GA release)
Comment 3 Matthias Runge 2016-04-08 04:24:32 EDT
Unfortunately, this is hard to reproduce and thus, we can not agree upstream that this bug is really fixed. Please re-open, if there's a reproducer
Comment 4 Jon Schlueter 2016-04-08 07:21:16 EDT
I'll follow up with upstream launchpad then, and test with Mitaka release to see if it still happens

Note You need to log in before you can comment on or make changes to this bug.