Bug 1492490
Summary: | [downstream clone - 4.1.7] [ovirt-ansible-roles] ovirt-vm-infra: memory_guaranteed value in template don't allow user to specify lower value in memory | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-ansible-roles | Assignee: | Ondra Machacek <omachace> |
Status: | CLOSED ERRATA | QA Contact: | Petr Kubica <pkubica> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.5 | CC: | mgoldboi, mperina, pstehlik |
Target Milestone: | ovirt-4.1.7 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-ansible-roles-1.0.4-1.el7ev | Doc Type: | No Doc Update |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | 1490852 | Environment: | |
Last Closed: | 2017-11-07 17:27:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1490852 | ||
Bug Blocks: |
Description
rhev-integ
2017-09-17 19:41:15 UTC
> user can't specify memory_guaranteed value to override this
I agree with this. We need to add it.
- if memory value was specified and memory_guaranteed not, role should recalculate memory_guaranteed value as webadmin (same behavior)
Martin, do we want this behavior?
(Originally by Ondra Machacek)
I've added a documentation that memory param shouldn't be less then memory_guaranteed param, user need to pass those parameter correctly otherwise we fail. (Originally by Ondra Machacek) I've added a documentation that memory param shouldn't be less then memory_guaranteed param, user need to pass those parameter correctly otherwise we fail. (Originally by Ondra Machacek) Verified in ansible-2.3.2.0-2.el7.noarch ovirt-ansible-roles-1.0.4-1.el7ev.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/RHBA-2017:3137 |