+++ This bug was initially created as a clone of Bug #1108254 +++ +++ This bug was initially created as a clone of Bug #1073725 +++ Description of problem: Can not update user variables if user have setted maximum user variables
The maximum user-defined environment variables should be able to be manually configured with this PR: https://github.com/openshift/origin-server/pull/6403 As for the issue where users are unable to modify their existing variables when at their maximum, I can confirm that that was already resolved some time ago. Unless there is another issue this bug was opened for, the ability to configure the maximum user-defined environment variables should complete the work for this bug.
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/a4bee2ecfe84a166dac4a9f922dff99f973bb0f3 Allow maximum allowed user defined env variables to be configured Bug 1266239 https://bugzilla.redhat.com/show_bug.cgi?id=1266239
Verified this bug with 2.2/2016-08-08.1, and PASS. By default, allow user to create 50 user var. $ for i in $(seq 1 51); do rhc env-set TEST$i=VALUE$i -a php54app; done Setting environment variable(s) ... done ... Setting environment variable(s) ... User Variables maximum of 50 exceeded Change 'USER_VARIABLE_MAX_COUNT' option in /etc/openshift/node.conf to 60, user could create 10 more vars. $ for i in $(seq 51 60); do rhc env-set TEST$i=VALUE$i -a php54app; done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done Setting environment variable(s) ... done $ for i in $(seq 61 61); do rhc env-set TEST$i=VALUE$i -a php54app; done Setting environment variable(s) ... User Variables maximum of 60 exceeded
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://rhn.redhat.com/errata/RHSA-2016-1773.html