Bug 1020020 - OPENSHIFT_GEAR_MEMORY_MB does not change if the default template changes
Summary: OPENSHIFT_GEAR_MEMORY_MB does not change if the default template changes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jhon Honce
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 19:34 UTC by Rob Millner
Modified: 2015-05-14 23:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-16 23:15:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rob Millner 2013-10-16 19:34:35 UTC
Description of problem:
OPENSHIFT_GEAR_MEMORY_MB is set based on the default template when a gear is created.  Cartridges use it for tuning in their ERB processed configuration files.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create apps
2. modify memory_limit_in_bytes in /etc/openshift/resource_limits.conf
3. [ The missing step that updates the gear environment and configuration ]
4. Restart apps
5. Check gear env OPENSHIFT_GEAR_MEMORY_MB and config files

Actual results:
Step 5 shows no changes.

Expected results:
Step 5 should have changed.

Additional info:
Step 3 is missing.

Comment 1 Dan McPherson 2013-10-16 20:59:47 UTC
Taking off UpcomingRelease so we at least talk about this.

Comment 2 Jhon Honce 2013-10-16 23:15:16 UTC
Gear migrations will be used to update values in gears.


Note You need to log in before you can comment on or make changes to this bug.