Public bug reported: Nova version:Havana
We have two compute nodes: Host A and Host B. Each one have 100G disk, 4 cpus and 2G mem for example. First, launch an image-backed instance named vm-1 in Host A using the flavor successfully. The flavor's specs is 60G disk, 2cpus and 1G mem. So, obviously the free resource on Host A is 40G disk, 2 cpus and 1 mem. Second, doing live migration with block migation flag from Host A to Host B.Then success. Now, no active instance exist on Host A. But, the problem is the free resource on Host A is still 40G disk, 2 cpu and 1G mem. The resource described in compute_nodes table don't add back. Then adding another new instance named vm-2 to Host A using same flavor as vm-1. We are notified that resource is insuffieint on Host A.(40G<60G disk denied) Notice that the data would be correct after next priodic task of update_available_resource. Wihin the interval time, it means we can't deploy another instance, but it can be in fact. I think the resource should be recaculate immediatly on Host A, otherwise it may affects vm delpoyment. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1267862 Title: launch a new vm fail in source host after live migration Status in OpenStack Compute (Nova): New Bug description: Nova version:Havana We have two compute nodes: Host A and Host B. Each one have 100G disk, 4 cpus and 2G mem for example. First, launch an image-backed instance named vm-1 in Host A using the flavor successfully. The flavor's specs is 60G disk, 2cpus and 1G mem. So, obviously the free resource on Host A is 40G disk, 2 cpus and 1 mem. Second, doing live migration with block migation flag from Host A to Host B.Then success. Now, no active instance exist on Host A. But, the problem is the free resource on Host A is still 40G disk, 2 cpu and 1G mem. The resource described in compute_nodes table don't add back. Then adding another new instance named vm-2 to Host A using same flavor as vm-1. We are notified that resource is insuffieint on Host A.(40G<60G disk denied) Notice that the data would be correct after next priodic task of update_available_resource. Wihin the interval time, it means we can't deploy another instance, but it can be in fact. I think the resource should be recaculate immediatly on Host A, otherwise it may affects vm delpoyment. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1267862/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp