Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 888396

Summary:	Edit pool - Prestarted VMs - slowdown
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	ovirt-engine	Assignee:	Arik <ahadas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Belka <jbelka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	ahadas, dyasny, hateya, iheim, lpeer, ofrenkel, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone:	---
Target Release:	3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	sf7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	915537

Description Jiri Belka 2012-12-18 16:08:35 UTC

Description of problem:

When creating new pool, waiting a while so VMs are created, editing pool to define number of prestarted VMs, then it takes some time to make them running. According to tjelink@ it is VmPoolMonitor interval. My (default) VmPoolMonitorIntervalInMinutes is 5 minutes and I have to wait... Make it to trigger the action immediatelly for newly edited pool or let the user know in documentation about this slowdown.

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

How reproducible:
100%

Steps to Reproduce:
1. new pool
2. edit pool (when previous task is done)
3. wait...
  
Actual results:
Have to wait for next trigger of VmPoolMonitor to start my VMs.

Expected results:
Have my prestarted VMs up ASAP when possible or let me know I have to wait.

Additional info:

2012-Dec-18, 16:54
VM test_pool-3 was restarted on Host dell-r210ii-04

2012-Dec-18, 16:54
VM test_pool-2 was restarted on Host dell-r210ii-04

2012-Dec-18, 16:54
VM test_pool-1 was restarted on Host dell-r210ii-04

2012-Dec-18, 16:53
VM test_pool-3 was restarted on Host <UNKNOWN>

2012-Dec-18, 16:53
VM test_pool-2 was restarted on Host <UNKNOWN>

2012-Dec-18, 16:53
VM test_pool-1 was restarted on Host <UNKNOWN>

2012-Dec-18, 16:51
VM Pool test_pool was updated by admin@internal, 0 VMs were added.

2012-Dec-18, 16:50
VM test_pool-5 creation has been completed.


[root@jb-rh31 ~]# rhevm-config -a | egrep -i "pool.*interval"
VmPoolMonitorIntervalInMinutes: 5 version: general

Comment 1 Simon Grinberg 2012-12-26 12:45:53 UTC

Required behavior: 
The VMs should start immediately when setting the pre-started number

VmPoolMonitor should be the mechanism to grantee that if VMs where consumed, to pre-start other.

Comment 2 Arik 2013-02-06 11:26:51 UTC

https://gerrit.eng.lab.tlv.redhat.com/gitweb?p=ovirt-engine.git;a=commit;h=e56b145f148b2f99e62b0686ca52fb640fb6c1da
https://gerrit.eng.lab.tlv.redhat.com/gitweb?p=ovirt-engine.git;a=commit;h=8ab7ff2810bcc8e09654e04f74717210d15cd40f

Comment 3 Jiri Belka 2013-02-14 14:38:55 UTC

OK, sf7.

2013-Feb-14, 15:30
VM testpool-2 was restarted on Host <UNKNOWN>
	
2013-Feb-14, 15:30
VM testpool-1 was restarted on Host <UNKNOWN>
	
2013-Feb-14, 15:30
VM Pool testpool was updated by admin@internal, 0 VMs were added.

Comment 4 Itamar Heim 2013-06-11 08:23:07 UTC

3.2 has been released

Comment 5 Itamar Heim 2013-06-11 08:25:02 UTC

3.2 has been released