New object creation is failing after enabling RBAC under previously existing tenants.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.2 |
Fix Committed
|
Medium
|
Suresh Vinapamula | |||
R4.0 |
Fix Committed
|
Medium
|
Suresh Vinapamula | |||
Trunk |
Fix Committed
|
Medium
|
Suresh Vinapamula |
Bug Description
Contrail Release: 3.2.3
Problem Description:
“Create Network” operation using GUI is failing for certain tenants after enabling RBAC feature even though “virtual_network” object has been assigned “Create” rights for “_member_”.
This is only affecting tenants that existed before enabling RBAC feature. We created some new tenants and we were able to successfully create new networks using the same tenant users.
Also issue is not only tied to "virtual network" creation, any new object creation under pre-existing tenants is also experiencing the same error
This has been identified as a known limitation. Objects (including projects) created prior to enabling RBAC will not be accessible to non-admin users after RBAC is enabled. This is because the ‘onwer’ field for such objects is set to ‘service’ tenant (which is because neutron didn’t pass the tenant information correctly), making them accessible to only ‘service’ tenant.
This LP defect is for an enhancement request to fix this behavior in upcoming releases where enabling RBAC should also make ownership changes of objects accordingly under pre-existing tenants.
Current workaround is to manually change the ownership of objects including projects using "/opt/contrail/
description: | updated |
information type: | Proprietary → Private |
Changed in juniperopenstack: | |
assignee: | nobody → Suresh Vinapamula (sureshk) |
tags: | added: config |
information type: | Private → Public |
tags: | added: blocker |
Review in progress for https:/ /review. opencontrail. org/34228
Submitter: Suresh Vinapamula (<email address hidden>)