Cannot create a security group rule with its own SG as the source field

[Tomoe Sugihara]

Horizon only allows you to create a rule with the other SG as the source field, not its own SG.
Nova API allows you to create such a rule and horizon shouldn't prevent from creating it.

This happens on essex branch.

[Devin Carlen (devcamcar)]

I'm not sure I understand why you would want to do this? Can you explain the use case?

It may be a bug that Nova allows this, so we just need to figure out which one is incorrect and fix it there.

[Tomoe Sugihara (tomoe)]

Devin,

If you go to EC2's Security Group page, you can do this. I thought Nova was following that model.
Do you know why Horizon is preventing this?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/9979

[Julie Pichon (jpichon)]

I submitted a patch for this, although I realise the bug hasn't been "accepted" yet.

If the patch is declined because of this I'd be happy to adapt the included test to the existing code. There's no test for adding a rule with a security group as source at the moment, and I think it would be useful.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/9979
Committed: http://github.com/openstack/horizon/commit/ac39a8e5903398606053b57ce948cf9d5aa5463a
Submitter: Jenkins
Branch: master

commit ac39a8e5903398606053b57ce948cf9d5aa5463a
Author: Julie Pichon <email address hidden>
Date: Sun Jul 15 21:43:13 2012 +0100

    Allow security group rules to have their own group as a source

    Fixes bug 1012457.

    Change-Id: I8f9dc6904ba4b19302551fae7455fdf41b50442e