| 2018-03-20 16:46:19 |
Hanif Kukkalli |
bug |
|
|
added bug |
| 2018-03-20 16:46:54 |
Hanif Kukkalli |
tags |
placement |
neutron placement |
|
| 2018-03-20 16:47:05 |
Hanif Kukkalli |
tags |
neutron placement |
neutron nova-manage placement |
|
| 2018-03-20 16:47:30 |
Hanif Kukkalli |
tags |
neutron nova-manage placement |
nova-manage placement |
|
| 2018-03-20 16:49:20 |
Hanif Kukkalli |
description |
Description
===========
When I execute the command `nova-status upgrade check`,
output:
nova-status upgrade check
+----------------------------------------------------------------------+
| Upgrade Check Results |
+----------------------------------------------------------------------+
| Check: Cells v2 |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Placement API |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Resource Providers |
| Result: Warning |
| Details: There are 4 compute resource providers and 15 compute nodes |
| in the deployment. Ideally the number of compute resource |
| providers should equal the number of enabled compute nodes |
| otherwise the cloud may be underutilized. See |
| http://docs.openstack.org/developer/nova/placement.html |
| for more details. |
+----------------------------------------------------------------------+
How to replicate this?
Remove the hosts from the openstack controller:
nova hypervisor-list
nova service-delete {id}
Then run:
su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
The deleted compute node will be added again as a new node.
run:
nova-status upgrade check
You can find this warning.
This causes issue with placement of new VM's.
The deleted compute host will not be considered during VM scheduling and placement. |
Description
===========
When I execute the command `nova-status upgrade check`,
output:
nova-status upgrade check
+----------------------------------------------------------------------+
| Upgrade Check Results |
+----------------------------------------------------------------------+
| Check: Cells v2 |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Placement API |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Resource Providers |
| Result: Warning |
| Details: There are 4 compute resource providers and 15 compute nodes |
| in the deployment. Ideally the number of compute resource |
| providers should equal the number of enabled compute nodes |
| otherwise the cloud may be underutilized. See |
| http://docs.openstack.org/developer/nova/placement.html |
| for more details. |
+----------------------------------------------------------------------+
How to replicate this?
Remove the hosts from the openstack controller:
nova hypervisor-list
nova service-delete {id}
Then run:
su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
The deleted compute node will be added again as a new node.
run:
nova-status upgrade check
You can find this warning.
This causes issue with placement of new VM's.
The compute host which was deleted and added again will not be considered during VM scheduling and placement. |
|
| 2018-03-20 16:53:34 |
Hanif Kukkalli |
description |
Description
===========
When I execute the command `nova-status upgrade check`,
output:
nova-status upgrade check
+----------------------------------------------------------------------+
| Upgrade Check Results |
+----------------------------------------------------------------------+
| Check: Cells v2 |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Placement API |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Resource Providers |
| Result: Warning |
| Details: There are 4 compute resource providers and 15 compute nodes |
| in the deployment. Ideally the number of compute resource |
| providers should equal the number of enabled compute nodes |
| otherwise the cloud may be underutilized. See |
| http://docs.openstack.org/developer/nova/placement.html |
| for more details. |
+----------------------------------------------------------------------+
How to replicate this?
Remove the hosts from the openstack controller:
nova hypervisor-list
nova service-delete {id}
Then run:
su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
The deleted compute node will be added again as a new node.
run:
nova-status upgrade check
You can find this warning.
This causes issue with placement of new VM's.
The compute host which was deleted and added again will not be considered during VM scheduling and placement. |
Description
===========
When I execute the command `nova-status upgrade check`,
output:
nova-status upgrade check
+----------------------------------------------------------------------+
| Upgrade Check Results |
+----------------------------------------------------------------------+
| Check: Cells v2 |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Placement API |
| Result: Success |
| Details: None |
+----------------------------------------------------------------------+
| Check: Resource Providers |
| Result: Warning |
| Details: There are 4 compute resource providers and 15 compute nodes |
| in the deployment. Ideally the number of compute resource |
| providers should equal the number of enabled compute nodes |
| otherwise the cloud may be underutilized. See |
| http://docs.openstack.org/developer/nova/placement.html |
| for more details. |
+----------------------------------------------------------------------+
Steps to reproduce
==================
How to replicate this?
Remove the hosts from the openstack controller:
nova hypervisor-list
nova service-delete {id}
Then run:
su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova
The deleted compute node will be added again as a new node.
run:
nova-status upgrade check
Expected result
===============
No warning when you run:
nova-status upgrade check
Actual result
=============
You can find the warning.
This causes issue with placement of new VM's.
The compute host which was deleted and added again will not be considered during VM scheduling and placement.
Environment
===========
OpenStack Pike release
Neutron Networking which is default.
Logs and Configs
================
Config as the Openstack documentation. |
|
| 2018-03-21 21:18:23 |
Matt Riedemann |
nova: status |
New |
Incomplete |
|
| 2018-03-21 21:28:58 |
Surya Seetharaman |
tags |
nova-manage placement |
placement |
|
| 2018-05-28 04:17:37 |
Launchpad Janitor |
nova: status |
Incomplete |
Expired |
|
| 2018-07-06 22:56:37 |
iain MacDonnell |
nova: status |
Expired |
Incomplete |
|
| 2018-09-22 00:59:26 |
OpenStack Infra |
nova: status |
Incomplete |
In Progress |
|
| 2018-09-22 00:59:26 |
OpenStack Infra |
nova: assignee |
|
iain MacDonnell (imacdonn) |
|
| 2018-09-22 16:22:35 |
Matt Riedemann |
nova: importance |
Undecided |
Medium |
|
| 2018-09-22 16:22:46 |
Matt Riedemann |
nominated for series |
|
nova/queens |
|
| 2018-09-22 16:22:46 |
Matt Riedemann |
bug task added |
|
nova/queens |
|
| 2018-09-22 16:22:46 |
Matt Riedemann |
nominated for series |
|
nova/pike |
|
| 2018-09-22 16:22:46 |
Matt Riedemann |
bug task added |
|
nova/pike |
|
| 2018-09-22 16:22:46 |
Matt Riedemann |
nominated for series |
|
nova/rocky |
|
| 2018-09-22 16:22:46 |
Matt Riedemann |
bug task added |
|
nova/rocky |
|
| 2018-09-22 16:23:06 |
Matt Riedemann |
nova/pike: status |
New |
Confirmed |
|
| 2018-09-22 16:23:08 |
Matt Riedemann |
nova/queens: status |
New |
Confirmed |
|
| 2018-09-22 16:23:10 |
Matt Riedemann |
nova/rocky: status |
New |
Confirmed |
|
| 2018-09-22 16:23:17 |
Matt Riedemann |
nova/pike: importance |
Undecided |
Medium |
|
| 2018-09-22 16:23:19 |
Matt Riedemann |
nova/queens: importance |
Undecided |
Medium |
|
| 2018-09-22 16:23:29 |
Matt Riedemann |
nova/rocky: importance |
Undecided |
Medium |
|
| 2018-09-24 13:29:18 |
OpenStack Infra |
nova: status |
In Progress |
Fix Released |
|
| 2018-09-24 13:48:27 |
OpenStack Infra |
nova/rocky: status |
Confirmed |
In Progress |
|
| 2018-09-24 13:48:27 |
OpenStack Infra |
nova/rocky: assignee |
|
s10 (vlad-esten) |
|
| 2018-09-24 13:48:49 |
OpenStack Infra |
nova/queens: status |
Confirmed |
In Progress |
|
| 2018-09-24 13:48:49 |
OpenStack Infra |
nova/queens: assignee |
|
s10 (vlad-esten) |
|
| 2018-09-24 13:54:30 |
OpenStack Infra |
nova/pike: status |
Confirmed |
In Progress |
|
| 2018-09-24 13:54:30 |
OpenStack Infra |
nova/pike: assignee |
|
s10 (vlad-esten) |
|
| 2018-09-25 12:16:17 |
OpenStack Infra |
nova/rocky: status |
In Progress |
Fix Committed |
|
| 2018-09-26 15:46:41 |
OpenStack Infra |
nova/queens: status |
In Progress |
Fix Committed |
|
| 2018-10-03 14:26:27 |
OpenStack Infra |
nova/pike: status |
In Progress |
Fix Committed |
|
