Bug 1459629 - openshift-on-openstack stack can not auto scaling
openshift-on-openstack stack can not auto scaling
Status: MODIFIED
Product: OpenShift Container Platform
Classification: Red Hat
Component: Reference Architecture (Show other bugs)
3.4.1
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Mark Lamourine
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-07 11:49 EDT by Gan Huang
Modified: 2017-07-19 15:58 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gan Huang 2017-06-07 11:49:01 EDT
Description of problem:
Creating a heat stack with autoscaling enabled ("autoscaling: true"), it turned out that the stack was not able to scale up automatically.

Version-Release number of selected component (if applicable):
openshift-heat-templates-0.9.9-2.el7ost.noarch
OCP 3.4 on OSP 10

How reproducible:
always

Steps to Reproduce:
1. Create a heat stack using following parameters template:

https://raw.githubusercontent.com/ganhuang/shell-learning/master/ocp-on-osp-scritps/ocp34-on-osp10/ocp-templates/ha-master-dedicated-flannel-auto-scale.yaml

2. After stack complete, adding CPU load against the app node.
for i in `seq 1 $(cat /proc/cpuinfo |grep "physical id" |wc -l)`; do dd if=/dev/zero of=/dev/null & done



Actual results:
The stack has no actions with the CPU load, the app node are not scaled up as expected.

Expected results:
The app node should be scaled up as expected once the CPU of app node reached the defined CPU threshold.

Additional info:
Comment 1 Mark Lamourine 2017-07-19 15:57:39 EDT
Fixed in PR https://github.com/redhat-openstack/openshift-on-openstack/pull/374
Comment 2 Mark Lamourine 2017-07-19 15:58:41 EDT
This will be fixed in the next release.

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