Bug 1284652

Summary: Insufficient permissions causes NPE in UserPortal extended
Product: [oVirt] ovirt-engine Reporter: jniederm
Component: Frontend.UserPortalAssignee: Martin Mucha <mmucha>
Status: CLOSED DUPLICATE QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: low    
Version: 4.0.0CC: alkaplan, bugs, ylavi
Target Milestone: ovirt-4.0.0-alphaFlags: ylavi: ovirt-4.0.0?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-05 12:15:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
stack_trace.txt none

Description jniederm 2015-11-23 18:53:19 UTC
Created attachment 1097823 [details]
stack_trace.txt

Description of problem:
Insufficient permission causes that callback ProfileBehavior$2, method onSuccess() is passed empty list which causes NPE at line 

managementNetworkName = Linq.findManagementNetwork(clusterNetworks).getName();

Version-Release number of selected component (if applicable):
4.0 master, commit 47337ae

How reproducible:
100%

Steps to Reproduce:
1. In webadmin: create vm with disk
2. Create template of that vm
3. Add new user grant him (only) following permissions
     * VmCreator for template created in step 2
     * VmCreator for some Cluster that is in DC that is in state 'UP'
     * VmCreator for Storage Domain the disk of the template is located at
4. In UserPortal extended: log as newly created user
5. Open New VM dialog

Actual results:
Exception is thrown to browser console, pink popup in UI

Expected results:
New VM dialog is open and/or user is notified that permissions are insufficient/set in a wrong way.

Comment 1 Alona Kaplan 2016-01-05 12:15:39 UTC

*** This bug has been marked as a duplicate of bug 1286984 ***