Closed guarly closed 10 years ago
I'm able to solve it with the following code snippet:
--- a/src/clj/backtype/storm/security.clj
+++ b/src/clj/backtype/storm/security.clj
@@ -116,7 +116,7 @@
(sg-service compute)
region
to-group
- (UserIdGroupPair. user-id from-group)
+ (UserIdGroupPair. "" from-group)
)
(catch IllegalStateException _)
)))
You should open a pull request with your fix for this and the other issue.
Done, although not sure if complying with the necessary netiquette...
On Sun, Feb 10, 2013 at 9:34 PM, petermelias notifications@github.comwrote:
You should open a pull request with your fix for this and the other issue.
— Reply to this email directly or view it on GitHubhttps://github.com/nathanmarz/storm-deploy/issues/24#issuecomment-13360501..
This issue should be closed, it was resolved by ec9c1251224765c76e7aa59842500834b2ce258b.
The API Request to AWS requesting to add the supervisor/zookeeper groups to the nimbus security group fails consistently with an "InvalidPlacementGroup.Unknown" error, due to the fact that the API AuthorizeSecurityGroupIngress doesn't like telling a SourceSecurityGroupOwnerId when it's yourself: