Bug 1061424
| Summary: | The hot_deploy marker/--hot-deploy option can not take effect when deploying app with binary deployment | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
| Component: | ImageStreams | Assignee: | Brenton Leanhardt <bleanhar> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.0.0 | CC: | adellape, agoldste, anli, bparees, chunchen, jolamb, pruan, wsun |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-openshift-origin-node-1.17.5.9-1.el6op openshift-origin-node-util-1.17.5-1.el6op | Doc Type: | Bug Fix |
| Doc Text: |
The --hot-deploy option was ignored when deploying an application using the binary deployment method. This bug fix adds the missing handling for the --hot-deploy option to the binary deployment logic and the option is now recognized. The MCollective service must be restarted after applying this fix.
|
Story Points: | --- |
| Clone Of: | 1033523 | Environment: | |
| Last Closed: | 2014-02-25 15:48:00 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: | |||
| Bug Depends On: | 1033523 | ||
| Bug Blocks: | |||
|
Description
Brenton Leanhardt
2014-02-04 20:06:39 UTC
Verified on puddle-2-0-3-2014-02-06 On node : tailf platform.log 1. deploy using curl [ose215@dhcp-9-237 ~]$ curl -k -H "Accept: application/xml" --user "hanli1:redhat" https://br215.oseanli.cn/broker/rest/application/52f481254945dc14ab0002ef/deployments -X POST -d artifact_url=http://sperl510-hanli1dom.oseanli.cn/jbosseap.tar.gz -d hot_deploy=true <?xml version="1.0" encoding="UTF-8"?> <response> <status>created</status> <type>deployment</type> <data> <deployment> <created-at>2014-02-07T08:31:42Z</created-at> <hot-deploy>true</hot-deploy> <force-clean-build>false</force-clean-build> <ref>master</ref> <sha1 nil="true"></sha1> <id>7daa8ce7</id> <activations> <activation>2014-02-07T08:31:45Z</activation> </activations> </deployment> </data> <messages> <message> <severity>info</severity> <text>Added 7daa8ce7 to application jbosseap</text> <exit-code>0</exit-code> <field nil="true"></field> <index nil="true"></index> </message> </messages> <version>1.6</version> <api-version>1.6</api-version> <supported-api-versions> <supported-api-version>1.0</supported-api-version> <supported-api-version>1.1</supported-api-version> <supported-api-version>1.2</supported-api-version> <supported-api-version>1.3</supported-api-version> <supported-api-version>1.4</supported-api-version> <supported-api-version>1.5</supported-api-version> <supported-api-version>1.6</supported-api-version> </supported-api-versions> </response> 2.deploy using rhc deploy-app [ose215@dhcp-9-237 jbosseap]$ rhc deploy-app --ref jbosseap.tar.gz -a jbosseap --hot-deploy Deployment of file '/home/ose215/jbosseap/jbosseap.tar.gz' in progress for application jbosseap ... Starting deploy for binary artifact Stopping gear Not stopping cartridge jbosseap because hot deploy is enabled Creating new deployment directory Preparing deployment Preparing build for deployment Deployment id is 0fa5b90d Distributing deployment Distribution status: success Activating deployment Not starting cartridge haproxy because hot deploy is enabled Deploying jbosseap cartridge Not starting cartridge jbosseap because hot deploy is enabled Activation status: success Deployment status: success Success 3. Check the platform log, and there isn't cartridge restarted. 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. http://rhn.redhat.com/errata/RHBA-2014-0209.html |