CloudifySource / cloudify-widget

Widget for embedding a Cloudify "recipe player" in other website, to allow visitors to launch a certain recipe with a single click.
Apache License 2.0
3 stars 11 forks source link

When cloudify fails to install a recipe, machine does not return to pool #43

Closed guy-mograbi-at-gigaspaces closed 9 years ago

guy-mograbi-at-gigaspaces commented 11 years ago

on "dev" environment, I started from scratch with a single widget. I entered wrong input ( wrong recipe details ) and hit "play" in the widget.

The "play" failed with a message "recipe is invalid" which is ok.. I stopped the server and restarted again -

==> saw the following prints

5614 [main] INFO beans.ServerPoolImpl - Started to initialize ServerPool, cold-init=false 7088 [main] INFO beans.ServerPoolImpl - ServerId: 880551 expired or not found in server-pool, address: {private=[Address{addr=10.6.35.171, version=4}, Address{addr=15.185.164.122, version=4}]} 7363 [main] INFO beans.ServerBootstrapperImpl - Server id: 880551 was deleted. 7366 [main] INFO beans.ServerPoolImpl - ServerId: 880549 expired or not found in server-pool, address: {private=[Address{addr=10.6.35.170, version=4}, Address{addr=15.185.164.116, version=4}]} 7604 [main] INFO beans.ServerBootstrapperImpl - Server id: 880549 was deleted. 7611 [main] INFO beans.ServerPoolImpl - Found a busy server, leave it: Server{id=880547, name=cloudify_pool_server1

==> It seems that the pool was changed. The correct behavior should be - if recipe is invalid, we should return the server to the pool and it was untouched.