The source group of security group does not work

Bug #1373832 reported by Ken'ichi Ohmichi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

I created a security group with the other security group as the source group, and booted a server with the security group:

$ nova secgroup-create source-any "secgroup for any sources"
$ nova secgroup-add-rule source-any tcp 1 65535 0.0.0.0/0
$
$ nova secgroup-create accept-ssh "secgroup for ssh"
$ nova secgroup-add-group-rule accept-ssh source-any tcp 22 22
$
$ nova boot --flavor m1.nano --security-groups accept-ssh --image cirros-0.3.2-x86_64-uec vm01

but I could not access the server with SSH.

According to http://docs.openstack.org/developer/nova/nova.concepts.html#concept-security-groups , the source group is
considered as CIDR of acceptable source addresses and we can reuse it for new security groups.

Revision history for this message
Sean Dague (sdague) wrote :

Hmm... I sort of think this is working as designed and the docs are wrong. Is this possibly just a documentation bug?

Changed in nova:
status: New → Incomplete
Revision history for this message
Ken'ichi Ohmichi (oomichi) wrote :

I'm not sure now what is right usage of this feature.
Hopefully, some typos on the documentation would be nice.

no longer affects: neutron
Revision history for this message
Anne Gentle (annegentle) wrote :

The source for http://docs.openstack.org/developer/nova lives in the nova repo.

no longer affects: openstack-manuals
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.