Bug 1020020 - OPENSHIFT_GEAR_MEMORY_MB does not change if the default template changes
OPENSHIFT_GEAR_MEMORY_MB does not change if the default template changes
Status: CLOSED NOTABUG
Product: OpenShift Online
Classification: Red Hat
Component: Containers (Show other bugs)
2.x
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Jhon Honce
libra bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-16 15:34 EDT by Rob Millner
Modified: 2015-05-14 19:30 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-16 19:15:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rob Millner 2013-10-16 15:34:35 EDT
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 16:59:47 EDT
Taking off UpcomingRelease so we at least talk about this.
Comment 2 Jhon Honce 2013-10-16 19:15:16 EDT
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.