| 2016-08-03 00:53:39 |
Charlotte Han |
description |
Steps to reproduce
==================
A chronological list of steps which will bring off the
issue you noticed:
* I had a compute node, set allow_resize_to_same_host=true.
* I did boot a instance with flavor m1.tiny
1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True
* then I did boot many instance
* then I did Z
A list of openstack client commands (with correct argument value)
would be the most descriptive example. To get more information use:
$ nova --debug <command> <arg1> <arg2=value>
or
$ openstack --debug <command> <arg1> <arg2=value>
Expected result
===============
After the execution of the steps above, what should have
happened if the issue wasn't present?
Actual result
=============
What happened instead of the expected result?
How did the issue look like?
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://docs.openstack.org/releases/
If this is from a distro please provide
$ dpkg -l | grep nova
or
$ rpm -ql | grep nova
If this is from git, please provide
$ git log -1
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
Logs & Configs
==============
The tool *sosreport* has support for some OpenStack projects.
It's worth having a look at it. For example, if you want to collect
the logs of a compute node you would execute:
$ sudo sosreport -o openstack_nova --batch
on that compute node. Attach the logs to this bug report. Please
consider that these logs need to be collected in "DEBUG" mode.
This bug contains information that is:
PublicEdit |
Steps to reproduce
==================
A chronological list of steps which will bring off the
issue you noticed:
* I had a compute node, set allow_resize_to_same_host=true.
* I did boot a instance with flavor m1.tiny
1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True
* then I did boot many instances, let free vcpus of this compute node is 3
* then I did resize this instance use flavor 1-1 which vcpu number is 4.
| 1-1 | hanrong_cpu_4 | 512 | 1 | 0 | | 4 | 1.0 | True |
* then the instance was error.
{"message": "Insufficient compute resources: Free vcpu 3.00 VCPU < requested 4 VCPU.", "code": 400, "created": "2016-08-02T12:12:36Z"}
Expected result
===============
I hope this instance resize successfully and freen vcpus of this compute node is 0 after resize.
Actual result
=============
instance error, and freen vcpus of this compute node is 3 after resize.
Environment
===========
1.
If this is from git, please provide
$ git log -1
commit 2b0557e4ee6737f44cb6fa845d7f59446bca90bf
Merge: 40913fe 15a9458
Author: Jenkins <jenkins@review.openstack.org>
Date: Thu Jun 16 01:51:48 2016 +0000
Merge "Added missed response to test_server_tags" |
|
| 2016-08-04 19:51:30 |
Sarafraj Singh |
description |
Steps to reproduce
==================
A chronological list of steps which will bring off the
issue you noticed:
* I had a compute node, set allow_resize_to_same_host=true.
* I did boot a instance with flavor m1.tiny
1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True
* then I did boot many instances, let free vcpus of this compute node is 3
* then I did resize this instance use flavor 1-1 which vcpu number is 4.
| 1-1 | hanrong_cpu_4 | 512 | 1 | 0 | | 4 | 1.0 | True |
* then the instance was error.
{"message": "Insufficient compute resources: Free vcpu 3.00 VCPU < requested 4 VCPU.", "code": 400, "created": "2016-08-02T12:12:36Z"}
Expected result
===============
I hope this instance resize successfully and freen vcpus of this compute node is 0 after resize.
Actual result
=============
instance error, and freen vcpus of this compute node is 3 after resize.
Environment
===========
1.
If this is from git, please provide
$ git log -1
commit 2b0557e4ee6737f44cb6fa845d7f59446bca90bf
Merge: 40913fe 15a9458
Author: Jenkins <jenkins@review.openstack.org>
Date: Thu Jun 16 01:51:48 2016 +0000
Merge "Added missed response to test_server_tags" |
Steps to reproduce
==================
A chronological list of steps which will bring off the
issue you noticed:
* I had a compute node, set allow_resize_to_same_host=true.
* I did boot a instance with flavor m1.tiny
1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True
* then I did boot my instance, let free vcpus of this compute node is 3
* then I did resize this instance use flavor 1-1 which vcpu number is 4.
| 1-1 | hanrong_cpu_4 | 512 | 1 | 0 | | 4 | 1.0 | True |
* then the instance was error.
{"message": "Insufficient compute resources: Free vcpu 3.00 VCPU < requested 4 VCPU.", "code": 400, "created": "2016-08-02T12:12:36Z"}
Expected result
===============
I hope this instance resize successfully and freen vcpus of this compute node is 0 after resize.
Actual result
=============
instance error, and freen vcpus of this compute node is 3 after resize.
Environment
===========
1.
If this is from git, please provide
$ git log -1
commit 2b0557e4ee6737f44cb6fa845d7f59446bca90bf
Merge: 40913fe 15a9458
Author: Jenkins <jenkins@review.openstack.org>
Date: Thu Jun 16 01:51:48 2016 +0000
Merge "Added missed response to test_server_tags" |
|
