Bug 1063704

Summary: Unable to create VM pools from UI when only Blank template is available
Product: [oVirt] ovirt-engine Reporter: Eli Mesika <emesika>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: bugs <bugs>
Severity: low Docs Contact:
Priority: low    
Version: ---CC: bugs, emesika, gklein, mgoldboi, michal.skrivanek, rbalakri, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-10 10:38:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Eli Mesika 2014-02-11 09:58:27 UTC 
Description of problem:

Try to create a new VM pool from the POOLs webadmin TAB , all fields are disabled 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Try to create a new VM poold from web admin 
2.
3.

Actual results:
No option to create a new pool from webadmin

Expected results:
We should be able to create VM pools from webadmin 

Additional info:
Comment 1 Eli Mesika 2014-02-11 09:59:39 UTC 
Created attachment 861731 [details]
Screenshot
Comment 2 Eli Mesika 2014-02-11 12:06:53 UTC 
This occurs only when the only template available is the Blank template
Comment 3 Eli Mesika 2014-02-11 12:17:32 UTC 
Now I see that when I am adding additional template , all is enabled , but when I try to create a pool from Blank Template I got a message that I am not allowed to create a pool from Blank template.

So, 

1) if this is how it should behave , please change this BZ to give a clear message once the New VM Pool is opened when you have just a Blank template and not just disable all the fields 

2) If Blank template can not be used in VM Pool please remove it from the displayed template list and not enable to select it and give an error message that it can not be used
Comment 4 Itamar Heim 2014-02-16 08:23:15 UTC 
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.
Comment 5 Michal Skrivanek 2014-08-22 14:26:14 UTC 
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know
Comment 6 Michal Skrivanek 2015-08-05 12:48:08 UTC 
this low prio bug didn't make it for 3.6 beta cutoff, moving to 4.0
Comment 7 Sandro Bonazzola 2015-09-04 08:58:31 UTC 
This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.
Comment 8 Eli Mesika 2015-09-06 08:04:45 UTC 
Target version already updated to 4.0
Comment 9 Red Hat Bugzilla Rules Engine 2015-10-19 11:01:08 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 10 Yaniv Kaul 2016-03-10 10:38:23 UTC 
Closing old tickets, in medium/low severity. If you believe it should be re-opened, please do so and add justification.