Bug 924201 - Cannot Create New VM due to Custom Property value not set properly
Summary: Cannot Create New VM due to Custom Property value not set properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: All
OS: Linux
urgent
high
Target Milestone: ---
: 3.3
Assignee: Gilad Chaplik
QA Contact: Martin Pavlik
URL:
Whiteboard: virt
: 949858 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-21 11:02 UTC by Deepak C Shetty
Modified: 2016-04-18 10:40 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-23 12:15:37 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
Zip has 4 .pngs as referenced in the desc. (94.18 KB, application/zip)
2013-03-21 11:02 UTC, Deepak C Shetty
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 13304 0 None None None Never
oVirt gerrit 13748 0 None None None Never

Description Deepak C Shetty 2013-03-21 11:02:03 UTC
Created attachment 713770 [details]
Zip has 4 .pngs as referenced in the desc.

Description of problem:
Attached 4 .png snapshots .. pls see them in sequence {1, 2, 3, 4}.png

When i try to create a new VM and click on i get error as depicted in 2.png.
The only way to get around that is to go to custom prop tab, click on '+' to add another combo, select "No available keys" from the drop down, which then changes both the combos to "Pls select a key..." and now creatign new VM works without the error seen in 2.png.


Version-Release number of selected component (if applicable):
I am using latest git version of engine. I haven't used RPM install of engine.

How reproducible:
Always

Steps to Reproduce:
See above
1.
2.
3.
  
Actual results:
Unable to create a new VM. it throws some unrelated error of custom property!

Expected results:
Should be able to create a VM, w/o touchign anything but the main tab.

Additional info:

Comment 1 Gilad Chaplik 2013-03-24 08:08:44 UTC
Hi Deepak, 
Do you have any properties populated in the drop down (or just "Pls select a key...")?
Thanks, Gilad.

Comment 2 Gilad Chaplik 2013-03-24 12:58:48 UTC
(In reply to comment #1)
> Hi Deepak, 
> Do you have any properties populated in the drop down (or just "Pls select a
> key...")?
> Thanks, Gilad.

Tested it out, probably the answer is yes :-)

Comment 3 Deepak C Shetty 2013-03-26 07:54:15 UTC
Sorry, didn't see this earlier.
I am starting from a clean slate and its the first time ever i am creating a VM.
So i cannot have any properties in the drop down except "Pls select a key..". I haven't created any custom property.. so there can't be anything in the drop down.

Comment 4 DHC 2013-04-04 17:54:50 UTC
I can also confirm this from a fresh build of engine from master as of this morning.

from engine log:
2013-04-04 12:39:44,123 WARN  [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (ajp--127.0.0.1-8702-9) [3648fc67] CanDoAction of action AddVmFromScratch failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_CUSTOM_VM_PROPERTIES_INVALID_SYNTAX

vdsm has hooks installed on the hosts but nothing has been added to the engine custom properties wise, everything a clean slate

- DHC

Comment 5 Martin Pavlik 2013-04-09 08:18:50 UTC
*** Bug 949858 has been marked as a duplicate of this bug. ***

Comment 6 Gilad Chaplik 2013-04-09 14:07:03 UTC
After further investigation, vdc_option properties for version 3.3 were missing. Note that this may cause several issues and regressions.
Thanks.

Comment 7 Itamar Heim 2013-08-21 16:40:48 UTC
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 8 Martin Pavlik 2013-09-19 12:38:35 UTC
works in  oVirt Engine Version: 3.4.0-0.2.master.20130918140617.git54da2f7.fc19

Comment 9 Itamar Heim 2013-09-23 12:15:37 UTC
bulk closing, assuming verified bugs are in 3.3.


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