"profiles" commands should check nova hypervisors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Low
|
Dmitry Tantsur |
Bug Description
Dear Stackers,
Apparently, the following commands don't ensure we can deploy the overcloud properly:
- openstack overcloud profiles list
- openstack overcloud profiles match <options>
For example, even if we have the previously listed commands working fine (first one returns the matching between hosts and profiles, the second has a 0 exit code), Nova can't see the nodes. The following command might show the issue: openstack hypervisor stats show
The "count" entry can show a 0, because of several issues, like https:/
Making the "overcloud profiles" commands check nova hypervisor states would allow to have a reliable way to ensure we actually HAVE the compute power needed in order to either deploy or scale out the overcloud.
Thank you!
Cheers,
C.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Low |
assignee: | nobody → Dmitry Tantsur (divius) |
tags: | added: tripleoclient |
Changed in tripleo: | |
milestone: | none → queens-1 |
summary: |
- "profiles" commands shoule check nova hypervisors + "profiles" commands should check nova hypervisors |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Fix proposed to branch: master /review. openstack. org/500570
Review: https:/