Bug 1264210 - nodejs control script should wait for http to be available
nodejs control script should wait for http to be available
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Timothy Williams
DeShuai Ma
Depends On: 1221836
  Show dependency treegraph
Reported: 2015-09-17 17:39 EDT by Timothy Williams
Modified: 2017-03-08 12 EST (History)
12 users (show)

See Also:
Fixed In Version: openshift-origin-cartridge-nodejs-
Doc Type: Bug Fix
Doc Text:
Previously, a Node.js cartridge with hot_deploy disabled would not wait until the application is actually available when starting the application. On scaled Node.js applications where 20 to 30 seconds is required for the application to start, an outage was seen during the push while the Node.js applications started. For other cartridges (such as JBoss EAP), each start is blocked until the application is available so that gear rotation ensures no downtime is experienced. This bug fix updates the Node.js cartridge to now block until the HTTP port is available, with a maximum wait time of 60 seconds. As a result, scaled Node.js cartridges with hot_deploy disabled will properly update and start gears in rotation when pushing a new version of the application. This ensures no downtime is seen while pushing a new version.
Story Points: ---
Clone Of: 1221836
Last Closed: 2015-09-30 12:38:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1844 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 2.2.7 security, bug fix and enhancement update 2015-09-30 16:35:28 EDT

  None (edit)
Comment 4 Gaoyun Pei 2015-09-18 03:17:39 EDT
Checked with puddle 2.2/2015-09-15.1, only got openshift-origin-cartridge-nodejs- on the env, waiting for openshift-origin-cartridge-nodejs- to test this bug.
Comment 6 Gaoyun Pei 2015-09-22 03:07:35 EDT
Verify this bug with openshift-origin-cartridge-nodejs-

The control script will check HTTP port is available when starting nodejs cartridge now. As shown in the output during deployment:
remote: *** Starting application using: npm start -d
remote: Waiting for application port (8080) become available ...
remote: Found listening port
remote: -------------------------
Comment 8 errata-xmlrpc 2015-09-30 12:38:46 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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