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

Bug 1757108

Summary:	'Add Allowed Address Pair' button is visible to admin role [osp13]
Product:	Red Hat OpenStack	Reporter:	Radomir Dopieralski <rdopiera>
Component:	python-django-horizon	Assignee:	Radomir Dopieralski <rdopiera>
Status:	CLOSED ERRATA	QA Contact:	Radomir Dopieralski <rdopiera>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	athomas, jrist, knoha, rdopiera, rhos-maint
Target Milestone:	---	Keywords:	Reopened, Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-django-horizon-13.0.2-6.el7ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-10 11:25:01 UTC	Type:	---
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:	1710659
Bug Blocks:

Description Radomir Dopieralski 2019-09-30 15:06:04 UTC

This bug was initially created as a copy of Bug #1710659

I am copying this bug because: backport



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 1 Keigo Noha 2019-10-23 02:55:46 UTC

Hi Radomir,

In upstream, stable/queens branch merged the proposed fix into the repository.
Would we include the fix into RHOSP13 tree? Is it possible to ship the fix into RHOSP13z9?

Thank you,
Keigo Noha

Comment 11 errata-xmlrpc 2020-03-10 11:25:01 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/RHBA-2020:0763