Bug 1032781

Summary: App status is shown as "Unknown" and unable to restart the app.
Product: OpenShift Online Reporter: Hasif <haasaif>
Component: WebsiteAssignee: Jordan Liggitt <jliggitt>
Status: CLOSED INSUFFICIENT_DATA QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: jliggitt
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-02 16:45:28 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:
Embargoed:
Attachments:
Description Flags
The image shows my app console. none

Description Hasif 2013-11-20 20:16:00 UTC 
Created attachment 826829 [details]
The image shows my app console.

Description of problem:
The app status is shown as "Unkonwn" and also unable to restart the app. When tried to restart the console is redirected to this url: 
https://openshift.redhat.com/app/console/server_unavailable

I was able to build the app from the rhc client. But when tried to restart from rhc client i got the following error "Server returned an unexpected error code: 504".

After building from rhc, the app is up and running.

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


How reproducible:


Steps to Reproduce:
1.Pushed the code into git.
2.Restarted the application
3.

Actual results:
App status "Unknown" and app is running fine.

Expected results:
App status "Started".

Additional info:
Comment 1 Jordan Liggitt 2013-11-21 16:15:58 UTC 
Can you recreate the issue? If so, can you run the rhc restart command that is failing in debug mode, and include the results (minus any authorization headers)?

HTTP_DEBUG=1 rhc -d app restart APP_NAME 2>&1 | grep -v authorization:
Comment 2 Jordan Liggitt 2013-12-02 16:45:28 UTC 
Closing. If you can recreate or provide more details, please reopen.