Bug 1231777
| Summary: | Its possible to scale up beyond the number of free nodes | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Amit Ugol <augol> |
| Component: | python-rdomanager-oscplugin | Assignee: | Jan Provaznik <jprovazn> |
| Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 (Kilo) | CC: | brad, calfonso, dmacpher, jslagle, mburns, rhel-osp-director-maint, yeylon |
| Target Milestone: | y1 | Keywords: | Triaged, ZStream |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-rdomanager-oscplugin-0.0.10 | Doc Type: | Bug Fix |
| Doc Text: |
The "openstack overcloud deploy" command did not check available nodes for deployment. This caused failed deployments due if there were not enough nodes available. This fix adds a pre-deployment check to the CLI and checks the number of available nodes before creating or updating the Overcloud stack. Now if not enough nodes are available, users get an error message before Heat creates or updates the stack.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-08 12:09:44 UTC | 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: | |||
|
Description
Amit Ugol
2015-06-15 11:56:21 UTC
Moving this to an oscplugin bug since the CLI is the only place that speaks across both Tuskar and Ironic. Assigning this to Jan as he's the one who implemented stack scaling. The scale command is being replaced with the newly added CLI command which is now used for any update of stack:
openstack management plan set $PLAN_UUID -S Compute-1=2
openstack overcloud deploy --plan-uuid $PLAN_UUID
I can implement a check in the "openstack overcloud deploy" command which would check number of available nodes, but TBH not sure if this is high prio - we don't implement ATM any other tests for other input - e.g. flavor, images,...
Latest version: $ openstack overcloud deploy --templates --control-scale 1 --compute-scale 2 Deployment failed: Not enough nodes - available: 0, requested: 3 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1862 |