This is a bug that is a result of changing the behavior of source groups. For
a while we emulated the old style aws source group style that doesn't allow
specifying protocol and ports. This was changed recently and it looks like
this check was missed.
Vish
On Oct 6, 2011, at 6:20 AM,
Hi guys.
Recently, I've stumbled upon strange behaviour of euca-authorize
command. I'm using Diablo release
If I create two security groups and add a rule using euca-authorize
command to authorize ICMP traffic from one group to another, why am I
not able to add another rule for, say, tcp traffic?
2 matches
Mail list logo
