Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1710659

Summary: 'Add Allowed Address Pair' button is visible to admin role
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: python-django-horizonAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED ERRATA QA Contact: Tatiana Ovchinnikova <tovchinn>
Severity: medium Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: athomas, jrist, rdopiera
Target Milestone: Upstream M3Keywords: Triaged
Target Release: 16.0 (Train on RHEL 8.1)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-django-horizon-16.1.0-0.20191120111947.338a58f.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-06 14:40:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1757102, 1757106, 1757108    

Description Keigo Noha 2019-05-16 01:38:14 UTC 
Description of problem:
'Add Allowed Address Pair' button is visible to admin role

Version-Release number of selected component (if applicable):
Current openstack dashboard.

How reproducible:
Always

Steps to Reproduce:
1. Create a project whose name is test.
2. Create a user whose name is test_user and assign _member_ role to the user.
3. Login to the dashborad with test_user then create a new private network.
4. Create a port to the private network.
5. Move the port details and click address 'Allowed address pairs' tab.
6. 'Add Allowed Address Pairs' button is not visible to test_user

Actual results:
The buttons is not visible to test_user.

Expected results:
The button is visible to the user.

Additional info:
This issue is already reported to upstream.
LP: https://bugs.launchpad.net/horizon/+bug/1794421
Comment 9 errata-xmlrpc 2020-02-06 14:40:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0283