GitHub user nitin-maharana opened a pull request:
https://github.com/apache/cloudstack/pull/1258
CLOUDSTACK-9186: Root admin cannot see VPC created by Domain admin user
Issue:
=====
Root admin cannot see LB rules and Public LB IP addresses created by
domain-admin in UI therefore root admin cannot manage those.
Reproducible Steps:
================
1. Log in as a Domain-Admin account and create a VPC with vpc virtual
router as public load balancer provider
2. click on the newly created VPC -> click on the VPC tier -> click
internal LB
3. Add internal LB,
4. Logoff domain-admin and login as root admin
5. Navigate the VPC created previously and click internal LB, internal lb
is not showing up.
Same steps for Public LB IP addresses except select the correct Network
offering while creating a tier.
Expected Behaviour:
=================
Root admin should be able to manage VPC created by Domain admin user .
Actual Behaviour:
==============
Root admin cannot see VPC created by Domain admin user and hence not able
to manage it.
Fix:
===
Added the parameter listAll=true in case of Internal LB as well as Public
LB IP addresses.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nitin-maharana/CloudStack CloudStack-Nitin3
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1258.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1258
----
commit fb882aa909f52bfd5e590e967bf4e0d2b5d936e7
Author: Nitin Kumar Maharana <nitin.mahar...@gmail.com>
Date: 2015-12-18T07:53:50Z
CLOUDSTACK-9186: Root admin cannot see VPC created by Domain admin user
Added the parameter listAll=true in case of Internal LB as well as Public
LB IP addresses.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
