Comment 0 for bug 1620011
Revision history for this message
| Kanagaraj Manickam (kanagaraj-manickam) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
when signal occurred during the cooldown window, heat does not report that its not doing the scaling due to cooldown widnow. so better provide an http response for resource signal action, saying 202->accepted for scaling 403-> conflict , no signalling. now user could differentiate whether scaling started or cooldown happening, now there is no response provided for resource signal action