Bug 1023855

Summary: Met "export:`OPENSHIFT_HAPROXY_*=<%= ENV['OPENSHIFT_HAPROXY_DIR'] %>*`: not a valid identifier" when ssh into existing scalable app on INT after migration.
Product: OpenShift Online Reporter: Liang Xia <lxia>
Component: ContainersAssignee: Paul Morie <pmorie>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.x   
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: 2014-01-24 03:27:10 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 Liang Xia 2013-10-28 05:59:43 UTC 
Description of problem:
When ssh into existing scalable app after INT migration, met following errors:
bash: export: `OPENSHIFT_HAPROXY_LOG_DIR.erb=<%= ENV['OPENSHIFT_HAPROXY_DIR'] %>logs/': not a valid identifier
bash: export: `OPENSHIFT_HAPROXY_PATH_ELEMENT.erb=<%= ENV['OPENSHIFT_HAPROXY_DIR'] %>usr/bin': not a valid identifier

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

How reproducible:
always

Steps to Reproduce:
1.create scalabe app on INT.
2.migrate servers.
3.ssh into app.

Actual results:
# rhc ssh jbossews2s
Connecting to 5264c9876cec0e4ccb00036e.rhcloud.com ...
Warning: Permanently added 'jbossews2s-lxiamigrate.int.rhcloud.com,50.19.66.196' (RSA) to the list of known hosts.
bash: export: `OPENSHIFT_HAPROXY_LOG_DIR.erb=<%= ENV['OPENSHIFT_HAPROXY_DIR'] %>logs/': not a valid identifier
bash: export: `OPENSHIFT_HAPROXY_PATH_ELEMENT.erb=<%= ENV['OPENSHIFT_HAPROXY_DIR'] %>usr/bin': not a valid identifier

Expected results:
SSH into the app successfully without errors.

Additional info:
Comment 1 Paul Morie 2013-10-28 21:08:27 UTC 
This happened because the haproxy upgrade script failed for your app, leaving unprocessed ERB templates in your haproxy/env directory.  Please retest the upgrade with a stage instance to see if this is still an issue - we have made several changes to the upgrades for this release.
Comment 2 Liang Xia 2013-10-30 02:07:18 UTC 
Still met this error on INT(devenv_3965).

$ rhc ssh jbossews2s
Connecting to 5269f7a003ef6419fc00057b.rhcloud.com ...
bash: export: `OPENSHIFT_HAPROXY_LOG_DIR.erb=<%= ENV['OPENSHIFT_HAPROXY_DIR'] %>logs/': not a valid identifier
bash: export: `OPENSHIFT_HAPROXY_PATH_ELEMENT.erb=<%= ENV['OPENSHIFT_HAPROXY_DIR'] %>usr/bin': not a valid identifier
Comment 3 Liang Xia 2013-10-30 07:48:52 UTC 
However, doesn't met this error after migration from devenv_stage_528  to devenv_3967.
Comment 4 Liang Xia 2013-10-30 09:09:36 UTC 
(In reply to Paul Morie from comment #1)
> This happened because the haproxy upgrade script failed for your app,
> leaving unprocessed ERB templates in your haproxy/env directory.  Please
> retest the upgrade with a stage instance to see if this is still an issue -
> we have made several changes to the upgrades for this release.

Hi Paul,

Will the broker apps on INT like this be fixed or not ?

Thanks,
Liang
Comment 5 Paul Morie 2013-10-30 14:41:21 UTC 
Liang-

Apps in INT will not be affected by the fix; you will have to test in a devenv.
Comment 6 Liang Xia 2013-10-31 09:00:17 UTC 
Verified on instance which is migrated from devenv_stage_528 to devenv_3973, didn't met this issue.

According to comment #3, #5, and this one, move to verified.