Bug 1368512
| Summary: | [RFE] Director should check available resources before deployment/upgrade | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | mlammon |
| Component: | openstack-tripleo-validations | Assignee: | Florian Fuchs <flfuchs> |
| Status: | CLOSED ERRATA | QA Contact: | Ola Pavlenko <opavlenk> |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | 12.0 (Pike) | CC: | achernet, apannu, dbecker, dmacpher, jcoufal, jjoyce, jrist, jschluet, mburns, morazi, opavlenk, rhel-osp-director-maint, sclewis, slinaber, tvignaud, ukalifon |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, Triaged |
| Target Release: | 12.0 (Pike) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-validations-7.1.1-0.20170621111847.fb7346f.el7ost | Doc Type: | Enhancement |
| Doc Text: |
The update adds a new validation to check the hardware resource on the undercloud before an deployment or upgrade. The validation ensures the undercloud meets the necessary disk space and memory requirements prior to a deployment or upgrade.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-13 20:46:56 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: | |||
| Bug Depends On: | 1510719, 1510722, 1512556 | ||
| Bug Blocks: | 1442136, 1469882 | ||
|
Description
mlammon
2016-08-19 15:44:15 UTC
Changing component to validations. Tho this should be doable via node tagging, where resource amount is requested for node tagging. Potential candidate for M3 There are already validations for disk space and ram as part of the prep and pre-introspection groups, but not as part of the pre-upgrade/update groups. Verified: openstack-tripleo-validations-7.4.2-1.el7ost.noarch 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/RHEA-2017:3462 |