Bug 1096789
Summary: | Idler doesn't unidle secondary gears in a scaled application | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
Component: | Containers | Assignee: | Brenton Leanhardt <bleanhar> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 2.1.0 | CC: | adellape, dmace, gpei, jhonce, jkeck, libra-onpremise-devel, pruan, xtian, yadu |
Target Milestone: | --- | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-openshift-origin-node-1.23.9.14-1.el6op, rubygem-openshift-origin-controller-1.23.10.7-1.el6op, openshift-origin-broker-1.16.1.10-1.el6op | Doc Type: | Bug Fix |
Doc Text: |
When unidling scaled applications using the `oo-admin-ctl-gears idle` command or an HTTP request, the head gear was unidled, but secondary gears were left idle. This was because the unidle logic used a local gear start only affecting the head gear. This bug fix updates the logic to instead use a broker REST call to start the entire application when unidling, which affects all gears. As a result, head gears and secondary gears are all unidled as expected.
|
Story Points: | --- |
Clone Of: | 1093776 | Environment: | |
Last Closed: | 2014-08-04 13:27:03 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: | 1093776 | ||
Bug Blocks: |
Description
Brenton Leanhardt
2014-05-12 12:35:38 UTC
Upstream commit: commit 8bee9dbe15cf839b929bc19e9d6eb034f0fb0b05 Author: Dan Mace <ironcladlou> Date: Fri May 2 10:51:51 2014 -0400 Support unidling scalable apps Use a broker REST call to start the entire app up during unidle rather than a local gear start. Adjust the 'scale' auth scope to include explicit state changes. This allows the node to start the app via the broker API, and is consistent with the previous scope in that it already includes scaling (which itself involves an implicit state change). Resolve bug: https://bugzilla.redhat.com/show_bug.cgi?id=1093776 Verify this bug on puddle 2.1.z/2014-07-18.2. Create a scalable php app and embed mysql to it. Idle the two gears using "oo-admin-ctl-gears idlegear". [root@dhcp-129-188 workspace]# rhc app show app1 --gears ID State Cartridges Size SSH URL ------------------------ ----- ------------------- ------ -------------------------------------------------------------------------- 53ccb33edb26c87509000015 idle haproxy-1.4 php-5.4 medium 53ccb33edb26c87509000015.com.cn 53ccb3cadb26c87509000034 idle mysql-5.5 medium 53ccb3cadb26c87509000034.com.cn Then unidle the primary gear via HTTP request. Check the state of the gears again. [root@dhcp-129-188 workspace]# rhc app show app1 --gears ID State Cartridges Size SSH URL ------------------------ ------- ------------------- ------ -------------------------------------------------------------------------- 53ccb33edb26c87509000015 started haproxy-1.4 php-5.4 medium 53ccb33edb26c87509000015.com.cn 53ccb3cadb26c87509000034 started mysql-5.5 medium 53ccb3cadb26c87509000034.com.cn DB gear's state is started, so move this bug to VERIFIED. 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-0999.html |