Bug 1339668 - can not create Vm in userportal
Summary: can not create Vm in userportal
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.UserPortal
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Tomas Jelinek
QA Contact: Pavel Novotny
URL:
Whiteboard:
: 1340033 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-25 14:36 UTC by Tomas Jelinek
Modified: 2016-08-07 22:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
This update fixes an exception error in the New Virtual Machine window in the User Portal that prevented a user from creating a new virtual machine.
Clone Of:
Environment:
Last Closed: 2016-07-05 07:52:31 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.0.0+
rule-engine: blocker+
rule-engine: planning_ack+
tjelinek: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 58074 0 master MERGED userportal: GetAllMigrationPolicies user query 2016-05-26 11:55:57 UTC
oVirt gerrit 58132 0 ovirt-engine-4.0 MERGED userportal: GetAllMigrationPolicies user query 2016-05-26 14:11:34 UTC

Description Tomas Jelinek 2016-05-25 14:36:17 UTC 
In user portal, when creating a new VM an NPE is thrown due to un-inited migrationPolicies.

Steps to reproduce:
- in user portal click new VM
- give a name
- press ok
Comment 1 Nisim Simsolo 2016-05-26 14:29:36 UTC 
*** Bug 1340033 has been marked as a duplicate of this bug. ***
Comment 2 Pavel Novotny 2016-06-24 10:27:59 UTC 
Verified in
ovirt-engine-userportal-4.0.0.6-0.1.el7ev.noarch
rhevm-4.0.0.6-0.1.el7ev.noarch (4.0.0-19)

Verified according to reproducer from comment 1.
VM creation work correctly, no errors/warnings found in engine.log or ui.log.
Comment 3 Sandro Bonazzola 2016-07-05 07:52:31 UTC 
oVirt 4.0.0 has been released, closing current release.
Note You need to log in before you can comment on or make changes to this bug.