Bug 982647 – User can't see networks in DC when he has NetworkUser role on that DC.

Bug 982647 - User can't see networks in DC when he has NetworkUser role on that DC.

Summary:	User can't see networks in DC when he has NetworkUser role on that DC.

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.2.0
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	---
Target Release:	3.3.0
Assigned To:	Moti Asayag
QA Contact:	Meni Yakove
Docs Contact:

URL:
Whiteboard:	network
Keywords:	TestBlocker, Triaged, ZStream

Depends On:
Blocks:	998254
	Show dependency tree / graph

Reported:	2013-07-09 09:28 EDT by Ondra Machacek
Modified:	2016-02-10 14:57 EST (History)
CC List:	9 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Clones:	998254 (view as bug list)
Environment:
Last Closed:	2013-08-19 06:53:29 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ondra Machacek 2013-07-09 09:28:06 EDT

Description of problem:


Version-Release number of selected component (if applicable):
3.2.1-0.39.el6ev (sf18.3)

How reproducible:
100%

Steps to Reproduce:
1. Create private networks in DC.
2. Assign NetworkUser on that DC to user1.
3. As user1 check /api/networks

Actual results:
User can't see private networks.

Expected results:
User should see private networks.

Additional info:

Comment 2 Moti Asayag 2013-08-18 05:28:31 EDT

This bug is no longer relevant for 3.3 since the network usage visibility was modified to Vnic Profiles level and VnicProfileUser replaced the NetworkUser role.

Comment 4 lpeer 2013-08-18 11:59:18 EDT

I'm removing the 3.3 flag per comment#2

Note You need to log in before you can comment on or make changes to this bug.