Problems creating security groups within Asgard

[jhohertz]

I am getting started with Asgard, and running into a wall early on in the process around creating security groups for an application. I am working with an account w/o Classic, and running in a VPC. The subnets have been given the immutable_metadata tags as described in the Wiki.

All steps are fine up until the security group creation step, what happens is as follows:

1) Application was created fine 2) Create SG for application appears to work at first, and in fact, the empty security group does get created in EC2 3) Asgard brings up the screen for editing the ingress, and on saving the result, complains the security group does not exist. (Which, per item 2, it does, as Asgard did create it ok) 4) Bringing up the security group list in Asgard, it (usually) does not list the security group, but does see pre-existing ones. 5) Through some combination of events I have yet to identify, sometimes the security group does appear in the list of security groups, however: 6) Trying to edit that group when it does show up, gets the same result where it doesn't think it exists.

This is seen in both the binary 1.5 release, as well as builds against the current HEAD.

I've not had time yet to trace through what might be happening, but will follow up with what I find when I do.

Any ideas in the meantime what might be going wrong here?

[pdehlke]

bump

Exactly the same issue here, which makes Asgard effectively useless. I see that this has been sitting, uncommented on, for 9 months. Is anyone at Netflix paying attention?

[jhohertz]

Questions @pdehlke , were you using the lastest master? I haven't had a chance to try again since I filed the ticket but the commits from March 20th look like they might have touched some areas that would have improved this (it sure seemed like an issue with caching security groups).

This commit in particular: 80ea2ced0474809e7104001d4da1f8737b6e51f5