storm-deploy exception about storm-deploy

[BenMacKenzie]

Just a quick follow up:

notwithstanding the fact the storm-deploy threw an exception and did not complete, I am able to submit and execute a topology.

Also, I had to manually modify the aws security group nimbus is assigned to in order to access the ui.

[jsquirrelz]

I'm having the same issue. As soon as the attaching phase begins, it throws a RuntimeException:

ERROR logging - Exception in thread "main"
ERROR logging - java.lang.RuntimeException: request: POST https://ec2.us-west-1.amazonaws.com/ HTTP/1.1; cause: java.lang.NullPointerException (NO_SOURCE_FILE:1)

Unfortunately I made the edit to the Nimbus security group (added port 8080) and tried to visit the UI, but it threw an internal server error. Tried submitting a topology as well, turns out Nimbus never started (or crashed on startup?).

[rjtg]

Same issue for me

[gworley3]

I wrote a reply to this on the mailing list: something changed with Amazon's security group api responses because it is breaking the version of jclouds used in storm-deploy. They made the change a couple weeks ago. Not sure what has changed that is incompatible with the version of jclouds used by storm-deploy, but a workaround that we're using is to comment out everything that sets security groups and manage them manually via the ec2 web ui after we bring up the cluster.

[kerinin]

Same here