Bug 1459629 - openshift-on-openstack stack can not auto scaling
Summary: openshift-on-openstack stack can not auto scaling
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Reference Architecture
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.7.0
Assignee: Mark Lamourine
QA Contact: Gan Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-07 15:49 UTC by Gan Huang
Modified: 2020-02-03 14:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-27 06:43:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gan Huang 2017-06-07 15:49:01 UTC
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 19:57:39 UTC
Fixed in PR https://github.com/redhat-openstack/openshift-on-openstack/pull/374

Comment 2 Mark Lamourine 2017-07-19 19:58:41 UTC
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.