Provision/deploy operation can be started for node which doesn't belong to any cluster

[Artem Roma]

Steps to reproduce:
1. Create cluster (by any available or preferable means);
2. Try to deploy/provision single node which is not added to any cluster (indicated by "discovered" status):

     fuel --env {env_id} node --provision --node {node-id}

Expected:
some meaningful warning message from the client about that the user should add the node to any cluster prior provisioning/deploying it.

Actual:
traceback of internal server error:

500 Server Error: Internal Server Error (Traceback (most recent call last):
  File "/home/aroma/Programming/projects/fuel-web/nailgun/nailgun/api/v1/handlers/base.py", line 279, in content_json
    resp = func(cls, *args, **kwargs)
  File "/home/aroma/Programming/projects/fuel-web/nailgun/nailgun/api/v1/handlers/orchestrator.py", line 254, in PUT
    return self.handle_task(cluster)
  File "/home/aroma/Programming/projects/fuel-web/nailgun/nailgun/api/v1/handlers/orchestrator.py", line 215, in handle_task
    raise self.http(400, message=six.text_type(exc))
TypeError: http() got an unexpected keyword argument 'message'
)

It is worsen by that "--env" option is obligatory for user to supply for the command.

[Artem Roma (aroma-x)]

I've provided not proper traceback from my dev env with changed code of fuel-client. I apologize for that. Here is bug with correct info [1]. Mark this one as invalid.

[1]: https://bugs.launchpad.net/fuel/+bug/1445531