Autoscaling triggered by schedule and alarm and exceeds maxsize

asked 2017-03-30 00:19:04 -0500

fukuda-yuko gravatar image

Hi, In my OpenStack environment I'm seeing Autoscaling create more VMs than specified in maxsize when both scheduled autoscaling and alarm autoscaling (i.e. CPU usage metering) are triggered at the same time.

I'm currently using Kilo, but does anyone know if this has been implemented in recent Openstack releases or if there is a workaround?

Thanks in advance!

edit retag flag offensive close merge delete


Do you have the fix for this bug? That's the only thing I can think of that might be related.

zaneb gravatar imagezaneb ( 2017-03-30 18:16:34 -0500 )edit

Hmmm, this isn't exactly it, but thanks for the info!

fukuda-yuko gravatar imagefukuda-yuko ( 2017-04-07 00:14:38 -0500 )edit