Bug 1011326

Summary: [origin_broker_113] The value of 'secret_token' in mongo did not change after reset 'OPENSHIFT_SECRET_TOKEN'
Product: OpenShift Online Reporter: zhaozhanqi <zzhao>
Component: PodAssignee: Abhishek Gupta <abhgupta>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: xtian
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-17 13:30:51 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 zhaozhanqi 2013-09-24 05:43:08 UTC
Description of problem:
create one app and reset the env variable 'OPENSHIFT_SECRET_TOKEN', after do that, the OPENSHIFT_SECRET_TOKEN has been changed, but in mongo the value 'secret_token' did not change.

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

How reproducible:
always

Steps to Reproduce:
1. create one any type app
2. reset the value of env variable OPENSHIFT_SECRET_TOKEN
    rhc env set OPENSHIFT_SECRET_TOKEN=hello -a $app
3. rhc ssh -a $app --gear env |grep -i variable OPENSHIFT_SECRET_TOKEN
4. check mongo db

Actual results:

step 3: OPENSHIFT_SECRET_TOKEN=hello
step 4: the value of secret_token did not change
"secret_token" "g1F41sFyHjLOZnM8_122BnkpL1Wds4RaRw2zv4Lidv1tcvtUr3VHrrh5Ym9SDxXFxxsEbSOK3R2XjUv4B8MdPZsIVXdfUOz6zHqCJGBsOmhm_jYJ_Hz-pxkLYyYXzJa-"

Expected results:
the value of 'secret_token' in mongo should be also changed and keep consistent with OPENSHIFT_SECRET_TOKEN

Additional info:

Comment 1 Abhishek Gupta 2013-09-24 22:49:51 UTC
This is as expected. The user can set/reset the environment variable and the token stored in mongo will not be updated. The secret token stored in mongo is the system generated token and can be overridden by the user. The user specified environment variable will take effect in such cases. If the user decides to unset/remove the environment variable, then the system generated secret token will once again be applicable.

Comment 2 zhaozhanqi 2013-09-25 01:56:34 UTC
according to comment 1, it is by design, so close this bug.