Bug 1026251 - Met syntax error on line 2 of php/configuration/etc/conf.d/openshift.conf when git push to app which is created with empty repo.
Summary: Met syntax error on line 2 of php/configuration/etc/conf.d/openshift.conf whe...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Mrunal Patel
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-04 09:34 UTC by Liang Xia
Modified: 2015-05-14 23:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-04 17:34:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Liang Xia 2013-11-04 09:34:23 UTC
Description of problem:
Given an app created with empty repo, when pushing changes, will met:
remote: Syntax error on line 2 of /var/lib/openshift/527763ba2587c82c01000066/php/configuration/etc/conf.d/openshift.conf:
remote: DocumentRoot must be a directory

Version-Release number of selected component (if applicable):
STG(devenv-stage_549)

How reproducible:
always

Steps to Reproduce:
1.Create an app with initial_git_url=empty.
2.Add some code to the local repo and git push.
3.

Actual results:
remote: Stopping PHP cartridge
remote: Syntax error on line 2 of /var/lib/openshift/527763ba2587c82c01000066/php/configuration/etc/conf.d/openshift.conf:
remote: DocumentRoot must be a directory
remote: httpd (no pid file) not running
remote: Building git ref 'master', commit 4dfa8e9
remote: Building PHP cartridge
remote: Preparing build for deployment
remote: Deployment id is 02b3d98a
remote: Activating deployment
remote: Starting PHP cartridge
remote: Result: success
remote: Activation status: success
remote: Deployment completed with status: success
To ssh://527763ba2587c82c01000066.rhcloud.com/~/git/myapp1.git/
   fcd7b39..4dfa8e9  master -> master

Expected results:
Git push successfully without errors.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.