Bug 1225327 - PHP hot deploy needs an app restart and server is unavailable during deployment
Summary: PHP hot deploy needs an app restart and server is unavailable during deployment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jakub Hadvig
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-27 06:49 UTC by Ingo Volkmann
Modified: 2015-09-08 20:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-08 20:14:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ingo Volkmann 2015-05-27 06:49:02 UTC
I set up a scaled PHP 5.3 app to deploy by a git push. During the push / deploy process, the server is unavailable:
503 Service Unavailable
No server is available to handle this request.
When the deployment is finished, the changes take no effect. I have to restart the app.

Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 310 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Not stopping cartridge php because hot deploy is enabled
remote: Syncing git content to other proxy gears
remote: Building git ref 'beta', commit 3041595
remote: Preparing build for deployment
remote: Deployment id is 7bded422
remote: Activating deployment
remote: Not starting cartridge haproxy because hot deploy is enabled
remote: Copy database file
remote: Copy .htaccess file
remote: Not starting cartridge php because hot deploy is enabled
remote: -------------------------
remote: Git Post-Receive Result: success
remote: Activation status: success
remote: Deployment completed with status: success

Comment 3 Wenjing Zheng 2015-07-02 03:17:36 UTC
Verified on INT(devenv_5573).


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