security-group-not-attached-to-instance

[Vipul Sabhaya]

The security groups refactor missed an important assignment, which causes None to be passed into the 'boot' call.

security_groups = None
        if CONF.trove_security_groups_support:
            try:
                self._create_secgroup()

The response of _create_secgroup() should be assigned to security_groups, such that it's propagated to nova_client.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/54235
Committed: http://github.com/openstack/trove/commit/d7e153dbb1db3f26463e059082ecefa2179035b5
Submitter: Jenkins
Branch: master

commit d7e153dbb1db3f26463e059082ecefa2179035b5
Author: Vipul Sabhaya <email address hidden>
Date: Mon Oct 28 22:40:56 2013 -0700

    Fix bug in Security Group association to Instance

    * Refactor of security groups to TaskManager left out an assignment that
      is required for the security_group to be attached to an intance.

    fixes bug 1245767

    Change-Id: I161d50b2ddb50dbf25eb67e10414425f098b9979