Bug 1020020

Summary:	OPENSHIFT_GEAR_MEMORY_MB does not change if the default template changes
Product:	OpenShift Online	Reporter:	Rob Millner <rmillner>
Component:	Containers	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED NOTABUG	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	dmcphers, mfisher, mfojtik
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-16 23:15:16 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:

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.