Red Hat Bugzilla – Bug 844258
will keep "deploying" status in .state file for nodejs application after git push
Last modified: 2015-05-14 18:57:17 EDT
Description of problem:
Create nodejs app, login to the app and check the app-root/runtime/.state file, it should show the app current status. Do some change and git push the change, during the push, watch the .state file for app status, it will keep "deploying" after git push finished.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create nodejs app
2.Do some change and git push
3.After push finished, check the app-root/runtime/.state file for the app
The .state file will keep "deployint" status.
The status in .state should be started->stopped->building->deploying->started
Check the status from rest api will get the same result.
[root@ip-10-86-205-90 limits.d]# curl -k -H 'Accept: application/xml' --user firstname.lastname@example.org:123123 https://localhost/broker/rest/domains/bmengdev/applications/no1/gear_groups
<?xml version="1.0" encoding="UTF-8"?>
And check the status from rhc client,
$ rhc app status -a no1
Application 'no1' is running
app_ctl.sh doesn't update state for application. Should be modeled after jboss app_ctl_impl.sh regarding state updates.
Fixed by: https://github.com/openshift/crankcase/pull/373
Checked on devenv_1990, issue has been fixed.
After git push, nodejs app .state file show as started.