Bug 1726285 - Router which created by admin, forced creating on admin project
Summary: Router which created by admin, forced creating on admin project
Keywords:
Status: CLOSED DUPLICATE of bug 1724114
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.11.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: GA
: 5.11.0
Assignee: Marek Aufart
QA Contact: Ido Ovadia
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-02 13:40 UTC by Ido Ovadia
Modified: 2019-08-14 08:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-14 08:13:54 UTC
Category: Bug
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:
mfeifer: mirror+

Attachments (Terms of Use)

Description Ido Ovadia 2019-07-02 13:40:42 UTC 
Description of problem:
=======================
Router which created by admin does not created on selected project, but on admin 

Version-Release number of selected component:
=============================================
5.11.0.10

How reproducible:
=================
100%

Steps to Reproduce:
===================
1. Add OpenStack as cloud provider with admin credential
2. Create project A
3. As admin user create router, cloud tenant placement: project A 

Actual results:
===============
Router doesn't created on selected project (project A), but on admin

Expected results:
=================
Router should create on selected project
Comment 1 Sudhir Mallamprabhakara 2019-07-02 18:21:49 UTC 
Ido, Is this a regression??
Comment 2 Ido Ovadia 2019-07-03 13:53:54 UTC 
(In reply to Sudhir Mallamprabhakara from comment #1)
> Ido, Is this a regression??

I think so yes
Comment 3 dmetzger 2019-07-05 12:48:47 UTC 
What CFME version last worked?
Comment 4 Ido Ovadia 2019-07-31 13:15:40 UTC 
(In reply to dmetzger from comment #3)
> What CFME version last worked?

5.10, dont remember the specific build
Note You need to log in before you can comment on or make changes to this bug.