Comment 2 for bug 1671265

The issue is that some logic was added to account for changes to the security
group rules. Instead of updating any existing group with the changed rules, a
new one is always created. So there was a logic error introduced there. The
issue only applies to neutron, not nova groups. The code fix is to simply replace the
rules in the existing group like is done for AWS for example.

To fix an existing deployment with this issue, you need to delete the wrong security group and ensure existing machines have the correct group. More explicit instructions will be posted on how to do that.